Nagios Support Forum

Hello,

Recently, we installed a certificate. Now, when I go to delete a service, or make any change, then click apply configuration I get the following message:

An error occurred while attempting to apply your configuration to Nagios Core. Monitoring engine configuration files have been rolled back to their last known good checkpoint.

I looked at the XI wiki, and ran through the steps on the closest error match I could find, and the error is from wget complaining about the certificate/hostname match:

certificate common name `ubitmon-jf.intel.com' doesn't match requested host name `localhost'.
HTTP request sent, awaiting response.

Apparently, the hostname doesn't match the certificate, and I don't know where this needs to be changed. I am including two error files.

Nagios Version: 2012R1.8
Redhat 6.4

Regards,

Randy.

Did you follow the steps, outlined in this document?

Yes. I can't find anything about hostname in that file. The error message definitely claims the cert is being used but the hostname is wrong.

It is only a warning, and it still fetches the page. (200 OK) Just a note - you need to set your time (localtime and php.ini timezone). See the following document: http://assets.nagios.com/downloads/nagi ... m_Time.pdf

The date and time is correct. That doesn't solve the problem as I still can't save the configuration. Can we please escalate this?

Regards,

Randy.

You can certainly open a ticket with [email protected] and preferably link back to this page. Otherwise I see a couple things that don't really seem to have been addressed. It seems a system update may have caused a known issue with php and it seems that your nagios ql login might be incorrect.

So first question, do you know if you have changed the QL default authentication at all?

Secondly check your /etc/php.d/mcrypt.ini like so:
Once that is done, if you could attempt to save the config again, and attach another errors.txt and reconfig.txt that would be fantastic!

Thank you. Given all the suggestions you all gave me, it turns out that the system now works very well. You can close this out.

Regards,

Randy.

Thanks for letting us know!