empty hostgroups forbidden in 2.0b6
Phil Mayers
p.mayers at imperial.ac.uk
Tue Dec 6 21:02:36 CET 2005
moving from 2.0b3
"[root at monhost nagios]# /usr/local/nagios/bin/nagios -v
/usr/local/nagios/etc/nagios.cfg -h
Nagios 2.0b6
Copyright (c) 1999-2005 Ethan Galstad (http://www.nagios.org)
Last Modified: 11-30-2005
License: GPL
Reading configuration data...
Error: Hostgroup has no members (config file
'/usr/local/nagios/etc/dynamic/ic.cfg', starting on line 161)
"""
To which I'd reply - so what?
This is particularly annoying for us. We (re)build the nagios
configuration every 5 minutes (and HUP if diff says so) from an
extensive SQL database containing routers, switches, hosts, networks,
routing topology and so on.
The hostgroups in question are per-building and per-wiring-centre.
They're just extracted as a list and added to the config file. If I have
to only add ones which actually contain stuff, I'll have to keep a list
of what was touched whilst building the other devices and then append
them - this means each time I add a new device type to the export
script, I have to remember to include the code. Annoying.
Is there a practical reason for this change? Or would a patch/revert be
accepted?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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
More information about the Users
mailing list