Nagios Support Forum

Here is the update output...


---- Starting Nagios XI Backup ----
Backing up NagiosQL...
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
tar: /etc/nagiosql: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
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.bak: socket ignored
tar: /usr/local/nagios/var/ndo.sock: socket ignored
Backing up Nagios XI...
tar: Removing leading `/' from member names
Backing up MRTG...
tar: Removing leading `/' from member names
Backing up the SNMP trap interface configuration files...
Backing up NRDP...
tar: Removing leading `/' from member names
Backing up Nagvis...
tar: Removing leading `/' from member names
Backing up MySQL databases...
Backing up cronjobs for Apache...
Backing up logrotate config files...
Backing up Apache config files...
Compressing backup...

===============
BACKUP COMPLETE
===============
Backup stored in /store/backups/nagiosxi/autoupgrade_backup.1565032339.tar.gz

---- Starting Nagios XI Upgrade ----
Cleaning up temp directory...

Hi @mkeey,

On occasion the upgrade from the web interface will fail. Please try running the upgrade from the command line, and let me know if that works for you. If not, please post the full output from the upgrade log. Thanks.
Nagios XI Upgrade Instructions

Thank you for the information and suggestion. Issue is that one team in our organization handles the Admin duties of Nagios while another team handles the server & operating system. In other words, I don't have authority to run any command line functions on the XI server as that's considered a server/os function.

Besides that doesn't "fix" the problem, it's a workaround. Since we have these separation of duties (for a reason) I need the GUI upgrade to work.

How can we find out what's failing causing the upgrade to stall in the GUI?

Hi @mkeey,

It could be a slow network, disk space, permission settings, repos..,.etc. For typical, minimal installations, the GUI upgrade does work well. That said, we are planning to re-write the backend process to make it more robust.

Is this the first time you've had trouble upgrading from the web interface? If so, have you made any changes to your server? Have your admin check the disk space on the server.

We tried once before shortly after purchasing Nagios. The GUI upgrade failed then as well, due to permissions. We were in a hurry to get the upgrade in place to fix issues so we didn't pursue the problem but used the line command instead.

We once again need to upgrade to fix certain issues but have a little more time. So, we started working on the issue and this time fixed permission issues and actually got the process to start. Backups finished but stalled on cleaning up Temp files.

Only changes were Linux patching and some Nagios host/services/user add & deletes.

Not sure how deleting temp files can be caused by a lack of space or a download problem. Does the upgrade process create a more verbose log other than the one displayed in the GUI? Maybe that could provide more information on the specific problem? Or, can you provide any insight as to why the process would hang on deleting temp files.

Hi @mkeey,

What you see in the output on the Updates page is what is stored in the upgrade log. After you get the "Cleaning up temp directory" message, it will download and unpack the latest version and kick off the upgrade script. You can look at the upgrade script for possible sources, but it's a communication issue between the GUI and upgrade script.

As mentioned, the developers are aware of the issue, and in the meantime if your GUI update is not working, please perform the workaround using a manual upgrade.

Thanks.