Nagios Support Forum

The update screen is stuck updating and nothing I've tried will release or finish that update. The update box shows the info below but never completes. os looks to be CentOS release 6.7 (Final)

Also, I ran a manual update via ssh and it appeared to complete. Still can't get the gui to reflect the new version and remove the upgrade in progress dialog.


---- Starting Nagios XI Backup ----
No entry for terminal type "unknown";
using dumb terminal settings.
Stopping nagios: done.
Starting nagios: done.
Backing up NagiosQL...
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
Backing up Nagios Core...
tar: Removing leading `/' from member names
tar: /usr/local/nagios/var/rw/nagios.qh: socket ignored
tar: /usr/local/nagios/var/ndo.sock: socket ignored
Backing up Nagios XI...
tar: Removing leading `/' from member names

Hi thfadmin,

Sometimes that "Upgrade in progress" message needs to be cleared manually. Here is a KB that will walk you through that process.

https://support.nagios.com/kb/article/n ... e-851.html

I had not come across that article. Thanks. It did indeed reset the update status in the web interface but clicking to update to the new version still stalls and does not complete. Just sits at "update in progress" with the text below showing.

Verified that the upgrade log has the same information and nothing more.

---- Starting Nagios XI Backup ----
No entry for terminal type "unknown";
using dumb terminal settings.
Stopping nagios: done.
Starting nagios: done.
Backing up NagiosQL...
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
Backing up Nagios Core...
tar: Removing leading `/' from member names
tar: /usr/local/nagios/var/rw/nagios.qh: socket ignored
tar: /usr/local/nagios/var/ndo.sock: socket ignored
Backing up Nagios XI...
tar: Removing leading `/' from member names

Hello @thfadmin,

If you ran a manual upgrade and it completed, you should be running the latest version. Please send over a system profile for us to review the logs. Thanks.

To send us your system profile.
Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and share in a private message or upload it to the post/ticket, and then reply to this post to bring it up in the queue.

The download profile does not work for some reason. I get the error

"PROFILE BUILD FAILED
Array
(
)
CODE: 1

I just copied and pasted the output to a txt file. Odd....

Hi @thfadmin,

"PROFILE BUILD FAILED
Array
(
)
CODE: 1

This error is typically the result of an incorrect sudoers file. To correct, follow the instructions in the article below and then try to download the system profile again.

Nagios XI - Profile Build Failed

Let me know if you have any questions.

That worked. Here is the file.

Hi @thfadmin,

Thanks for the system profile. I dd notice crashed database tables in the logs, so let's run the db repair script and then try upgrading again.

1. To repair the script, log in as root and run the following command: 2. Then run the commands the following commands to upgrade and post the output of any errors. Reference: Nagios XI Upgrade Instructions

Ok I completed those commands. No change in Update status.


DISTRO INFO:
CentOS
6.7
x86_64


Archive: sourceguardian/ixed4.lin.x86-64.zip
inflating: /usr/lib64/php/modules/ixed.5.3.lin
Sourceguardian extension found for PHP version 5.3
Sourceguardian extension already in php.ini
Stopping httpd: [ OK ]
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain for ServerName
[ OK ]
Checking required prereqs...
Please wait...

OLD VERSION: 5510
Loaded plugins: fastestmirror
Setting up Update Process
Loading mirror speeds from cached hostfile
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
[root@localhost ~]#

Hello @thfadmin,

Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again

It looks like some issues with the repos on the server causing the upgrade to fail. Please post the the full output to the following commands to help us diagnose the issue. Thanks.

1. List repositories 2. Clear yum cache 3. List configured repositories 4.Lastly, are you able to successfully connect over both http and https?