On 06/27/2011 11:45 PM, Eric B. wrote: > This has me stumped. I whittled my ugly config down to 35 lines, and was > still able to re-create the error. Any ideas what is wrong? I'm running > Nagios Core v. 3.2.3. Much thanks in advance! >
It appears that the error reporting isn't working as it should. It claims that the problem is with the serviceescalation or servicegroup when it's in fact a problem with the host and the service being incomplete objects. Remove the serviceescalation for now and run the config verifier with the config you posted and you'll see all the errors reported. Fixing those, the config passes even when including the serviceescalation. I can see how that must've been pretty confusing. Unfortunately I have no time to spend on this at the moment, so unless someone else comes up with a patch, it'll be left as-is until I revamp config parsing to do objects in relational order. -- Andreas Ericsson [email protected] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ 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
