Error: Host Status Information Not Found!

[chris at aidworld.org]

Hello "T",

> I believe this phenomenon is tied to the check_timeout value of the nagios
> check processes.   The initscripts work fine after I added a 'sleep 10' to
> them in between the stop and start clauses.  I even converted them to
> RedHat
> style (Starting nagios...  [OK]).  My check_timeout is 10 seconds, so the
> lingering child processes have died by the time the script starts a new
> instance.  If you're using a much longer timeout, 'killall nagios' in
> between the stop/start might work better.

But I don't understand why a lingering service check is able to make the
web interface behave this way. Once the main (old) nagios process is dead,
the service checks should complete and then the old nagios should clean up
after itself, while the new one takes over running service checks and
maintaining state. It seems that it doesn't work in this nice clean way,
but why? And shouldn't it be fixed?

In the mean time, adding "killall nagios" to the initscript seems like a
sensible precaution, if perhaps a little violent.

Cheers, Chris.



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null