nsclient connection refused after restart

[Tom DE BLENDE]

Here's what I think your problem is:

W2K box is rebooting. It comes back up and the TCP/IP stack is loaded
quite early in the boot process. Nagios sees your W2K has returned to
life again, and assumes it's OK to start checking services on that
host again. However, since the boot process has not been fully
completed, the NSClient service is more than likely not available for
queries yet.

To test my theory, you should try to run the plugin a few times from
the CLI after the system is fully booted to see if that really is the
problem.

> "VanZee, Timothy" wrote:
> 
> I have searched the nagios.org faq and looked at the mail archives
> back through November 2002 and didn’t find anything relating to this
> issue, unless I missed which is possible.
> 
> 
> 
> I’m running nagios 1.0 on a RH 7.2 server with nsclient 1.07.1.  I
> have the nsclient service running on multiple Win2k servers.  If
> anyone restarts one of the Win2k servers while nagios is still
> running, the Win2k server will come back up and nagios will report
> ‘Connection refused by host’.  I will then check the Win2k system
> and verify that the nsclient service is running.  If I then stop and
> restart the nsclient service; nagios will again start monitoring the
> affected services successfully.
> 
> 
> 
> Is there a solution to this issue for the Win2k servers?
> 
> 
> 
> 
> 
> Tim Van Zee
> 
> ITS Network Specialist
> 
> Governors State University
> 
>


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
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