Why does Socket Timeout immediately send notification?

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of timeless
> Sent: Friday, January 06, 2006 11:51 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Why does Socket Timeout immediately send
> notification?
> 
> I have Nagios configured to send notifications after 4 CRITICAL
service
> checks. However, if the service check returns "socket timeout," Nagios
> immediately sends the page without doing another 3 checks.

Is it a service or host notification?

> 
> Google searches and searching the documentation/FAQ for "socket
timeout"
> only explain what the problem is, not why that sort of failure results
> in an immediate HARD STATE change.

It doesn't. It's treated no differently than any other non-OK plugin
state. Nagios only knows about exit codes and there are only 4
possibilities: OK, WARNING, CRITICAL and UNKNOWN. Nagios performs
retries if the state is anything except OK up to max_check_attempts.

> Any clues for me? How can I make it only result in a HARD CRITICAL
after
> 4 checks, like other CRITICAL events?
> 

Service and host definitions as well as their associated command
definitions would be helpful. My guess would be that when nagios sees
the non-OK return of the service plugin it executes the host
check_command which returns a non-OK state as well resulting in a host
notification because nagios believes the host is down.
 
--
Marc


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&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