Nagios Support Forum

From what I can tell from the audit logs no commits have been done since 2/10/2019 @ 13:19, where a host was added for monitoring. We went to update our on-call list this morning and now we are getting errors related to "an escalation but is not defined anywhere!"

I deactivate the escalation it is complaining about then it hits the next service as if it is walking through all of them. I rolled back to the last good commit and still getting the same errors. I think there is a deeper problem but can't for the life of me find it.


Here is the output from the last attempted commit.
Error: Service 'sw89.phibred.com' on host 'PassiveService' has an escalation but is not defined anywhere!
Error: Could not register service escalation (config file '/usr/local/nagios/etc/serviceescalations.cfg', starting on line 367)
Error processing object config files!

Thanks.

Are there any files found in the import directory? If so, lets delete them and try applying configuration again

Found the problem. Some how, some way one of my admins was able to remove a host from a service which was causing the problem. I am not sure why I didn't see it in the log files.

System is working fine now.

hockad wrote:Found the problem. Some how, some way one of my admins was able to remove a host from a service which was causing the problem. I am not sure why I didn't see it in the log files.

System is working fine now.

Great, glad to hear it is resolved!

Locking thread