Upgrade from 5.2.3 to newest failed

[akepley]

Centos 6.8 server

Having the following in the upgrade log:

URL: http://localhost/nagiosxi/includes/components/ccm/
CMDLINE
/usr/bin/wget --save-cookies nagiosql.cookies --keep-session-cookies http://localhost/nagiosxi/includes/components/ccm/ --no-check-certificate --post-data 'submit=Login&hidelog=true&loginSubmitted=true&backend=1&username=nagiosxi&password=(removed)' -O nagiosql.loginNAGIOSQL LOGIN FAILED!

I have restored back to the backup taken before upgrade began so I'm back to normal but would like to understand where to go from here.

[dwhitfield]

I'm sorry to hear of the upgrade troubles. I have a few questions to help us help you get your upgrade working.

Could you post the entire upgrade.log? Is your database off-loaded? What about any other modification such as a ramdisk? If this an offline install (or through a proxy)? When you say the latest, do you mean 5.3.3 or 5.3.4 (released yesterday)? Was this a GUI upgrade or CLI upgrade?

Lastly, could you post or PM your /etc/sudoers and any files in /etc/sudoers.d/? If you choose to PM, please update the thread with the other information so your support thread shows back up on our support dashboard. Thanks!

[rkennedy]

In addition to what @dwhitfield mentioned, also, please show us your /etc/hosts file, and a screenshot of your Admin -> System Settings page - at times this is due to DNS not resolving properly for the internal calls.

[akepley]

Thanks all.

Our entire nagiosxi setup is local on one server, database and everything. No proxy whatsoever. No ramdisk or other mods. I was trying the install this morning and used the instructions to do the wget of the latest, so its whatever was available on your website this morning. CLI all the way.

PM'ing the rest of the stuff to you. FYI: nothing in /etc/sudoers.d/

[ssax]

Please follow this KB article:

Code: Select all

https://support.nagios.com/kb/article.php?id=532

If that doesn't resolve it, go to Admin > System Config > Reset Security Credentials
- Don't change anything, just click the Update Credentials button.

Now try the upgrade again.

If you are still having issues, please go to Configure > Core Config Manager > Config Manager Admin > Manage Config Access
- Edit the nagiosxi user, type in the password that the previous error showed and click the Save button


Try the upgrade again, if you are still having issues, please run this command and sent the full output:
- Make sure to change PASSWORD in the command below

Code: Select all

curl 'http://localhost/nagiosxi/includes/components/ccm/?submit=Login&hidelog=true&loginSubmitted=true&backend=1&username=nagiosxi&password=PASSWORD' -k -v

Thank you

[akepley]

Tried all troubleshooting suggestions and still have the same issue with NAGIOSQL

Here is the output of the command you wanted. Each time I run teh upgrade, the pass appears to change, so I tried it for each one.

root@nagiosxi nagiosxi# curl 'http://localhost/nagiosxi/includes/comp ... &password=' -k -v
* About to connect() to localhost port 80 (#0)
* Trying ::1... connected
* Connected to localhost (::1) port 80 (#0)
> GET /nagiosxi/includes/components/ccm/?submit=Login&hidelog=true&loginSubmitted=true&backend=1&username=nagiosxi&password=4hb02c HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: localhost
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 500 Internal Server Error
< Date: Fri, 16 Dec 2016 16:34:13 GMT
< Server: Apache/2.2.15 (CentOS)
< X-Powered-By: PHP/5.5.31
< Content-Length: 0
< Connection: close
< Content-Type: text/html; charset=UTF-8
<
* Closing connection #0

[tgriep]

Another thing to try id your server has SSL enabled is to edit the following file

Code: Select all

/usr/local/nagiosxi/html/config.inc.php

And make sure the use_https is set to true like below.

Code: Select all

$cfg['use_https'] = true;

Try that and let us know if this fixes the issue.

[akepley]

I'm confused on when I should do these things now. I've restored from teh backup so I'm back to 5.2.3. Should I be doing the upgrade, waiting for the failure and then make this change and do what?

[rkennedy]

All of this would help post upgrade, but also could affect it prior too. Usually with a 500 error, it'll help to see the apache logs and what is happening specifically.

If you'd like, I can walk through the upgrade with you on a remote session. Please email [email protected] referencing this post and my username. (as long as you are authorized for tickets)

[avandemore]

Handling in ticket.