Hi NagiosXI team,
We're using check_nt to monitor CPU usage, but in one server, sometimes, it returns super big value. Like below.
[1570626026] SERVICE ALERT: SERVER_NAME_XXXX;System: CPU Usage;CRITICAL;SOFT;1;CPU Load 18446744044341600887% (5 min average)
CPU load is 18446744044341600887%, just wondering what caused this and how to avoid it? Is it RRD overflow?
Nagios XI version : 5.5.8
NSClient++ version : 0.5.0.62
Thanks
check_nt returns super big CPU usage value
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_nt returns super big CPU usage value
Can you post the actual command that Nagios is using when making this call to nsclient?
Re: check_nt returns super big CPU usage value
check_nt -H hostname -s "password" -p 12489 -v CPULOAD -l 5,80,90
This huge CPU usage returning value is not always happening. It happens for example, once or twice a week. Very concerning how it happens.
This huge CPU usage returning value is not always happening. It happens for example, once or twice a week. Very concerning how it happens.
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_nt returns super big CPU usage value
I've not run into this ever with CPULOAD, I'm not sure if it's a bug with the version or your specific server.
We are not the authors of NSClient however and it would have to be a bug in that, I would suggest reaching ot to the author, they may have some suggestions or things you can try to resolve the issue.
Their forum is here
https://forums.nsclient.org/
We are not the authors of NSClient however and it would have to be a bug in that, I would suggest reaching ot to the author, they may have some suggestions or things you can try to resolve the issue.
Their forum is here
https://forums.nsclient.org/
Re: check_nt returns super big CPU usage value
Please upgrade to the latest 0.5.2.xx version of NSClient as there is a but that was fixed in newer versions that could effect that test you are running.
From the NSClient++ changelog
From the NSClient++ changelog
Code: Select all
2017-04-06 Michael Medin
* check_nt CPU load using invalid time (second instead of minute) Fixes #251 and #403
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: check_nt returns super big CPU usage value
Thanks guys!
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_nt returns super big CPU usage value
Let us know if the upgrade resolves your issue.caqin wrote:Thanks guys!
Thanks!