Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
That makes sense. Your Nagios system is outside of the network where your target machine resides. There is a machine that has an external IP address, and has access to your target machine. So we put NCPA on the machine with the external IP address, put the check_ping plugin in NCPA's plugins directory, and then have Nagios use the check_ncpa.py plugin like this.
I have updated as you said,
I have taken the check_ping plugin from Nagios plugins and put it in remote server ncpa plugin folder, after that i run the command from Nagios Server
Im getting an error UNKNOWN: An error occured connecting to API. (HTTP error: '500 INTERNAL SERVER ERROR')
That looks like you're not able to connect to the NCPA API at all. If you put the external IP address into your web browser followed by :5693 do you get a page asking for your token?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Alright, let's make sure we have the correct plugin installed. Previously, I saw that check_ping.c was copied over to the server. This is actually the source code for the check_ping plugin. We need the binary copied over. You should have a file called /usr/local/nagios/libexec/check_ping with no .c at the end. That's the one you need to transfer.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Your Right .. And I have changed the check_ping file as you said, but when I'm running those command in Nagios Server still it's not succeeding getting error like https://prnt.sc/qj73ta
Perfect! We're getting closer. That is the output for check_ping, so we know the request is making it across. I think all you should have to do is encapsulate the command line switches for check_ping in single quotes. So your command will look something like this.
THRESHOLD is <rta>,<pl>% where <rta> is the round trip average travel
time (ms) which triggers a WARNING or CRITICAL state, and <pl> is the
percentage of packet loss to trigger an alarm state.
So 70 and 80 are pretty high numbers. That would be 70 and 80 seconds to make the trip. In the screenshot, your round trip was 0.22. So you might want a warning of 0.8 and a critical of 0.9. Then adjust as you get alerts. Or you can leave the round trip average up at 70 and 80, which will pretty much guarantee you will not get an alert unless there is packet loss.
Packet loss is the second part of the pair. Your warning is set to 2% packet loss, and critical is 5% packet loss. The check_ping plugin sends 5 pings to the specified host. So if you lose 1 packet, you have a 20% packet loss.
Does that help clear things up?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!