[resending as a real new message, rather than a lazily hijacked thread] Hi all,
I'm trying to get service dependencies with service groups working and not having any luck. The format given in the docs isn't working for me. Am I just being stupid, or is there something else going on? I'll admit to not having dived into the source, as reading source code isn't one of my strong suits... The intent is to have a bunch of services (same service on several hosts) not be checked if the same service type on one host fails. Service group membership is defined by "servicegroups" lines on the specific service defs. The following servicedependany def is only one of many I've tried. Every way I've tried fails nagios -v with: "Nagios 2.9 Copyright (c) 1999-2007 Ethan Galstad (http://www.nagios.org) Last Modified: 04-10-2007 License: GPL Reading configuration data... Error: Could not expand dependent hostgroups and/or hosts specified in service d ependency (config file '/usr/local/etc/nagios/services.cfg', starting on line 19 ) ***> One or more problems was encountered while processing the config files..." Service group and dependency definitions: define servicegroup{ servicegroup_name all-wan-ping alias Pings for all WAN } define servicedependency{ host_name host1 service_description PING dependent_servicegroup_name all-wan-ping dependent_service_description PING execution_failure_criteria w,u,c notification_failure_criteria w,u,c } Freebsd 6.1, Nagios 2.9 Any thoughts? thank you for your time, tim ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ 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