Page 1 of 1
Rogue Contact
Posted: Tue Sep 18, 2012 5:24 am
by Flava
Hi,
I am unable to delete/activate or deactivate a contact in the NagiosXI UI, it is giving me the following errors.
The "Active" checkbox is grayed out.
Code: Select all
Entry cannot be activated because it is used by another configuration:
When I attempt to delete it, I get this error.
Code: Select all
No data deleted. The dataset probably does not exist, is protected from deletion or has relations to other configurations which cannot be deleted. Use the "info" function for detailed information about relations!
Re: Rogue Contact
Posted: Tue Sep 18, 2012 8:01 am
by scottwilkerson
Click the exclamation point next to the delete icon and you will get output on the bottom of the screen outlining what the dependencies are.
Re: Rogue Contact
Posted: Tue Sep 18, 2012 9:57 am
by Flava
I did, but some the services/ host it is referencing don't exist and anymore, and I don't recognize them, for example the have a suffix of <hostname>-SQL and i cannot find these hosts anywhere
Re: Rogue Contact
Posted: Tue Sep 18, 2012 1:23 pm
by slansing
Are you noticing any strange activity within Nagios? Can you stop and restart Nagios, and apply configurations?
Re: Rogue Contact
Posted: Wed Sep 19, 2012 3:22 am
by Flava
I think I have figured out what time issue is, in fact there are two issue here, first - Issue with Nagios CCM Beta Bulk Update, second - Core Config Manager cannot see any changes from Nagios CCM Bulk Update.
First Issue: Issue with Nagios CCM Beta Bulk Update
I am able to use Nagios CCM to bulk update contacts list for services, however, when I view the alert settings for the individual services nothing is listed. If I attempt to delete the contact, Core Config Manager complains deletion not possible
...The second annoying thing, removing the contact from all services using Nagios CCM to bulk update does not work, it says it has been removed, but this is not the case. I have just over 700 services, updating the alert setting individually is quite frustrating and the bulk update seemed handy, but it is actually more of hindrance. Can you please advice a work around? Updating several hundred services individually is not good use of my time.
Core Config Manager
The second issue I have noticed is that any changes made by Nagios CCM Beta Bulk such as the contact bulk update as example is not visible in the Core Config Manager UI, even though it is reporting contact is associated with particular service. The only way to fix this is to de-activate the service, write the config, and then only then you can make changes to contact (see attached pix), the UI will not allow you to de-activate that contact.
Also, if a service has only one contact configured for alerting, Core Config Manager will not let you remove that contact unless you remove the contact from the each service contact is applied. If you have decided to remove a contact, then the UI should also remove it from all dependant services, it should not force you to go into every service and do it manually. I understand this is weird protection mechanism, but override should be available.
Re: Rogue Contact
Posted: Wed Sep 19, 2012 11:02 am
by mguthrie
What version of the new CCM component are you using? It should list the version number in the Admin->Manage Components page?
Re: Rogue Contact
Posted: Fri Sep 21, 2012 3:40 am
by Flava
Version: 0.4 Date: 05/03/2012 Author: Mike Guthrie. Nagios Enterprises, LLC
Re: Rogue Contact
Posted: Fri Sep 21, 2012 10:22 am
by lmiltchev
Can you click on the "Info" button and post a screenshot of the output?