Running 2011R1.2:
In prepping for a migration from 2009 to 2011, I had imported hosts too soon. I removed 31 pages of hosts, selected apply configuration and now it just sits @ "Waiting for configuration verification", 30 minutes and counting. The dots just continue expanding. If I change to a different page, and come back and hit apply configuration, the cycle starts over.
If I modify an existing configuration and hit apply, though it doesn't appear to ever finish, the change does take place.
Any ideas?
Thanks,
Andy
Waiting for configuration verification never finishes
Re: Waiting for configuration verification never finishes
My guess is that you could be hitting either the memory limit or the timeout threshold for the PHP script.
Try the following solution and see if the config will go through:
http://support.nagios.com/wiki/index.ph ... _Completes
Try the following solution and see if the config will go through:
http://support.nagios.com/wiki/index.ph ... _Completes
Re: Waiting for configuration verification never finishes
Thanks for your suggestion, however it did not work in this instance. I did discover the following in the httpd:
[Mon May 16 15:26:28 2011] [error] [client 127.0.0.1] access to /usr/local/nagiosxi/html/backend/ failed, reason: SSL connection required
On Friday, before removing the hosts, and after configuring SSL, I had modified nagiosxi.conf and uncommented the #SSLRequireSSL line. When I commented out the line and restarted httpd, the issue went away.
Thanks,
Andy
[Mon May 16 15:26:28 2011] [error] [client 127.0.0.1] access to /usr/local/nagiosxi/html/backend/ failed, reason: SSL connection required
On Friday, before removing the hosts, and after configuring SSL, I had modified nagiosxi.conf and uncommented the #SSLRequireSSL line. When I commented out the line and restarted httpd, the issue went away.
Thanks,
Andy
Re: Waiting for configuration verification never finishes
Are you running strict SSL site-wide? If so I should probably give you a heads up that we had a couple of known bugs when everything is forced through port 443. However, they should be fixed in the next release, but in the meantime you may want to leave port 80 open since there are a couple of backend calls that will still want to use port 80.