NagiosQL Login Failed

[vhoover]

I attempted to upgrade our nagios server tonight from 2012r2.9 to 2014r2.0 after fixing a few minor problems the upgrade took off. I had to repair the database, but after all was said and done I got the following message:

Capture.JPG

Now the nagios xi instance acts as though it will not speak to the databases. If that wasn't bad enough the performance graphs completely disappeared. The is no graph or icon for a graph.

My system is a NagiosXI VM
Operating System : CentOS 6.3
I have configured Nagios to use SSL (https://nagiosxi.mydomain.com/nagiosxi)

I have another server that took the upgrade without any issue. This server that seems to have broke from the upgrade is the only instance that is running 2012r2.9, I need to get it upgraded so that I can get my fail-over configuration running (see the Nagios Advanced Training manual written by Mike). I can submit my system profile if needed.

[Box293]

I suspect you are using a proxy server.

Follow this FAQ:

http://support.nagios.com/wiki/index.ph ... th_Proxies

Specifically edit the /etc/wgetrc file and add the no_proxy entry.

Re-run the upgrade and it should complete from here.

Let us know how that goes.

[vhoover]

Sorry no proxy is used, and I verified the system is not set to use a proxy, in fact I set the option use_proxy to "off".

[Box293]

Can you try running the upgrade with iptables turned off.

Code: Select all

service iptables stop

[vhoover]

Keep in mind that this solution was tested on a clone of the production server, but that seemed to work. I would like to keep this open for a week to try it on the production server. Thanks Troy.

[abrist]

Alright. Let us know if you experience any issues on the prod system.

[vhoover]

When I made the earlier statement

Keep in mind that this solution was tested on a clone of the production server, but that seemed to work.

I was under the impression that the upgrade had worked on the clone. I was incorrect. I tried to upgrade the production server with the suggestion of having iptables turned off, only to find that no change in the result. I still receive the same error message. So I thought that I would use the clone sine the upgrade worked, that is when I discovered that it did not work and was still running 2012r2.9. Not to mention that it was saying that every host was down. I knew this to be in error. So I had to roll back the VM to the snapshot taken prior to the upgrade attempt. I am at a complete loss, and I need to get this resolved as it it making me look like I have no clue what I am doing.

[Box293]

If you have support send an email to [email protected] and we'll get it resolved via a remote session.

[vhoover]

An email has been sent.

[tmcdonald]

Going to lock this for the time-being while we handle it via email.

Edit: Success! Solved via remote.