Page 2 of 4

Re: Nagios Monitoring ERROR/BUG

Posted: Wed Jan 07, 2015 12:25 pm
by slansing
Is the address of the server changing? Perhaps a low DHCP lease time? Alternatively, are you sure the nrpe daemon is starting properly, and that your firewall is not being reset, or changing upon system start? Looks like it is just having routing issues to port 5666 on that address.

Re: Nagios Monitoring ERROR/BUG

Posted: Fri Jan 09, 2015 12:00 am
by rmuhammadali
Dear,
Static IPs used rather then DHCP.
Firewall is disabled.
NRPE is running fine.

Anyother suggestions?

Re: Nagios Monitoring ERROR/BUG

Posted: Fri Jan 09, 2015 3:00 pm
by tmcdonald
How long are you waiting after the system is brought down, and between checks? If you run "shutdown -h now" on the machine and test immediately after, you might get a timeout as the machine is still on but no services are running. Then the next check might be done after the machine really is down, showing the second error of no route.

Re: Nagios Monitoring ERROR/BUG

Posted: Fri Jan 09, 2015 3:20 pm
by tgriep
What version of Nagios Core are you running?

Can you run this command on the Nagios Core server and post the output so we can get the version of the check_nrpe plugin?

Code: Select all

/usr/local/nagios/libexec/check_nrpe

Re: Nagios Monitoring ERROR/BUG

Posted: Sat Jan 10, 2015 1:22 am
by rmuhammadali
Dear,
I am using Nagios 4.0.4 and nrpe 2.15
tmcdonald wrote:How long are you waiting after the system is brought down, and between checks? If you run "shutdown -h now" on the machine and test immediately after, you might get a timeout as the machine is still on but no services are running. Then the next check might be done after the machine really is down, showing the second error of no route.
i know this situation, but my problem is something else.

Re: Nagios Monitoring ERROR/BUG

Posted: Sun Jan 11, 2015 6:10 am
by rmuhammadali
Any Suggestions?

Re: Nagios Monitoring ERROR/BUG

Posted: Mon Jan 12, 2015 5:54 pm
by abrist
Are these 2 boxes on the same subnet?
Can you add -vvv to your swap check?

Re: Nagios Monitoring ERROR/BUG

Posted: Tue Jan 13, 2015 2:02 am
by rmuhammadali
Yes dear both boxes are on same network subnet

Re: Nagios Monitoring ERROR/BUG

Posted: Tue Jan 13, 2015 5:33 pm
by tmcdonald
Can you add the -vvv switch to the check as abrist suggested? We would like to see the verbose output.

Re: Nagios Monitoring ERROR/BUG

Posted: Thu Jan 15, 2015 12:34 am
by rmuhammadali
On Client (When its up)

Code: Select all

./check_swap -w 40% -c 20% -vvv
Reading PROC_MEMINFO at /proc/meminfo
Got Total with 1228792.000000
Got Free with 1228792.000000
SWAP OK - 100% free (1199 MB out of 1199 MB) |swap=1199MB;479;239;0;1199
After changing in /usr/local/nagios/etc/nrpe.cfg of Client

Code: Select all

command[check_swap]=/usr/local/nagios/libexec/check_swap -w 40% -c 20% -vvv
On Server (When client is up)

Code: Select all

./check_nrpe -H 192.168.2.5  -c check_swap
Reading PROC_MEMINFO at /proc/meminfo
Got Total with 1228792.000000
Got Free with 1228792.000000
SWAP OK - 100% free (1199 MB out of 1199 MB) |swap=1199MB;479;239;0;1199
On Server (When client is down)

Code: Select all

 ./check_nrpe -H 192.168.2.5  -c check_swap
connect to address 192.168.2.5 port 5666: No route to host
connect to host 192.168.2.5 port 5666: No route to host
On Nagios (When client is down)
Nagios Output 15012015.jpg