Nagios Support Forum

Hi all,

I'd appreciate some help with this one:

We recently upgraded from Nagios 3.5 to 4.2.3. Today we noticed that a lot of our hosts and services had comments associated with them (the little speech bubble). Turns out that all these comments are automatic comments due to downtimes we had scheduled some time last week, like so:

This host has been scheduled for fixed downtime from 12-03-2016 00:12:28 to 12-03-2016 02:12:28. Notifications for the host will not be sent out during that time period.

The comments are marked "Persistent: No", but they did not get deleted once the downtime ended. This is not only very confusing and makes it impossible to tell which host/service has a "real" comment associated with it, but it also makes loading of "System -> Comments" very, very slow since we've scheduled downtime for hundreds of hosts and thousands of services in the last couple of days due to some major OS upgrades.

I am pretty sure that in the old 3.5 version auto-comments associated with downtime disappeared once the downtime was canceled or expired. Is there a new configuration setting in v4 that I need to tweak in order to have non-persistent comments removed automatically again?

Any help would be much appreciated.

- B

I suspect I know the answer, but did you reload or restart? There is a difference in newer versions of Core per internal feature request 8830.

Please restart nagios and let us know if that resolves the issue.

If it does not resolve the issue, could you post the output of tail -100 /usr/local/nagios/var/nagios.log? Thanks!

This works for me on Core 4.2.2 and 4.2.4:

Thanks guys,

took me a few days to look into this but I finally got to it. Restarting instead of reloading takes indeed care of the non-persistent comments. I also found this discussion here:

https://support.nagios.com/forum/viewto ... =7&t=38779

I do not agree with the logic behind the change in comment handling, but at least I know now how to deal with it.


Thanks again,

- B

Brainslug wrote: I do not agree with the logic behind the change in comment handling, but at least I know now how to deal with it.

You're always free to get involved in the bug/enhancement discussions at https://github.com/NagiosEnterprises/nagioscore/issues

That said, are we ready to lock this up?

Yep, please go ahead and close this one.

Thanks again for your help.