When attempting to upgrade LMI 6.2.0 to any future supported version the upgrade can fail very early in the process before the first reboot occurs. The error indicating the upgrade failed is displayed in the File Update page but nothing is displayed regarding the cause. One of the symptoms is that the text field that shows the various stages of the upgrade will not display any progress text, such as when the authenticity of the upgrade file is being verified. If you don't see any of this output in the text field then it's an indicator the upgrade will fail. It may take 10-15 minutes before the upgrade process actually fails.



In contrast, when the upgrade process is functioning correctly you should instead see a status like that shown in the following screenshot:

 

Install 6.2.0 HF2 to resolve this issue. After HF2 is installed initiate the file update again. Having HF2 for 6.2.0 is a pre-requisite for upgrading to future LMI versions when upgrading from 6.2.0. If you can't install HF2 then an available workaround is to initiate the upgrade using the CLI command system update as root (not toor). If you are already logged in as toor because you were running commands like healthcheck to prepare for the GUI-based upgrade then simply run the su command and then you can initiate the CLI-based upgrade because all the upgrade files should still be in place. See the output below:

Logapp root:/loglogic/update 0$ su

LogAppliance MXVirtual

(c)2002-2018 TIBCO Software Inc.
Version 6.2.0


Status: RUNNING

Type 'help' or '?' for a list of commands.

> system update
Choose an update file from the list:
0: update-201806181135-full.tar.bz2
1: exit
>> 0
Extracting update.

 

A known issue with the file update process causes upgrades to fail. This article explains the symptoms, solution and also an available workaround.