Nagios Support Forum

Hi Support Team,

I'm unable to delete/deactivate the config for a service "Drive D: Disk Usage" due to the following error:
"Item <SERVERX> cannot be disabled because it has dependent relationships"

I have checked and there are no service/host escalations attributed, nor parent-child relationships.
I've deleted config files and re-written them.

Issue seems similar to this thread but I see no resolution in here:
https://support.nagios.com/forum/viewto ... ips#p87876

Is there a way I can gain some clarification from NagiosXI logs on what exactly is this rouge dependant relationship so that I can remove it and finally disable the host and service?
Additional note - Only this single service on the host is unable to be disabled, all other services on this host are able to be disabled without issue.

There was a bug in an older version of XI 2014.

In CCM, instead of clicking the X icon for the service, "check" the check box in the left column for the service and then at the bottom middle in the "With Checked" drop down list select "Delete".

Does this work?

If you still are getting the problem try this in an SSH session to the XI host: Replace centos01 with the name of your service defined in the service directive.
This will display all the config files where your server is being referenced.

Does any of this help?

Hi Box293,

Thanks you have helped me find the answer, although it is still very strange! I did the checked action and it provided me with this info:

Object ID: 526 of table tbl_service:
Relation to Serviceescalations, entry: <SERVERY>- Dependent relationship
Object still has dependent relationships!Item was not deleted.

Because I had a "Drive D: Disk Usage" service escalation activated for <ServerY> (but not <ServerX>), it would not let me disable the drive D service on <ServerX>.
This config seems strange because it should base the service escalation on the activates host(s) and service combinations, otherwise surely it will not allow me to disable this same service for all hosts that I wish to deactivate in future. Is this some kind of bug or by design?

I am on version 2014R2.7 for info.

Yes the escalations can be tricky at times.

In CCM, can you click the disk icon for the service escalation so I can look at the config and see what is going on ... even if you've already deleted the service, the escalation should still give the relevant information I am after.