Page 2 of 2

Re: Waiting for configuration verification.

Posted: Fri Feb 25, 2011 4:15 pm
by mccollege
Try increasing the max execution time for a php script in your /etc/php.ini file and see if that does anything. Crank it up to 60 seconds as a test.
No change.
Do you have any special configurations on your system, such as a proxy, or SSL?
We're redirecting http traffic to https.
On a sidenote, we generally recommend the latest release, as it has the latest features and bug fixes.
We started out with the ( I think 2009R1.3C ) VM you had released. When we had added most of our clients, we took a snapshot of the vm. When this same problem had happened, we upgraded to the newest version at the time ( 2009R1.3D ) but that didn't resolve the problem. When we rolled back to the snapshot the system was working correctly, so I upgraded to it's current version ( 2009R1.3G ) and the system was still working correctly. The system had been running about 2 weeks when I noticed it again started the behavior I created this thread for.

Re: Waiting for configuration verification.

Posted: Fri Feb 25, 2011 5:01 pm
by rdedon
mccollege wrote:
We're redirecting http traffic to https.
In what manner or how did you redirect?

Re: Waiting for configuration verification.

Posted: Tue Mar 01, 2011 9:32 am
by mccollege
I added:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

to the httpd.conf

Re: Waiting for configuration verification.

Posted: Tue Mar 01, 2011 12:32 pm
by mccollege
I added:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

to the httpd.conf
Ok, I was going over my notes and in /etc/httpd/conf.d/nagiosxi.conf, line 2, I had uncommented "SSLRequreSSL"

Commenting out the Rewrite lines, and re-commenting "SSLRequireSSL" -seemed- to resolve my problem.

So what's the proper way to force https for nagios without breaking it?

Re: Waiting for configuration verification.

Posted: Wed Mar 02, 2011 10:31 am
by rdedon
You should just be able to go to:
-Configure
-Run Monitoring Wizard
-Website
-Enter URL
-Check that Use SSL is enabled and port along with whatever Services you would like monitored
-Continue through next steps

Hopefully this helps! :-)

Re: Waiting for configuration verification.

Posted: Wed Mar 02, 2011 1:18 pm
by mccollege
Ok, I was going over my notes and in /etc/httpd/conf.d/nagiosxi.conf, line 2, I had uncommented "SSLRequreSSL"

Commenting out the Rewrite lines, and re-commenting "SSLRequireSSL" -seemed- to resolve my problem.

So what's the proper way to force https for nagios without breaking it?
Would doing the http rewrite cause any problems with nagiosxi?

I'm not sure why, reverting these changes appears to have resolved my issue?

Re: Waiting for configuration verification.

Posted: Thu Mar 03, 2011 10:35 am
by rdedon
I have also tried a rewrite from there with non-functioning results if I recall correctly.

Re: Waiting for configuration verification.

Posted: Thu Mar 03, 2011 12:02 pm
by mccollege
I have also tried a rewrite from there with non-functioning results if I recall correctly.
Is this a bug?

Or is there another way to use redirect/force https use in nagiosxi?

Re: Waiting for configuration verification.

Posted: Thu Mar 03, 2011 12:44 pm
by mguthrie
I wouldn't say we have a "right" way to force SSL on Nagios XI. I know many users have done it, some with mixed results. Nagios XI should detect https, but I know the CCM requires that https must specified manually in the Configure->Core Config Manager->Config Manager Admin->Config Manager Settings page. Actually, that could have been the issue you were running into, since the reconfigure_nagios.sh and the Apply Configuration calls CCM scripts to execute. We also just posted a fix for R2011 that should also detect https for grabbing the performance graphs as well. So long story short, if you find a way to force https site-wide and get it working correctly, if you could post what you did, we'll probably repost it on our wiki and document it as the "right" way ;).