Page 1 of 1

Check_nt uptime return wrong value

Posted: Mon Mar 09, 2015 9:52 am
by skeith
Hi everyone,

I have the nsclient version 0.4.3.88 on my entire organization, monitored by the last nagios core, I use the check_nt plugin, with some basic checks and i've problems with the UPTIME command.
It will often return a wrong value, the value is like a floating number where, for example, 70000 is equal to 7. Here's my test:

command for testing (i did a check more times in one minute):

Code: Select all

./check_nt -H host -p 12489 -s password -v UPTIME -l seconds
results:

Code: Select all

System Uptime - 392 day(s)  6 hour(s) 8 minute(s) |uptime=33890897
System Uptime - 392 day(s) 6  hour(s) 8 minute(s) |uptime=33890898
System Uptime - 392 day(s) 6  hour(s) 8 minute(s) |uptime=33890899
System Uptime - 3   day(s) 22 hour(s) 8 minute(s) |uptime=338909
can you tell me how to fix the problem?

Re: Check_nt uptime return wrong value

Posted: Mon Mar 09, 2015 4:05 pm
by ssax
The problem is with nsclient version 0.4.3.88, it is a bug, I experience the same thing. I validated that it does work properly with nsclient version 0.3.9.

We still recommend nsclient version 0.3.9 as the stable version.

Re: Check_nt uptime return wrong value

Posted: Mon Mar 09, 2015 7:04 pm
by Box293
You should report the issue here on GitHub so it gets fixed:

https://github.com/mickem/nscp

I find that 0.4.1.105 is stable.

0.4.2.x and 0.4.3.x has undergone a complete rewrite by the developer and not everything works as expected, it's very frustrating.

Re: Check_nt uptime return wrong value

Posted: Tue Mar 10, 2015 3:43 am
by skeith
You should report the issue here on GitHub so it gets fixed:

https://github.com/mickem/nscp
Ok I did it, ty!
Here's the link for the bug, if someone want help: https://github.com/mickem/nscp/issues/118

The problem is with nsclient version 0.4.3.88, it is a bug, I experience the same thing. I validated that it does work properly with nsclient version 0.3.9.

We still recommend nsclient version 0.3.9 as the stable version.
Yes it's true, i used for a long time 0.3.9 version and i've never found this bug.