Ok than had it been the issue with the check-host-alive command I am using it should be the same with other versions of nagios as well right?...I reverted back to 2.0b4 and its working fine now..explicitly had some tests. Outputs were as expected! None problems faced then.

However I will test 2.10 again and cross check the check-host-alive and other services run.

Thanks n Regards,

Gaurav

--
Disclaimer:
This Email message along with any attachments is intended only for the 
addressee and may contain confidential and/or privileged information. If you 
have received this message in error, please notify sender immediately and 
delete this message from your system.  If the reader is not the intended 
ecipient then any dissemination, distribution or copy of this communication is 
strictly prohibited.   Reasonable precautions have been taken to ensure that 
this message is virus-free. However, Subisu Cablenet Pvt. Ltd. does not accept 
responsibility for any loss or damage arising from the use of this message or 
attachments.



Marc Powell wrote:
On Mar 23, 2008, at 12:01 AM, Gaurav Ghimire wrote:

<rearranging reply to fit in context...>

Marc Powell wrote:
Does this host have any services associated with it? What is their
status when this problem occurs? Can you post the host definition and
a service definition for the host?
Yes this host has the service definitions attached to it. The configuration were the same and it was working well before the upgrade. I was using 2.0b4, later when I upgraded to 2.10 I started facing this sort of issues.

There are no known issues with any version of nagios like this.

Here is the host and its attached service.

Host Definition

define host{
        use                     generic-host3
        host_name               wrk_a
        alias                   wrk
        address                 192.168.1.5
        check_command           check-host-alive
        max_check_attempts      10
        notification_interval   120
        notification_period     24x7
        notification_options    d,r
        contact_groups  admins
        }

Looks fine. The implication then is that your check-host-alive command doesn't actually do that. The status information at the time this happens would be the confirmation of that. When a service goes down, check-host-alive is run. If it returns a non-OK state (or fails in certain ways), the host status is set to non-OK. When the service recovers, check-host-alive is run again to verify that the host has recovered. If it still returns a non-OK state (or fails in certain ways), the host status will remain non-OK. When you restart nagios, check-host-alive is _not_ run. Instead, nagios assumes the host is OK as long as the service on the host returns OK.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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

Reply via email to