Scheduled downtime issue

[skol]

I recently setup a service wide scheduled downtime to test the setting. After seeing how it worked for us, I removed the configuration. However, nagios is still scheduling downtime with the configuration removed.

[slansing]

Is this the only downtime configuration you have? How many times has it re-scheduled the downtime? What version of Nagios Xi are you on?

[skol]

Is this the only downtime configuration you have? How many times has it re-scheduled the downtime? What version of Nagios Xi are you on?

It was, yes. It has re-scheduled the downtime twice so far. 2012R1.5

[lmiltchev]

If you do to: Home->Incident Management->Scheduled Downtime or Home->Incident Management->Recurring Downtime, you don't see any schedules at all?

[skol]

Correct.

I also have hosts and services which aren't in the configuration yet seem to still be configured in the configuration database (they show up as a monitored service/host yet they do not exist in the CCM). Perhaps related?

[sreinhardt]

It sounds like you may have some ghost host\service issues. For those same objects, how recently did you remove them, and are the configuration files still existing in your local file system. They would be located in /usr/local/nagios/etc/hosts/ or /usr/local/nagios/etc/services/

[skol]

It sounds like you may have some ghost host\service issues. For those same objects, how recently did you remove them, and are the configuration files still existing in your local file system. They would be located in /usr/local/nagios/etc/hosts/ or /usr/local/nagios/etc/services/

For the ghost host/services in question:

I did some config clean up, removed 3-5 hosts and associated services. Wrote configs, verified, then restarted nagios. About 30 minutes later, I was adding an additional contact and left an option blank (it would be good to bold or red the absolutely required fields in the UI to reduce this next part) and clicked "apply configuration" which resulted in an error. Immediately after it seemed it rolled back to an older config set which then included these hosts/services I had removed which immediately began alerting. I removed them from the filesystem and restarted nagios (which fixed the problem) since the hosts/services in question weren't available via the CCM.

[lmiltchev]

Nagios cannot start or restart with bad configuration. It is always a good idea to run the Write Config Tool, prior to Applying Configuration, in order to check for config errors.
Just to confirm, has the issue been resolved?

[skol]

Nagios cannot start or restart with bad configuration. It is always a good idea to run the Write Config Tool, prior to Applying Configuration, in order to check for config errors.
Just to confirm, has the issue been resolved?

No, the recurring downtime part hasn't changed (I can't tell if it will attempt to do it again - the schedule was every Saturday 2300-0400).

recurringdowntime.cfg is empty.

[slansing]

Hmm, are you running multiple instances of the nagios process, possibly due to the configuration issue?:

Code: Select all

service nagios stop

killall -9 nagios

service nagios start

Please share the above command's output's.