I'm having the same problem as described in this post (http://thread.gmane.org/gmane.network.nagios.user/8176/); that is to say, I have hosts that are forever with status "pending" and status information "(Not enough data to determine host status yet)" in the Host Detail screen. In the Service Detail screen, the "Service check scheduled for" date under status information is shown as within the next minute, but it keeps getting put back and back indefinitely.

But the cause of my problem must not be the same as in the above post, because I do have the check-host-alive service defined for my host:

define host{
        use                     generic-host
        host_name               albany
        alias                   Albany - Second Bonded Link
        address                 192.168.253.200
        parents                 head_office
        check_command           check-host-alive
        max_check_attempts      20
        notification_interval   30
        notification_period     24x7
        notification_options    d,u,r
        notifications_enabled   1
        }

Also, there are no errors defined when I run nagios -v /etc/nagios/nagios.cfg, and I also ran nagios -s and made sure I had the recommended service check scheduling.

Does anyone have any suggestions?

TIA

--
Jeremy Malcolm LLB (Hons) B Com
Internet and Open Source lawyer, IT consultant, actor
host -t NAPTR 1.0.8.0.3.1.2.9.8.1.6.e164.org|awk -F! '{print $3}'

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

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

Reply via email to