High temperature since update on 2.0.0p19

Troubleshooting
,
1

Hi there

Since updating from version 2.0.0.p12 to 2.0.0.p19, the temperature of my server has rised from average 60-63 to 72-77.

Is this a known bug? Any advice how to fix this?

**CMK version: 2.0.0.p19 (CEE)
**OS version: Ubuntu 18.04.6 LTS

Greetings

2

It depends on your hardware and the actual load on the system. But i had no such problems on all my systems.

3

Its normal, its the climate change :rofl:

Sorry for that.

What exact check you are referring to? I can double check on our end.

regards

Michael

4

It’s the check “temperature zone 0” from the checkmk server itself.

It’s a HP Proliant DL360 Gen10

Intel Xeon Silver 4110 CPU @ 2.10GHz
32 GB RAM

Strangely right after updating, the temperature rised to crit. I restarted the server but shortly after 5-10 minutes, temperature was right back at crit state. Not sure if should go back to version 2.0.0.12p.

5

Hello,

Sorry to not be precise.
I need the following:

image

This is just an example! Tell what the service check command is for your temp check.

regards

Michael

6

Hi Michael

Its this: check_mk-lnx_thermal

7

I expect the problem is not the sensor, but maybe the cpu load that increased and so the temperature does. Have you checked the graph of the cpu load. Did it increase after the update?

1 Like
8

Yes cpu load und utilization increased right after update.

9

Please ignore this check on hardware like the HP Proliant it is useless.
For better results use the values provided from the iLO interface.
Only this values are relevant to detect overheating or anything like a hardware failure.

10

I’ve seen similar behaviour some time ago. As far as I remember, something seemed to be wrong with the rrd update and was restarting processes and gererating log entries multiple times per second.

Try to drill down to the culprit process and have a look for logs that grow more quickly than normal.

Sorry for being so vague, but since it was just a test site back then, I just trashed it and didn’t investigate any further.

2 Likes
11

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.