Hi Yueh-Hung, Unfortunately, same result (just tried it). -E <div class="gmail_quote">On Mon, Jun 27, 2011 at 7:05 PM, Yueh-Hung Liu <<a href="mailto:yuehung.liu@gmail.com">yuehung.liu@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">try to remove the line 'register 0' from the definition of your servicegroup. <div><div></div><div class="h5"> On Tue, Jun 28, 2011 at 8:17 AM, Eric B. <<a href="mailto:barnabus.pinklehorn@gmail.com">barnabus.pinklehorn@gmail.com</a>> wrote: > Hi Brandon, > > I would normally agree with you, but there are numerous undocumented > features w/i nagios, and it actually does recognize the option (the file I > posted is completely self-contained); if you misspell the option (like > serviceXgroup_name), it reports it as an unknown option. My much larger > config uses this parameter for serviceescalation in other parts with no > problems.The error says it can't 'expand the servicegroups specified', so > I'm leaning towards that the problem you mentioned as a red herring... > > Hopefully your thought isn't the case, otherwise, I have a big problem > rewriting all my configs... :-/ > > -Eric > > On Mon, Jun 27, 2011 at 3:43 PM, Brandon Williams <<a href="mailto:bwilliams@zynga.com">bwilliams@zynga.com</a>> > wrote: >> >> Looking at >> >> >> >> define serviceescalation { >> servicegroup_name group-1 >> first_notification 1 >> last_notification 6 >> notification_interval 5 >> contacts primary-oncall >> } >> >> >> >> I don’t see an option for : >> >> >> >> servicegroup_name group-1 >> >> >> >> >> >> In the Nagios documentation. I would try removing that line and trying >> again. >> >> >> >> >> <a href="http://nagios.sourceforge.net/docs/3_0/objectdefinitions.html#serviceescalation" target="_blank">http://nagios.sourceforge.net/docs/3_0/objectdefinitions.html#serviceescalation</a> >> >> >> >> >> >> From: Eric B. [mailto:<a href="mailto:barnabus.pinklehorn@gmail.com">barnabus.pinklehorn@gmail.com</a>] >> Sent: Monday, June 27, 2011 2:46 PM >> To: <a href="mailto:nagios-users@lists.sourceforge.net">nagios-users@lists.sourceforge.net</a> >> Subject: [Nagios-users] Expand service group error in 43 line test config >> (why?) >> >> >> >> 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! >> >> -Eric >> >> Error is: >> >> Error: Could not expand servicegroups specified in service escalation >> (config file '/home/opsmon/etc/nagios/objects/qbo/foo.cfg', starting on line >> 13) >> Error processing object config files! >> >> Here's the config: >> >> define servicegroup { >> servicegroup_name group-1 >> alias All Services >> register 0 >> } >> >> define contact { >> contact_name primary-oncall >> alias Primary Oncall >> email <a href="mailto:foo@bar.com">foo@bar.com</a> >> } >> >> define serviceescalation { >> servicegroup_name group-1 >> first_notification 1 >> last_notification 6 >> notification_interval 5 >> contacts primary-oncall >> } >> >> define service { >> servicegroups group-1 >> host_name <a href="http://admin.qa" target="_blank">admin.qa</a> >> check_command check_foo >> } >> >> define host { >> host_name <a href="http://admin.qa" target="_blank">admin.qa</a> >> address 127.0.0.1 >> } >> >> define command { >> command_name check_foo >> command_line /bin/true >> } >> >> >> ------------------------------------------------------------------------------ >> 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. >> <a href="http://p.sf.net/sfu/splunk-d2d-c2" target="_blank">http://p.sf.net/sfu/splunk-d2d-c2</a> >> _______________________________________________ >> Nagios-users mailing list >> <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> >> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> >> ::: Please include Nagios version, plugin version (-v) and OS when >> reporting any issue. >> ::: Messages without supporting info will risk being sent to /dev/null > > > ------------------------------------------------------------------------------ > 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. > <a href="http://p.sf.net/sfu/splunk-d2d-c2" target="_blank">http://p.sf.net/sfu/splunk-d2d-c2</a> > _______________________________________________ > Nagios-users mailing list > <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> > <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> > ::: Please include Nagios version, plugin version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null > ------------------------------------------------------------------------------ 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. <a href="http://p.sf.net/sfu/splunk-d2d-c2" target="_blank">http://p.sf.net/sfu/splunk-d2d-c2</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </div></div></blockquote></div>