Andreas Ericsson wrote: > Anirudh Srinivasan wrote: > >> Hey Folks, >> >> I know " socket timeout after 20 sec" has been discussed so many time in all >> the forums and post, but still this is not so clear to me. >> >> Nagios server : RHEL 5 >> >> NC_NET used on Windows server. >> >> In startup.cfg the port is 12489 and the ip_passive is ip address of the >> nagios server. >> >> Even through the Linux cli i get the same error >> >> ./check_nt -H <ip_windows_server> -v FREEDISKSPACE -l C -w 80 -c 90 -p 1248 >> -t 50 >> CRITICAL - socket timeout after 50 sec >> >> I really have been breaking my head on this. Please suggest some idea or >> your experience >> >> > > There is a firewall blocking the traffic somewhere along the way, or you > have managed to build a cyclic token-ring network (if you don't know what > those are, consider yourself lucky and look over your firewalls). > > I have also experienced this quite a lot of times on networks where there has been inconsistent duplex and speed settings on network cards and switches. My recommendation is to always fix the speed on connections between routers and switches otherwise you can get this speed renegotiation which causes short downtimes or mismatch in the duplex having one port decide that it's half-duplex and the connected port full-duplex, both will cause a lot of socket timeout in Nagios.
/Johannes ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Nagios-users mailing list Nagios-users@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
