Yeah! finally it worked... first i submited a failed passive check like u suggested, followed by a forced check on the host, and then host state finally changed :)
Thanks! Giles Coochey escribió: > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:nagios-users- >> [EMAIL PROTECTED] On Behalf Of Jesús Oliván >> Sent: 25 October 2007 16:50 >> To: nagios-users@lists.sourceforge.net >> Subject: Re: [Nagios-users] Host down, but ping works >> >> I've done what u say, but after several times of "Re-shedulation" and >> after disabling and enabling host checks, it returned me >> >> Host Status: >> UP >> Status Information: FPING OK - ap-cien08 (loss=0%, rta=2.620000 ms) >> Performance Data: loss=0%;;;0;100 rta=0.002620s;;;0.000000 >> Current Attempt: 1/20 >> State Type: HARD >> Last Check Type: ACTIVE >> Last Check Time: 28-05-2007 11:07:31 >> Status Data Age: 150d 5h 42m 58s >> Next Scheduled Active Check: 25-10-2007 16:32:11 >> Latency: 0.000 seconds >> Check Duration: 0.031 seconds >> Last State Change: 25-05-2007 15:22:57 >> Current State Duration: 153d 1h 27m 32s >> Last Host Notification: N/A >> Current Notification Number: 0 >> Is This Host Flapping? N/A >> Percent State Change: N/A >> In Scheduled Downtime? >> NO >> Last Update: 25-10-2007 16:47:18 >> >> >> > > [Giles Coochey] > What happens if you submit a failed passive service check for one of the > services on the host? > > I'm wondering whether that could force a host check. > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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
