2009/5/7 Dei Bertine <[email protected]>: > Basic question guys: > > Which file do you normally place your service dependencies in? > > It stated here: http://nagios.sourceforge.net/docs/2_0/dependencies.html > to place in objects cfg file which I thought placing it in my nagios.cfg???? > > But when I did, it complained about this error after running -v: > Error in configuration file 'nagios.cfg' - Line 2859 (NULL value) > > > Here's a sample of my definition: > define servicedependency{ > host_name ciscoasa-router > service_description PING > dependent_host_name ciscosw-router > dependent_service_description PING > execution_failure_criteria o > notification_failure_criteria w,u > } > > Please advise. > > Thank you! > DB
I would put service dependencies in a file called something like 'servicedependencies.cfg'. in nagios.cfg, you need a pointer to this new file, for example: cfg_file=/usr/local/nagios/etc/objects/servicedependencies.cfg The nagios.cfg file should only contain the main configuration file options which you'll find documented in http://nagios.sourceforge.net/docs/3_0/configmain.html But ... I'm not convinced you should need service dependencies for 'ping' from one host to another. Nagios handles this sort of thing automatically if you configure the host parent relationships. See: http://nagios.sourceforge.net/docs/3_0/networkreachability.html hth, Jim ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ 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
