This section provides the steps required for a successful upgrade from Zabbix 3.4.x to Zabbix 4.0.x using official Zabbix sources.
While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the same major version. Therefore, in a server-proxy setup, Zabbix 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 Zabbix server and then stop, upgrade and start Zabbix proxies one after another. When all proxies are upgraded, start Zabbix server. During the Zabbix server downtime, running proxies will keep collecting and storing data and will pass the data to Zabbix server when the server is up and running. Any notifications for problems during Zabbix 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.
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 Zabbix 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 Zabbix server/frontend;
Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;
'libpcre' and 'libevent' libraries mandatory for Zabbix server;
Exit code checks added for user parameters, remote commands and system.run items without the 'nowait' flag as well as Zabbix server executed scripts;
Zabbix 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|
|2.4.x||Also for 3.0||Minimum required PHP version upped from 5.3.0 to 5.4.0
LogFile agent parameter must be specified
|2.2.x||Also for 2.4||Node-based distributed monitoring removed|
|2.0.x||Also for 2.2||Minimum required PHP version upped from 5.1.6 to 5.3.0;
Case-sensitive MySQL database required for proper server work; character set utf8 and utf8_bin collation is required for Zabbix server to work properly with MySQL database. See database creation scripts.
'mysqli' PHP extension required instead of 'mysql'
You may also want to check the requirements for 4.0.
tail -f zabbix_server.logor
tail -f zabbix_proxy.login the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances.
Stop Zabbix server to make sure that no new data is inserted into 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).
Make a backup copy of Zabbix binaries, configuration files and the PHP file directory.
Use these instructions to compile Zabbix server from sources.
See the upgrade notes for details on mandatory changes.
For new optional parameters, see the What's new section.
Start new binaries. Check log files to see if the binaries have started successfully.
Zabbix server will automatically upgrade the database. When starting up, Zabbix server reports the current (mandatory and optional) and required database versions. If the current mandatory version is older than the required version, Zabbix server automatically executes the required database upgrade patches. The start and progress level (percentage) of the database upgrade is written to the Zabbix server log file. When the upgrade is completed, a “database upgrade fully completed” message is written to the log file. If any of the upgrade patches fail, Zabbix server will not start. Zabbix server will also not start if the current mandatory database version is newer than the required one. Zabbix server will only start if the current mandatory database version corresponds to the required mandatory version.
8673:20161117:104750.259 current database version (mandatory/optional): 03040000/03040000 8673:20161117:104750.259 required mandatory version: 03040000
Before you start the server:
The minimum required PHP version is 5.4.0. Update if needed and follow installation instructions.
After the upgrade you may need to clear web browser cookies and web browser cache for the Zabbix web interface to work properly.
Stop Zabbix proxy.
Make a backup copy of the Zabbix proxy binary and configuration file.
Use these instructions to compile Zabbix proxy from sources.
Start the new Zabbix proxy. Check log files to see if the proxy has started successfully.
Zabbix proxy will automatically upgrade the database. Database upgrade takes place similarly as when starting Zabbix server.
Stop Zabbix agent.
Make a backup copy of the Zabbix agent binary and configuration file.
Use these instructions to compile Zabbix agent from sources.
Alternatively, you may download pre-compiled Zabbix agents from the Zabbix download page.
There are no mandatory changes in this version to agent parameters.
Start the new Zabbix agent. Check log files to see if the agent has started successfully.
When upgrading between minor versions of 4.0.x (for example from 4.0.1 to 4.0.3) it is required to execute the same actions for server/proxy/agent as during the upgrade between major versions. The only difference is that when upgrading between minor versions no changes to the database are made.