Nagios Monitoring ERROR/BUG

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.
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Nagios Monitoring ERROR/BUG

Post 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.
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post by rmuhammadali »

Dear,
Static IPs used rather then DHCP.
Firewall is disabled.
NRPE is running fine.

Anyother suggestions?
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: Nagios Monitoring ERROR/BUG

Post 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.
Former Nagios employee
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Nagios Monitoring ERROR/BUG

Post 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
Be sure to check out our Knowledgebase for helpful articles and solutions!
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post 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.
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post by rmuhammadali »

Any Suggestions?
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: Nagios Monitoring ERROR/BUG

Post by abrist »

Are these 2 boxes on the same subnet?
Can you add -vvv to your swap check?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post by rmuhammadali »

Yes dear both boxes are on same network subnet
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: Nagios Monitoring ERROR/BUG

Post by tmcdonald »

Can you add the -vvv switch to the check as abrist suggested? We would like to see the verbose output.
Former Nagios employee
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post 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
Locked