> > > for that service. Ergo, if you set your service checks max to 15, after > > > 15 minutes (assuming your delay is 60 seconds) your service will hit a > > > HARD CRITICAL, and host checks will fire. > > > > That's not correct, host checks are performed as soon as a service check > > returns some non-OK status. > > Yes thats right. > A service never reaches the max_check_attempts if the host check return not=
Thanks for all the insight. And I assume ALL service checks are on hold as soon as host check returns non-OK. What I think I'm finding is that some of my SNMP-based service check scripts are hanging far too long and the Net-SNMP daemon can only handle one connection at a time (doesn't fork a new daemon) so all subsequent checks fail, to include my HOST check as it is a combination of connecting to the snmpd and sshd daemons. The sshd connection is fine but the snmpd times out. I do this as pinging wasn't possible to the systems I'm monitoring as they're spread across the Internet. Should I set my service check timeout to something outrageous (it's already at 90 seconds) or can I tell Nagios to run serialized service checks for certain problematic hosts? -- - Kyle --------------------------------------------- [EMAIL PROTECTED] http://www.panix.com/~kylet --------------------------------------------- ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Nagios-users mailing list [email protected] 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
