Re: Your request was not processed in a timely manner...
Posted: Mon Jun 03, 2013 10:39 pm
I was just able to reproduce this problem on a brand new clean install!
I did this in VMware Workstation 9
Steps to reproduce as I just did:
-Manual install of CentOS 5.9 x64
-Download XI Source 2012R1.8 and fullinstall
-Log in to XI to verify working
-Once installed, follow the "Configuring SSL with Nagios XI" document
-Log in to XI and verify SSL is working, verify monitoring engine status is all good
-Download XI Source 2012R2.0 and upgrade
-Log in to XI once upgrade is done.
-Observe that monitoring engine status is now broken and the system is exhibiting the behaviors in this thread and other threads.
Uknowns: 32 bit / 64 bit, does it matter? Would a clean fullinstall of R2.x on 5.9 cause the break, or does it only happen in an upgrade? Is CentOS6 upgrade similarly effected, using clean installs (I couldn't reproduce with the OVF files).
Just thinking out loud... hope some of that helps you guys in troubleshooting this. I figure if you can get your own box doing this it'll be tons easier for you to troubleshoot and fix it.
I did this in VMware Workstation 9
Steps to reproduce as I just did:
-Manual install of CentOS 5.9 x64
-Download XI Source 2012R1.8 and fullinstall
-Log in to XI to verify working
-Once installed, follow the "Configuring SSL with Nagios XI" document
-Log in to XI and verify SSL is working, verify monitoring engine status is all good
-Download XI Source 2012R2.0 and upgrade
-Log in to XI once upgrade is done.
-Observe that monitoring engine status is now broken and the system is exhibiting the behaviors in this thread and other threads.
Uknowns: 32 bit / 64 bit, does it matter? Would a clean fullinstall of R2.x on 5.9 cause the break, or does it only happen in an upgrade? Is CentOS6 upgrade similarly effected, using clean installs (I couldn't reproduce with the OVF files).
Just thinking out loud... hope some of that helps you guys in troubleshooting this. I figure if you can get your own box doing this it'll be tons easier for you to troubleshoot and fix it.