Funny thing is doing a new round of digging led me to the cause, thanks for that :)
There seems to be a problem with service dependencies, disabling that cfg results in working checks again. Guess I'll have to take that config file apart tomorrow. -----Original Message----- From: Marc Powell [mailto:m...@ena.com] Sent: Saturday, January 10, 2009 0:05 To: nagios-users Mailinglist Subject: Re: [Nagios-users] check_ping stuck on 'PENDING' On Jan 9, 2009, at 4:48 PM, <ibloodyhates...@gmail.com> <ibloodyhates...@gmail.com > wrote: > As per the subject... Nagios 3.0.6 and it happens both to lan and > external servers. > As ping's a very basic check and as far as I can see everything should > work normally, right now I'm stumped. Any idea what's going on here? Actual config information is necessary otherwise we're just guessing in the dark. Nagios doesn't think it's supposed to perform a check. Is the timeperiod right? host definition, service definition (and templates for both if used) and timeperiod definition would be a good start. -- Marc ---------------------------------------------------------------------------- -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ 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 ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ 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