Page 2 of 2
Re: Contact_groups for hosts always null in cfg file
Posted: Tue Jul 13, 2010 4:22 pm
by niebais
null isn't selected on the clients having problems. I'll send a screenshot still if needed.
Re: Contact_groups for hosts always null in cfg file
Posted: Wed Jul 14, 2010 9:48 am
by niebais
Ok, here's what we figured out, it has to be related somehow to the xi_wizard_website_host template.
Re: Contact_groups for hosts always null in cfg file
Posted: Wed Jul 14, 2010 11:25 am
by mguthrie
You might also want to check the settings for the xiwizard-generic-host template. The xi_wizard_website_host template inherits a lot of it's values from this parent template (or at least it's supposed to).
Re: Contact_groups for hosts always null in cfg file
Posted: Wed Jul 14, 2010 2:53 pm
by niebais
We've been looking into the values and haven't tracked down what is causing it quite yet.
Re: Contact_groups for hosts always null in cfg file
Posted: Wed Jul 14, 2010 4:19 pm
by mmestnik
You can look at the results of all the template's by examining the objects.cache file typically located some where around /usr/local/nagios/var.
Re: Contact_groups for hosts always null in cfg file
Posted: Wed Jul 14, 2010 4:21 pm
by mmestnik
Are you sure the group is highlighted? The interface lists every group weather it's selected/used or not.
Re: Contact_groups for hosts always null in cfg file
Posted: Fri Jul 16, 2010 8:53 am
by niebais
How do I upload images in this thing? I've got some screenshots.
Re: Contact_groups for hosts always null in cfg file
Posted: Fri Jul 16, 2010 8:56 am
by niebais
netscalar_alert.JPG
netscalar_check.JPG
netscalar_common.JPG
Re: Contact_groups for hosts always null in cfg file
Posted: Fri Jul 16, 2010 10:14 am
by mguthrie
I'm noticing in that first screenshot that the radio button under the "contact groups" is set to "null." Try setting that to "standard" and see if that takes care of it.
Re: Contact_groups for hosts always null in cfg file
Posted: Fri Jul 16, 2010 11:47 am
by niebais
I'm not sure how that "null" option got selected, but that solved the problem. Several of our services had the "null" option checked.