Project

General

Profile

Bug #69546

CPU Critical Temperature Alerts in Daily Security Run

Added by Dean Souleles 2 months ago. Updated 2 months ago.

Status:
Closed
Priority:
No priority
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
User Configuration Error
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No
Tags:

Description

Beginning with the 11.2 upgrade almost every day I get a "local security run" email with critical temperature detected messages on one or more cores like the following:

coretemp3: critical temperature detected, suggest system shutdown
coretemp2: critical temperature detected, suggest system shutdown

The dashboard CPU temperature reads a steady 32C any time I check, however I just ran this:

sysctl -a | egrep -E "cpu\.[0-9]+\.temp"
dev.cpu.3.temperature: 48.0C
dev.cpu.2.temperature: 55.0C
dev.cpu.1.temperature: 54.0C
dev.cpu.0.temperature: 51.0C

The CPU is a Core i5-3570K with the stock CPU fan installed and I verified that the fan is running. tjmax on the processor is 150C.

Any ideas what might be going on? Why am I getting critical temperature alerts? What is the dashboard CPU temperature displaying? What accounts for the difference between the dashboard and what I got back from form the sysctl command?

Thank you,

Dean

OS Version:
FreeNAS-11.2-RELEASE-U1
(Build Date: Dec 20, 2018 22:41)
Processor:
Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 cores)
Memory:
16 GiB

Temp Classic.JPG (40.1 KB) Temp Classic.JPG Dean Souleles, 01/15/2019 07:32 PM
Temp New.JPG (21.9 KB) Temp New.JPG Dean Souleles, 01/15/2019 07:32 PM
Temp Classic-zoomed.JPG (39.8 KB) Temp Classic-zoomed.JPG Dean Souleles, 01/16/2019 04:30 PM
48934
48936
49267

History

#1 Updated by Dru Lavigne 2 months ago

  • Private changed from No to Yes
  • Reason for Blocked set to Need additional information from Author

Dean: please attach a debug (System -> Advanced -> Save debug) to this ticket.

#2 Updated by Dean Souleles 2 months ago

  • File debug-freenas-20190114195036.tgz added

Debug attached.

#3 Updated by Dru Lavigne 2 months ago

  • Category changed from OS to Middleware
  • Assignee changed from Release Council to William Grzybowski
  • Reason for Blocked deleted (Need additional information from Author)

#5 Updated by William Grzybowski 2 months ago

  • Status changed from Unscreened to Blocked
  • Reason for Blocked set to Need additional information from Author

tjmax on the OS side is 105 and I can see in your debug a core is running above 70C already. So its likely at some point during the day its reaching 105 or very close.

The graph in new UI is suing wrong temperature units, there is another ticket about that.

Can you verify the Reporting graph in legacy UI for cpu temperature and verify the values during the days?

#6 Updated by Dean Souleles 2 months ago

48934
48936

Verified that legacy UI and new UI show different temperatures.

Also here is sysctl output from the same time:

% sysctl -a | egrep -E "cpu\.[0-9]+\.temp"
dev.cpu.3.temperature: 50.0C
dev.cpu.2.temperature: 60.0C
dev.cpu.1.temperature: 53.0C
dev.cpu.0.temperature: 56.0C

Can you show me where you found the 70.0C reported? If my CPU really is running hot I need to figure out what is happening.

Thank you,

Dean

#7 Updated by William Grzybowski 2 months ago

Its in your debug: dev.cpu.2.temperature: 71.0C

Please use the zoom out in the legacy UI so you can have a bigger picture of temperatures across days (not just hours)

#8 Updated by Dean Souleles 2 months ago

49267

Ok thanks - zoomed in legacy temp display attached.

It appears to be peaking every evening between 10-midnight and again around 3:00AM.

I guess I need to change / upgrade to CPU cooler - the fan appears to be working.

I have Freenas running, plus Plex in a jail (low to no usage), plus PiHole in a VM.

Dean

#9 Updated by William Grzybowski 2 months ago

  • Category changed from OS to Middleware
  • Status changed from Blocked to Closed
  • Target version changed from Backlog to N/A
  • Reason for Closing set to User Configuration Error
  • Reason for Blocked deleted (Need additional information from Author)

Seems like the message is legit so nothing to fix here.

Thanks for the feedback

#10 Updated by Dru Lavigne 2 months ago

  • File deleted (debug-freenas-20190114195036.tgz)

#11 Updated by Dru Lavigne 2 months ago

  • Private changed from Yes to No

Also available in: Atom PDF