NCPA - System Uptime

[Maxwellb99]

Hi Guys,

Any idea why in the GUI the system-uptime node of NCPA sometimes returns the value in seconds. Sometimes it says "uptime was x months y days z seconds" sometimes it says "uptime was XXXXXXX.00 seconds"

Thanks,
Maxwell Ramirez

[lmiltchev]

Is this an active or passive check? Can you show us how it's configured? What is the NCPA version that you are currently using?

Also, show us the actual check run from the command line along with the output of it.

[Maxwellb99]

Is this an active or passive check?
active

Can you show us how it's configured?
$USER1$/check_ncpa.py -H $HOSTADDRESS$ -t $USER9$ -M $ARG1$ $ARG2$
$ARG1$ 'system/uptime'
$ARG2$ -c 31622400 -w 15811200

What is the NCPA version that you are currently using?
Version 1.1.3

Also, show us the actual check run from the command line along with the output of it.
I posted part of the server names to demonstrate that these are different server instances. Otherwise the checks are the same.

uptime.PNG

Notes:
- It appears this is happening for warning & Critical. OK Shows the correct format.
- These checks are being executed against Linux Instances. I can't speak to whether this is happening on Windows.

[lmiltchev]

I tested the uptime checks against a Linux machine (CentOS 6), but haven't been able to recreate the issue. The output for OK, WARNING, and CRITICAL states is shown in days, minutes, and seconds. I will have to bring in our NCPA developer and do some more testing. Meanwhile, can you run your "failing" check a few times, then post the /usr/local/ncpa/var/log/ncpa_listener.log from the remote machine on the forum?

Also, run the following command on the Nagios XI server and show the output:

Code: Select all

/usr/local/nagios/libexec/check_ncpa.py -H <ip address> -P 5693 -t <token> -M system/agent_version

[Maxwellb99]

The ones it's jacked up on are running 2.06.
The majority are running 2.1.2.

... and there it is in the changelog: 2.1.0: "Fixed check settings not showing up on system/uptime and added human readable output to check return output."

Thanks for your help.
Maxwell Ramirez

[lmiltchev]

Please run your "failing" check a few times, then post the /usr/local/ncpa/var/log/ncpa_listener.log from the remote machine on the forum. Also, run the following command on the Nagios XI server and show the output:

Code: Select all

/usr/local/nagios/libexec/check_ncpa.py -H <ip address> -P 5693 -t <token> -M system/agent_version

[Maxwellb99]

The ones it's jacked up on are running 2.06.
The majority are running 2.1.2.

... and there it is in the changelog: 2.1.0: "Fixed check settings not showing up on system/uptime and added human readable output to check return output."

Thanks for your help.
Maxwell Ramirez

[lmiltchev]

The ones it's jacked up on are running 2.06.
The majority are running 2.1.2.

Upgrade your NCPA to the latest (2.1.6 at the moment) - this should fix the issue that you are having. If you are still having the same problem (after the upgrade), upload the /usr/local/ncpa/var/log/ncpa_listener.log on the forum, and verify the agent's version by running:

Code: Select all

/usr/local/nagios/libexec/check_ncpa.py -H <ip address> -P 5693 -t <token>-M system/agent_version

[Maxwellb99]

Agreed. Yeah, that's the plan.

Thanks for your help.

[lmiltchev]

Sounds good. I will be locking this topic now. If you have any more questions/issues, please start a new thread. Thank you!