Troubleshoot Upgrades

Beginning with Fusion 3.1, upgrading Fusion uses a migrator that migrates objects and data from your current version of Fusion to a new version of Fusion or Fusion Server.

The Fusion migrator log file will help you troubleshoot difficulties while upgrading. If the migrator fails to complete successfully, we explain how to correct problems and repeat an upgrade.

Known issues, and workarounds if available, are listed at the bottom of this topic.

Log file

The log file for the migrator is in /opt/fusion/x.y.z/var/upgrade/tmp/migrator.log (on Unix) or C:\lucidworks\var\fusion\x.y.z\upgrade\tmp\migrator.log (on Windows). The x.y.z directory is for the Fusion version that you are migrating from.

Completing an upgrade after an error

If the migrator script produces an error, you will need to correct the problem that the script encountered, and then finish the upgrade as explained here.

1. Fix the error

If an upgrade step fails:

  1. Examine the log file and determine what went wrong.

  2. Fix what went wrong.

2. Repeat the step that failed

After you have fixed the source of the error, repeat the step that failed.

Note
You can repeat the step that failed as many times as needed to correct errors that occur. If the step continues to fail, restart the upgrade from the beginning.

3. Complete the upgrade

Complete the upgrade.

If a different step fails, fix that error, repeat that step, and then perform the remainder of the upgrade procedure.

If the upgrade steps produce no additional errors, then you are finished.

Restarting an upgrade

If an upgrade step continues to fail, then restart the upgrade process from the beginning:

  1. Examine the log file and determine what went wrong.

  2. Remove the directory for the new version of Fusion.

  3. Reinstall the new version of Fusion, but don’t start it.

  4. Fix what went wrong.

  5. Perform the entire upgrade procedure from the beginning.

Known issues

Following are known issues with the Fusion migrator when using it to upgrade to Fusion 3.1.y.

Upgrades affected Issue Workaround (if available)

3.0.x to 3.1.0

The migrator fails when run with the argument -5.

Open a file explorer, navigate to /opt/fusion/3.1.0/apps/connectors/bootstrap-plugins (on Unix) or C:\lucidworks\fusion\3.1.0\apps\connectors\bootstrap-plugins (on Windows), and add -3.1.0 before the file extension (.zip) for all of the files in that directory. For example, the modified lucid.file.zip filename would be lucid.file-3.1.0.zip. Then rerun the migrator step that failed.

3.0.x to 3.1.0 and 3.1.x to 3.1.y

The managed-schema data in the Solr configuration can’t exceed 1 MB in size.

This is an example of a failure message:

2018-05-07T19:31:00,056 - ERROR [main:ZKImportExportComponent@276] - Error writing data to ZK org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /lwfusion/3.1.5/solr/configs/rh/managed-schema

Remove unneeded elements from the schema, and restart the upgrade from the beginning.