Updating the TIBCO LogLogic^® Appliance by Using File Update

The bz2 and bz2.sig files are required to perform file update process.

1. Back up the data on the TIBCO LogLogic^® appliance. For more information about backing up your data, see the TIBCO LogLogic^® Log Management Intelligence Administration Guide.
2. Log in to the TIBCO Support website 
https://support.tibco.com, and then download the latest software update that you want to apply to the appliance.
3. Verify that the appliance has sufficient available disk space to perform the upgrade (see the disk space requirement for partitions explained previously):
   1. Log in to the appliance through SSH and type the command: df -h.
   2. Look at the available space under the Available column.
4. Connect to the LogLogic appliance from the CLI or shell login. Use the command line through the serial port with a null modem cable or by using SSH.
   It is recommended to use the serial port; by using SSH, the connection is lost after the final reboot.

   The default user is toor, log in by using the toor password, which was created during Setting up Appliance Using the Console.

5. Make sure that the system is ready for upgrade by running the health check command healthcheck.sh with the correct path. For example:

   /loglogic/update/healthcheck/healthcheck.sh

   Note:

   1. During this process, if system finds any inconsistencies, the console displays the message: Ignore the inconsistency?[yes/no]:Type no to stop the process and go back and fix the issue before you proceed. You can run the health check command multiple times until you fix all inconsistencies. If you type yes, all inconsistencies are ignored and you can proceed.
   2. During this process, the console might prompt the following message to warn you about unconverted report data from previous upgrade process: There is report data on the system that was not converted after the last upgrade. Do you want to convert this data now? [yes/no]:Type yes to exit the health check command at this point and run the rundbm command to complete the post-upgrade process from the previous upgrade. Otherwise, type no to ignore this warning and proceed. 

   3. During this process, the health check might fail with the following error, Schema consistency checking failed. 
If this occurs use the following workaround. In mysql:

      use logappconfig
      alter table oddsfieldtags drop FOREIGN KEY oddsfieldtags_ibfk_1;
      alter table oddsfieldtags drop index msgPatternId;
      alter table oddsfieldtags add index oddsfieldtags_ibfk_1(msgPatternId);
      alter table oddsfieldtags add constraint oddsfieldtags_ibfk_1 FOREIGN KEY (msgPatternId) REFERENCES oddsmessagepattern(uuid) ON DELETE CASCADE;

   4. During this process, the health check might fail and the following error might be displayed: Data Vault is turned on but auto-unlock is not enabled.. If this occurs, use the system command system data_vault enable_auto_unlock to enable the automatic unlocking of the data vault.
   5. During this process, the health check might fail and the following warning might be displayed: WARNING: Advanced Features may not perform correctly with the current memory configuration on LMI 6.2.0 and above! Do you want to continue upgrade? [yes/no] This is because Advanced Features is enabled on the appliance but the configured memory is less than 32 GB. If this occurs, type yes to continue, or disable the Advanced Features, or configure more memory on the appliance.

   


6. Log in to the TIBCO LogLogic^® appliance you want to upgrade. You must log in as a user with Administrator privileges.
7. In the navigation menu, click Administration > File Update.
   The File Update tab is displayed.
8. From the Select File drop-down menu, select the appropriate software update.
   If you do not see any files in the list, verify that the update files are added to the /loglogic/update directory.
9. Click Update.
   A status message appears at the top of the File Update tab after the update is complete.
10. After the appliance reboots, run the Post Upgrade script.
11. (Optional) If you want to update the SSL signature algorithm to sha2, run the script: /loglogic/tomcat/conf/cert_utils/certgen.sh.