Follow

Troubleshooting migration process to 3.0

Applies to platform: UTM 2.5.X
Updated on: 30th June 2014

Warning: NEVER FORCE A REBOOT!

If for any reason the upgrade process does not finish successfully or it seems to be stuck, DO NOT forcibly reboot your Endian UTM Appliance, but make sure all the configuration have been migrated, by running the run-parts command mentioned in the "Upgrade process" section below.
This lesson shows solutions to issues arisen during the upgrade process to Endian UTM Appliances version 2.5. The upgrade process is described in this lesson.

Troubleshooting the Upgrade Process

In rare cases, the upgrade process may not end correctly. The areas that might be interrested by some problem are: The upgrade process itself (for example due to a network failure), the hotspot, the Endian Management Interface, and the synchronisation with Endian Network. Solution for those problem are listed below.

Upgrade process

In case the upgrade process does not start, you can force it by opening the SSH console and running:

root@endian:~# efw-update update && efw-update upgrade

This will restart the whole process. After that, run the following command to make sure all the post-upgrade script are executed:

root@endian:~# run-parts /etc/upgrade/upgrade.d/

Hotspot

The Hotspot Administration interface is not working.
From an SSH or Console session, run the following command:

root@endian:~# jobcontrol restart hotspot --force

Hotspot users and/or open sessions are not working?
From an SSH or Console session, run the following commands:

root@endian:~# jobcontrol call hotspot.fix

If this doesn’t correct the issue, please run the following command:

root@endian:~# jobcontrol call hotspot.rebuild

To test whether Hotspot authentication is working properly, run this command:

root@endian:~# hotspot-commandline -t

If you experience some issue with the hotspot database, run the following command to ensure it is migrated corectly:

root@endian:~# jobcontrol restart hotspot --force --migratedb --debug

Endian Management Interface (EMI)

EMI is not accessible anymore
From an SSH or Console session, run the following commands (in order):

root@endian:~# jobcontrol restart emi

Endian Netwok

If the system appears as offline on the Endian Network, issue the following command from the console:

root@endian:~# jobcontrol restart enclient

I have an issue that is not covered in this lesson!

 In the unlikely case that an issue arises, that has not been mentioned in this lesson, contact immediately your Endian Partner or Reseller to notify of the problem or contact Endian by opening a support ticket.
This document will be updated with new information, should some issue arise.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments