R2.5 Upgrade hiccup

[GldRush98]

Just had a weird thing happen. I was updating some XI machines to 2.5 and had something unusual happen.
Machine 1: 2.3 -> 2.5 = Upgraded good
Machine 2: 2.4 -> 2.5 = Upgraded good
Machine 3 (main production machine): 2.4 -> 2.5 = Issue below

Code: Select all

HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `nagiosql.login'

    [ <=>                                                                                                                                  ] 381,595     --.-K/s   in 0.04s

2015-01-27 09:05:11 (8.27 MB/s) - `nagiosql.login' saved [381595]

NAGIOSQL LOGIN FAILED!
[root@nagios nagiosxi]#

Just before that, I got:

File /usr/local/nagiosxi/html/includes/utilsl.inc.php Corrupt, Contact Nagios Support Immediately

Attempting to browse to the web gui immediately spit out the error about the same file being corrupted.
After I cleaned up my pants, I grabbed a utilsl.inc.php file off the previous machine that just updated fine and threw it in there. Updated ownership and perms. I could then browse to the web gui but I was afraid I was left with a partially upgraded box since the upgrade script errored out.

I attempted to run the upgrade script again and was greeted with:

[root@nagios nagiosxi]# ./upgrade
./upgrade: line 5: .: ./xi-sys.cfg: cannot execute binary file
[root@nagios nagiosxi]#

I rm'ed the directory and re-extracted the gz tar file and ran the upgrade script again. This final time it ran and completely normally with no errors. After looking over the output I don't think I needed to run it again, but I was paranoid. I've never see an upgrade script error out with a file corrupt error before.

The files are the exact same size:

-rwxr-x--- 1 nagios nagios 381612 Jan 27 09:14 utilsl.inc.php
-rwxr-x--- 1 nagios nagios 381612 Jan 27 09:05 utilsl.inc.php.corrupt

But there is something wrong:

[root@nagios includes]# md5sum utilsl.*
7ae78eeeacab23308ab699fc3fd0fcca utilsl.inc.php
c0ccf5ba176c331d97b362623972ab4f utilsl.inc.php.corrupt

Any idea on what the heck happened? I just ran the 2.4 update last week with zero issues and the machine has been running fine...
Solar flare? Paranoia?
It's just odd as I've never had an issue updating really and I just did 2 other machines off the same gz file I downloaded with in a few minutes of eachother....

[jomann]

It should be okay. It's likely that the tarball didn't extract the first time correctly and the file was corrupt. We've tested it here 2.4 upgrading to 2.5 and it works fine. As long as it upgraded fine at the end and it shows up in your GUI that you're running 2014R2.5 then you should be just fine.

[GldRush98]

Ok, it does. Thanks for the reassurance.

[cmerchant]

We'll go ahead and close the thread. Thanks.