Nagios Support Forum

Hi team,

I have scheduled downtime for complete hostgroup PFA (Hostgroup scheduled downtime)

But after that also schedule downtime is not working though there was no error found PFA (Schedule downtime result)

Date format mentioned in account information PFA (date information)

We are using nagiosxi 5.2.5
Recently we upgraded nagiosxi version and also shifted nagiosUI to secure layer means http:// to https:// (Using TLSv1.2 protocol with self signed certificate)

There is no error found while doing scheduling downtime in /usr/local/nagios/var/nagios.log

Getting below error in /var/log/httpd/error_log
[Sun Apr 03 05:39:15 2016] [notice] Digest: generating secret for digest authentication ...
[Sun Apr 03 05:39:15 2016] [notice] Digest: done
[Sun Apr 03 05:39:19 2016] [warn] RSA server certificate CommonName (CN) `ps-promon-prd-um-002' does NOT match server name!?
[Sun Apr 03 05:39:19 2016] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations

ps-promon-prd-um-002 is our hostname
Please help us in scheduling downtime as it is very critical .

This is most likely related to why you can't schedule downtime through core either.

I know you mentioned no errors are found in the nagios.log file, but what do you see in the GUI when you attempt to schedule downtime?

After scheduling hostgroup downtime , its not reflecting under incident management >schedule downtime

Both screenshots i have attached.

I have raised a case for this, they were saying this seems to be a bug in current version , in next upcoming release this issue will be fixed where some customers are facing this issue.

XI 5.2.6 was just released today, could you try updating to that version and see if your issue is resolved?

https://www.nagios.com/downloads/nagios-xi/

Thanks rkennedy .

Updated nagiosxi to v5.2.7 Schedule downtime bug has been fixed in version 5.2.6

Planned downtime for hostgroup is working now.

Thanks for that update and glad to hear everything is working now. Did you have any other questions, or may we close this thread?