Complete Guide to Updating GLPI
If you are using a version of GLPI that is lower than the current (latest) version, and you want to update your GLPI installation to take advantage of new features and corrections, this article is for you. <note> It is necessary to increase your memory_limit and timeout values in your php.ini configuration. The update process temporarily requires more resources. You can put the memory_limit and timeout values back to their original settings after the update is complete. </note>
<note> You need to disable the plugins before updating GLPI and make sure they are compatible with the new version you install. </note>
Save your old configuration
Above all you should do the following:
- Back up your database via backup GLPI.
- Save ALL GLPI directories (this should contain the backup of your SQL and your documents).
From there, if the update does not go as planned or that new implementations of the latest version does not suit you, it will be easy to go back to your previous version.
If you have problems, you can get help from the mailing lists or forum on the project site, or on the bugtracker. Be sure to include the following information with any help request:
- Your server's operating system, PHP version, and MySQL version
- GLPI version (original, and updated)
- Step by step actions during the update process (take notes as you go)
- The error message(s) you get
Recovery and installation files
First, download the archive of the latest version available in the download section of the project site glpi (http://glpi-project.org).
When updating a GLPI version < 0.68 to a version >= 0.68:
- Save all of your GLPI directory and delete it.
- Unpack the new archive GLPI
- Some directories have changed. You need to copy their contents
- old_installation_GLPI/backup/dump → new_installation_glpi/files/_dumps
- old_installation_GLPI/docs/ → new_installation_glpi/files
- Check or change the rights on the following folders:
- so that the web server user (apache) can write to those folders/directories.
When updating a GLPI version >= 0.68 to a higher version (eg 0.7x)
- Unpack the new GLPI version, simply replace the old files.
Launch the updated version
- Point your web browser on yourserver/glpi/
- Select the language in which you want to update and click “ok”.
- Click on “update”.
- Verify that all of the requirements on the check environment page are satisfied, otherwise follow the instructions and re-try.
- If everything went well, click “continue”.
- Configure the server to access the MySQL database.
- Mysql server: the host name of the database server, either localhost, or the IP address if it is a remote server; mysql user: MySQL username; MySQL pass: the password associated with the MySQL user
- Once all this is done click “continue”
- Select the database you want to update. Click on “continue”
- A popup screen will ask you if you are sure you want to update your database, click “continue” to perform the update.
- The update begins, it may take some time depending on the size of your database.
- Depending on the version of GLPI you are updating a number of intermediate screens will be offered. Answer the questions based on your organization.
- The script will ask you now to update the old content from your database.
<note> After clicking “Continue” a progress bar appears on your screen. Depending on the size of your database this process may be very long (several minutes or even hours) and sometimes the progress bar will stay at 0% for a long time. </note>
If the update procedure was successful, you can now use your new version of GLPI by clicking on “Use GLPI” and logging in as the usual user.
Upgrading a GLPI version < 0.4
The upgrade from a GLPI version lower than version 0.4 does not allow you to automatically preserve your specific configurations (General Configurations, External Sources, Mail Settings, etc.) that were stored in the config.php file.
You will need to use the post-installation configuration forms in the “configuration” menu of GLPI.
These menus are only accessible to a new type of user (only in GLPI versions >= 0.68) called the “super-admin”.
The update will therefore automatically convert “admin” users to “super admin” users or you can create a “super-admin” user.
At this point, several cases are possible depending on the version from which you updated, and your old configurations.
CASE 1: You had at least one “admin” type user that does not authenticate from external sources (ldap, imap) (users that authenticate from external sources do not store the password in the database).
All of your previous “admin” users with local authentication will be converted to “super admin” users.
Your database is updated, you can now configure GLPI by clicking on “use GLPI” and logging in as one of the former admin users.
CASE 2: You did not have users type “admin” or all “admin” has a blank password (as they are authenticated from an external source).
The script asks you to enter a username and one password (do not enter a user name that already exists).
The next step
If this process is successfull, your database is now updated and you can configure GLPI by clicking on “use GLPI” and logging in as the user you just created.
Once the setup is complete, you can delete the user.
<note warning> Make sure there is at least one “super admin” user with the ability to authenticate locally (password stored in GLPI), in the event of problems with external authentication sources. </note>