Nagios Monitoring ERROR/BUG
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Nagios Monitoring ERROR/BUG
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
Dear,
Static IPs used rather then DHCP.
Firewall is disabled.
NRPE is running fine.
Anyother suggestions?
Static IPs used rather then DHCP.
Firewall is disabled.
NRPE is running fine.
Anyother suggestions?
Re: Nagios Monitoring ERROR/BUG
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
Re: Nagios Monitoring ERROR/BUG
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?
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_nrpeBe 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
Dear,
I am using Nagios 4.0.4 and nrpe 2.15
I am using Nagios 4.0.4 and nrpe 2.15
i know this situation, but my problem is something else.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.
-
rmuhammadali
- Posts: 27
- Joined: Sat Dec 13, 2014 4:02 am
Re: Nagios Monitoring ERROR/BUG
Any Suggestions?
Re: Nagios Monitoring ERROR/BUG
Are these 2 boxes on the same subnet?
Can you add -vvv to your swap check?
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.
"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
Yes dear both boxes are on same network subnet
Re: Nagios Monitoring ERROR/BUG
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
On Client (When its up)
After changing in /usr/local/nagios/etc/nrpe.cfg of Client
On Server (When client is up)
On Server (When client is down)
On Nagios (When client is down)
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
Code: Select all
command[check_swap]=/usr/local/nagios/libexec/check_swap -w 40% -c 20% -vvv
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
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