Upgrade Ezeelogin Jump server to the latest version
Upgrade Ezeelogin jump server on Primary / Master Node
If you are running Version 5.x.x, you would first need to upgrade to Version 6.0.x before upgrading to Version 7.0.x.
- To upgrade to Version 6.0.x, download 6.0.0 and upgrade to Version 6.0.0 first.
If you are already running Version 6.x.x, you would first need to upgrade to Version 7.0.x before upgrading to Version 7.1.6
- Once you have upgraded to Version 7.0.0, download version 7.10.0 or latest from the cusomer portal .
Download the ezeelogin package corresponding to your php version.
|For PHP version 7.1 and above (recommended):||https://downloads.ezeelogin.com/ezlogin_7.10.0_php71.bin|
|For PHP version 5.6 to 7.0 (deprecated):||https://downloads.ezeelogin.com/ezlogin_7.10.0_php56-70.bin|
|For PHP version 5.3 to 5.5 (end of life):||https://downloads.ezeelogin.com/ezlogin_7.10.0_php53-55.bin|
If you are already running Version 7.10.x ,you can upgrade to latest Version
Check out the latest system requirements
You are required to upgrade your Ioncube encoder to the latest version 6 and above. Refer the following article to upgrade Ioncube to the latest.
It is recommended to have the secondary node configured and synchronized (cluster setup) to ensure that we can still login to servers via the secondary node and not locked out in the event of an unsuccessful upgrade.
Backup current Ezeelogin installation
Execute the following script on your server to generate a backup of your installation so that you can restore the backup in case the upgrade breaks.Run /usr/local/sbin/backup_ezlogin.php -help for help menu.
[root@gateway ~]# /usr/local/sbin/backup_ezlogin.php -nologs
By default, the backup archives are created in /var/ directory. To change the destination directory, use
[root@gateway ~]#php /usr/local/sbin/backup_ezlogin.php -out /backup_directory/
This would create a executable archive of your ezeelogin installation in /var/ezlogin_backup_v6.2.0_b167_Fri_Mar_02_2012_04_23_22_CST.bin
Execute the backup bin file to restore if something goes wrong and you would like to revert.
Ok, now that we have the backups ready, let go ahead with the update on the primary node as follows, preferably in screen
Upgrading Ezeelogin jump server
To upgrade ezeelogin, download and run the ezeelogin setup file as follows
root@gateway:~$ sh ezlogin_7.x.x.bin -- -update
Follow the onscreen prompts to complete the upgrade.
To upgrade in one step with your existing settings and without being prompted. Be ready with mysql root password if not in /root/.my.cnf
sh ezlogin_7.15.0._x_x.bin -- -skipgeolite -auto -force -ACCEPT_SETTINGS -I_ACCEPT_EULA -update
To upgrade in one step and to prevent the backup_ezlogin.php script from generating a backup again. Be ready with mysql root password if not in /root/.my.cnf
sh ezlogin_7.15.0._x_x.bin -- -skipgeolite -auto -force -ACCEPT_SETTINGS -I_ACCEPT_EULA -skipbackup -update
Login into the GUI, ezsh shell and remote servers to ensure that primary node has been upgraded successfully.
Restoring Ezeelogin jump server from backup
If something is broken after the upgrade, no worries. We will restore the backup from the archive that was created. You would first need to uninstall the current installation on the gateway. Run the following script to uninstall
Now that we have uninstalled, we can go ahead restore the binary backup archive that was created.
Increase php memory in /etc/php.ini if backup restoration fails without any reasons. Do check /var/log/ezlogin_restore.log for errors.
Upgrading Ezeelogin jump server on the Secondary Node
Unfortunately, the secondary nodes needs to be re-installed and we are working toward a seamless secondary upgrade as well.
Before uninstalling the slave node make sure to take the back up of log files. You can take the backup of log files by running : cp -pr /var/log/ezlogin/ /root/ezlogin_logs_backup_16_Wed_Mar_2020
On the secondary node do the following to set it up again.
- Uninstall ezeelogin with following command
- Download the same package used for the primary
Refer the following article to setup secondary node.