Debugging a hung upgrade

You must debug an upgrade if a failed task causes that upgrade to hang or stop.

If a new Secure Shell (SSH) session displays the UPGRADE IN PROGRESS message but does not display any additional output, a failed task causes the upgrade to stop.

To identify the cause for the upgrade to stop, issue this command:

tail -n 200 /opt/ibm/metaocean/logs/upgrade.log

After you fix any issues identified in the upgrade log, reboot and then restart the upgrader. Use the systemctl command to restart the upgrader:

[root@ ~]# systemctl start upgrader

The upgrader output is not displayed in the console after you restart the upgrader. Either use the tail of the /opt/ibm/metaocean/logs/upgrade.log file or reconnect your SSH connection to automatically see the progress.

If the upgrader does not restart when you upgrade from a same-level version, run the upgrade command again:

[root@ metaocean]# ./upgrade