Wrong CPU wait usage values
Hi,
I have Monit 5.20.0 running on a Debian 9.11 machine.
It is sometimes reporting erroneous CPU wait time values:
[UTC Nov 7 16:53:30] error : 'sip4' cpu wait usage of 1133092362155720704.0% matches resource limit [cpu wait usage>80.0%]
[UTC Nov 7 16:53:32] info : 'sip4' cpu wait usage check succeeded [current cpu wait usage=0.2%]
[UTC Nov 7 18:22:42] error : 'sip4' cpu wait usage of 1145049276229877760.0% matches resource limit [cpu wait usage>80.0%]
[UTC Nov 7 18:22:45] info : 'sip4' cpu wait usage check succeeded [current cpu wait usage=0.2%]
[UTC Nov 7 19:06:05] error : 'sip4' cpu wait usage of 1145049276229877760.0% matches resource limit [cpu wait usage>80.0%]
[UTC Nov 7 19:06:07] info : 'sip4' cpu wait usage check succeeded [current cpu wait usage=0.1%]
[UTC Nov 8 03:15:09] error : 'sip4' cpu wait usage of 1144338991718334464.0% matches resource limit [cpu wait usage>80.0%]
[UTC Nov 8 03:15:11] info : 'sip4' cpu wait usage check succeeded [current cpu wait usage=0.2%]
[UTC Nov 8 03:59:08] error : 'sip4' cpu wait usage of 1145049276229877760.0% matches resource limit [cpu wait usage>80.0%]
[UTC Nov 8 03:59:11] info : 'sip4' cpu wait usage check succeeded [current cpu wait usage=0.3%]
[UTC Nov 8 04:56:50] error : 'sip4' cpu wait usage of 1142920965315887104.0% matches resource limit [cpu wait usage>80.0%]
[UTC Nov 8 04:56:52] info : 'sip4' cpu wait usage check succeeded [current cpu wait usage=0.1%]
The processor is
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz
stepping : 9
microcode : 0xb4
cpu MHz : 3294.384
cache size : 8192 KB
Thank you,
Alex
Comments (4)
-
repo owner -
reporter 5.20 is the latest version available for Stretch
-
repo owner You can either compile monit from source or use pre-build binary distribution (https://mmonit.com/monit/#download)
-
repo owner - changed status to closed
- Log in to comment
please upgrade monit to 5.29.0 ... there were several CPU usage fixes since 5.20.0, the problem is most likely resolved already