This was working but appears to have stopped or causing errors.
COMMAND: /usr/local/nagios/libexec/check_ncpa.py -H webcms1t -t 'secret' -P 5693 -M cpu/percent -w 50 -c 90
OUTPUT: UNKNOWN: Error occurred while running the plugin.
The NCPA is running on Windows 2012 and is version 1.7.2 and I am using Nagios XI 2014R2.0. I would provide logs but not sure on Windows where these logs would be located.
NCPA UNKNOWN:Error occurred while running the plugin
Re: NCPA UNKNOWN:Error occurred while running the plugin
I've seem this error with an older version of the "check_ncpa.py" plugin, which had a bug.
Make a backup of the "old" plugin.
Download the latest version of the plugin from here:
https://github.com/NagiosEnterprises/nc ... ck_ncpa.py
Install it on your Nagios XI server:
Admin->Manage Plugins->Browse->check_ncpa.py->Upload Plugin
Note: Try running this command BEFORE and AFTER upgrading the plugin:
See if it is going to make a difference.
P.S. If you need to see the NCPA logs, they are located on the Windows client, usually in "Program FIles (x86)\Nagios\NCPA\var\" folder.
Make a backup of the "old" plugin.
Code: Select all
cd /usr/local/nagios/libexec
mv check_npca.py check_npca.py.oldhttps://github.com/NagiosEnterprises/nc ... ck_ncpa.py
Install it on your Nagios XI server:
Admin->Manage Plugins->Browse->check_ncpa.py->Upload Plugin
Note: Try running this command BEFORE and AFTER upgrading the plugin:
Code: Select all
/usr/local/nagios/libexec/check_ncpa.py -H webcms1t -t 'secret' -P 5693 -M cpu/percent -w 50 -c 90P.S. If you need to see the NCPA logs, they are located on the Windows client, usually in "Program FIles (x86)\Nagios\NCPA\var\" folder.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: NCPA UNKNOWN:Error occurred while running the plugin
I updated the plugin and tried running the command but got the same message. I took a closer look on the server and the log files were dated 11/16 and the services are stuck on Starting... I was unable get them to restart or stop so thought maybe a reboot, since after all this corrects 99% of Windows problems
but the services are still stuck at starting.
I am a Linux guy and not that familiar with Windows. I can point and click my way around but is there a way to force kill or force a restart on these ncpa services? This is my only machine running this client so I plan to install on a couple more to see if this is a bug or just a fluke on this particular Windows 2008r2 server. If anyone else has experienced this issue please let me know. I am in the process of trying to figure out what client to run and am leaning towards the ncpa over the NSCP but may have to rethink that decision.
I am a Linux guy and not that familiar with Windows. I can point and click my way around but is there a way to force kill or force a restart on these ncpa services? This is my only machine running this client so I plan to install on a couple more to see if this is a bug or just a fluke on this particular Windows 2008r2 server. If anyone else has experienced this issue please let me know. I am in the process of trying to figure out what client to run and am leaning towards the ncpa over the NSCP but may have to rethink that decision.
Re: NCPA UNKNOWN:Error occurred while running the plugin
I think I was finally able to get this working. I am going to install on another machine just to validate but I had to set the services to start with a delay and then the NCPA client reported back data and wasn't stuck on starting. Not sure if there was a conflict or what but after a couple reboots I got the same situation but once I delayed it then it started later on and the services showed started.
Re: NCPA UNKNOWN:Error occurred while running the plugin
This is a known issue and other users have set up "delayed" start of NCPA as a workaround. Our developers are looking into this. Let us know if you have any more issues.I think I was finally able to get this working. I am going to install on another machine just to validate but I had to set the services to start with a delay and then the NCPA client reported back data and wasn't stuck on starting.
Be sure to check out our Knowledgebase for helpful articles and solutions!