Upgrading an RPM installation
Contents
If you do not yet have the RPM file downloaded, please see our Downloads and Links page
If you don't yet have an installation, please follow the Installing with an RPM guide
Introduction
Upgrading the idenprotect applications works in a very similar way to doing the initial installation, except your configuration will remain untouched during an upgrade.
Upgrading
Upgrade Order
If you are upgrading all of the applications, please follow the same installation order as follows: -
- idenprotect Core Platform
- idenprotect Authentication Portal
- idenprotect User Portal
- idenprotect Active Directory Agent
Upgrading the RPM
- Place the RPM file in a directory on your server (you can do this using SCP or by directly downloading using something like wget)
- Using an account with root privileges, navigate to the directory and run the following command
yum --nogpgcheck localinstall packagename.rpm
Where packagename is the rpm you are upgrading, eg idenprotect-server-1.3.2-116b.el7.noarch.rpm
- Accept the changes and updates and the idenprotect software should upgrade
Known Upgrade Issues
If upgrading from a previous version that uses an older version of MariaDB it may be necessary to manually enable the new MariaDB service by using the following commands: -
chkconfig mariadb on service mariadb start
or for Centos 7
systemctl enable mariadb.service systemctl start mariadb
Next Steps
During the RPM upgrade process, it is normal to see some errors reported. You can verify if the upgrade has been successful by following the steps found in Verifying an RPM installation
