I am looking at the status.dat file and I noticed that the current_state is
=1 even when the host is down and is in critical state. I assume that if a
host is down, the current_state should be =2. I am not sure how Nagios sets
the current_status but in my case, the host is definitely off:
On Thu, 17 Mar 2011 14:57:08 +0800
Rai Ricafrente maill...@ricafrente.com wrote:
I am looking at the status.dat file and I noticed that the current_state is
=1 even when the host is down and is in critical state. I assume that if a
host is down, the current_state should be =2.
It's probably
Thanks for pointing the doc. I've been going through that and I guess I was
looking for the part where it says that DOWN = 1 and not 2.
On Thu, Mar 17, 2011 at 3:40 PM, Giacomo Montagner gmontag...@sorint.itwrote:
On Thu, 17 Mar 2011 14:57:08 +0800
Rai Ricafrente maill...@ricafrente.com
*Ubuntu 10.04*
*Nagios 3.0.3*
*Nagios-Plugin 1.4.14*
*Windows NSClient++ 0.3.7-Win32*
When running check_nt the following is being returned by Nagios
*Current Status:* WARNING (for 0d 2h 41m 44s) (Has been acknowledged)
*Status Information:* *could not fetch information from server*
I have a notification command that will typically take longer to run,
than my notification timeout. I don't particularly care, if Nagios gets
a valid return code back, so I set the main script to fork twice, with
the initial process printing 'OK' and exiting with a return code of 0.
The
