Table of Contents
- 2 Debian/Ubuntu
- Overview
- Upgrade procedure
- 1 Stop Áú»¢¶Ä²© processes
- 2 Back up the existing Áú»¢¶Ä²© database
- 3 Back up configuration files, PHP files and Áú»¢¶Ä²© binaries
- 4 Update repository configuration package
- 5 Upgrade Áú»¢¶Ä²© components
- 6 Review component configuration parameters
- 7 Start Áú»¢¶Ä²© processes
- 8 Clear web browser cookies and cache
- Upgrade between minor versions
2 Debian/Ubuntu
Overview
This section provides the steps required for a successful upgrade from Áú»¢¶Ä²© 3.4.x to Áú»¢¶Ä²© 4.0.x using official Áú»¢¶Ä²© packages for Debian/Ubuntu.
While upgrading Áú»¢¶Ä²© agents is not mandatory (but recommended), Áú»¢¶Ä²© server and proxies must be of the same major version. Therefore, in a server-proxy setup, Áú»¢¶Ä²© server and all proxies have to be stopped and upgraded.
To minimize downtime and data loss during the upgrade, it is recommended to stop and upgrade Áú»¢¶Ä²© server and then stop, upgrade and start Áú»¢¶Ä²© proxies one after another. When all proxies are upgraded, start Áú»¢¶Ä²© server. During the Áú»¢¶Ä²© server downtime, running proxies will keep collecting and storing data and will pass the data to Áú»¢¶Ä²© server when the server is up and running. Any notifications for problems during Áú»¢¶Ä²© server downtime will be generated only after the upgraded server is started.
Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.
Depending on database size the database upgrade to version 4.0 may take a long time.
Before the upgrade make sure to read the relevant upgrade notes!
The following upgrade notes are available:
| Upgrade from | Read full upgrade notes | Important notes/changes between versions |
|---|---|---|
| 3.4.x | For 4.0 | 'libpthread' and 'zlib' libraries now mandatory; Support for plain text protocol dropped and header is mandatory; Pre-1.4 version Áú»¢¶Ä²© agents are no longer supported; The Server parameter in passive proxy configuration now mandatory |
| 3.2.x | Also for 3.4 | SQLite support as backend database dropped for Áú»¢¶Ä²© server/frontend; Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended; 'libpcre' and 'libevent' libraries mandatory for Áú»¢¶Ä²© server; Exit code checks added for user parameters, remote commands and system.run[] items without the 'nowait' flag as well as Áú»¢¶Ä²© server executed scripts; Áú»¢¶Ä²© Java gateway has to be upgraded to support new functionality |
| 3.0.x | Also for 3.2 | Database upgrade may be slow, depending on the history table size |
You may also want to check the requirements for 4.0.
It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run tail -f zabbix_server.log or tail -f zabbix_proxy.log in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances.
Upgrade procedure
1 Stop Áú»¢¶Ä²© processes
Stop Áú»¢¶Ä²© server to make sure that no new data is inserted into database.
If upgrading Áú»¢¶Ä²© proxy, stop proxy too.
It is known to be possible to upgrade the server only and have older and unupgraded proxies report data to a newer server (the proxies can't refresh their configuration though). This approach, however, is not recommended and not supported by Áú»¢¶Ä²© and choosing it is entirely at your own risk.
2 Back up the existing Áú»¢¶Ä²© database
This is a very important step. Make sure that you have a backup of your database. It will help if the upgrade procedure fails (lack of disk space, power off, any unexpected problem).
3 Back up configuration files, PHP files and Áú»¢¶Ä²© binaries
Make a backup copy of Áú»¢¶Ä²© binaries, configuration files and the PHP file directory.
Configuration files:
# mkdir /opt/zabbix-backup/
# cp /etc/zabbix/zabbix_server.conf /opt/zabbix-backup/
# cp /etc/apache2/conf-enabled/zabbix.conf /opt/zabbix-backup/PHP files and Áú»¢¶Ä²© binaries:
4 Update repository configuration package
To proceed with the update your current repository package has to be uninstalled.
Then install the new repository configuration package.
On Debian 9 run:
# wget https://repo.zabbix.com/zabbix/4.0/debian/pool/main/z/zabbix-release/zabbix-release_4.0-2+stretch_all.deb
# dpkg -i zabbix-release_4.0-2+stretch_all.debOn Debian 8 run:
# wget https://repo.zabbix.com/zabbix/4.0/debian/pool/main/z/zabbix-release/zabbix-release_4.0-2+jessie_all.deb
# dpkg -i zabbix-release_4.0-2+jessie_all.debOn Ubuntu 18.04 run:
# wget https://repo.zabbix.com/zabbix/4.0/ubuntu/pool/main/z/zabbix-release/zabbix-release_4.0-2+bionic_all.deb
# dpkg -i zabbix-release_4.0-2+bionic_all.debOn Ubuntu 16.04 run:
# wget https://repo.zabbix.com/zabbix/4.0/ubuntu/pool/main/z/zabbix-release/zabbix-release_4.0-2+xenial_all.deb
# dpkg -i zabbix-release_4.0-2+xenial_all.debOn Ubuntu 14.04 run:
# wget https://repo.zabbix.com/zabbix/4.0/ubuntu/pool/main/z/zabbix-release/zabbix-release_4.0-2+trusty_all.deb
# dpkg -i zabbix-release_4.0-2+trusty_all.debUpdate the repository information.
5 Upgrade Áú»¢¶Ä²© components
To upgrade Áú»¢¶Ä²© components you may run something like:
If using PostgreSQL, substitute mysql with pgsql in the command. If upgrading the proxy, substitute server with proxy in the command.
6 Review component configuration parameters
See the upgrade notes for details on mandatory changes.
For new optional parameters, see the What's new section.
7 Start Áú»¢¶Ä²© processes
Start the updated Áú»¢¶Ä²© components.
8 Clear web browser cookies and cache
After the upgrade you may need to clear web browser cookies and web browser cache for the Áú»¢¶Ä²© web interface to work properly.
Upgrade between minor versions
It is possible to upgrade minor versions of 4.0.x (for example, from 4.0.1 to 4.0.3). It is easy.
To upgrade Áú»¢¶Ä²© minor version please run:
To upgrade Áú»¢¶Ä²© server minor version please run:
To upgrade Áú»¢¶Ä²© agent minor version please run: