Ghost Service

[WillemDH]

I'm having a weird issue with a service that is visible in the XI gui, but nowhere to be found in the CCM... This happened after trying to clone a host, which also failed for some reason, after which I copied the service from the source host with the copy icon in the CCM.

This service is also not found in any config files related to this server. When I try to delete the service from the reconfigure service tab in the XI gui, I get:

Could not find a unique id for this service
Service cannot be deleted using this method
One or more errors were detected that prevent the service from being deleted.
Possible causes include...
The service is associated with other hosts, services, or objects that need to be deleted first
The service is generated by an advanced monitoring configuration entry
The service is maintained in a static or external configuration file
To resolve this issue...
Use the Nagios Core Configuration Manager to delete the service - or -
Manually delete the service definition from the appropriate external configuration file.

So how do I proceed getting rid of this service?

EDIT: The service is called 'NSClient_Log_Size'. So I tried deleting all NSClient_Log_Size service from all hosts. So there are 0 services named NSClient_Log_Size in the CCM atm. But the XI gui still shows this one service for this one host...

[lmiltchev]

Do you have multiple instances of nagios running?

Code: Select all

ps -ef | grep bin/nagios

Have you tried the following?

1. Running the "Write Config Files" tool in the exact same order - Delete->Write->Verify->Apply Configuration
2. Stoping/starting services.

Code: Select all

service nagios stop
service ndo2db stop
service ndo2db start
service nagios start

[WillemDH]

Ludmill,

I did try all your suggestions and I didn't have multiple Nagios instances running. We have a check for that, so we always know when that is happening.

Bug 'good news', somehow this ghost service has dissapeared in the meantime. I have absolutely no clue what has caused this and how it was solved.., but I guess you can close this thread for now.

Tx and grtz

Willem

[lmiltchev]

I will close the thread, Willem. Start a new one if the issue resurfaces.