Zabbix Documentation 5.0

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


manual:installation:upgrade_notes_500

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
manual:installation:upgrade_notes_500 [2020/04/14 09:31]
martins-v 'dropdown first entry' option removed (ZBXNEXT-5702)
manual:installation:upgrade_notes_500 [2020/06/10 14:25]
martins-v ↷ Links adapted because of a move operation
Line 1: Line 1:
 ==== 9 Upgrade notes for 5.0.0 ==== ==== 9 Upgrade notes for 5.0.0 ====
- 
-​<note important>​Zabbix 5.0.0 is not released yet.</​note>​ 
  
 These notes are for upgrading from Zabbix 4.4.x to Zabbix 5.0.0. All notes are grouped into: These notes are for upgrading from Zabbix 4.4.x to Zabbix 5.0.0. All notes are grouped into:
Line 20: Line 18:
 === Support of IBM DB2 dropped === === Support of IBM DB2 dropped ===
  
-The IBM DB2 database ​is no longer ​supported by Zabbix.uu+The IBM DB2 database ​can no longer ​be used as a back-end database for Zabbix.
  
 === Support of Internet Explorer 11 dropped === === Support of Internet Explorer 11 dropped ===
Line 38: Line 36:
   * Oracle 11.2   * Oracle 11.2
  
-=== Enable extended range of Numeric (float) values ​===+=== Upgrade with MariaDB 10.2.1 and before ​===
  
-Numeric (float) data type now supports precision of approximately 15 digits and range from approximately -1.79E+308 to 1.79E+308 (with exception of [[:​manual/​installation/​known_issues#​floating_point_values|PostgreSQL 11 and earlier versions]]). This is by default for new installations. However, when upgrading existing installations,​ a manual database upgrade patch must be applied. The patch will alter data columns of history and trends tables, which usually contain lots of data, therefore it is expected to take some time to complete. Since the exact estimate depends on server performance,​ database management system configuration and version, and it cannot be predicted, it is recommended to first test the patch outside the production environment.+Upgrading Zabbix may fail if database tables were created with MariaDB 10.2.1 and before, because in those versions the default row format is compact. This can be fixed by changing the row format to dynamic (see also [[https://​support.zabbix.com/​browse/​ZBX-17690|ZBX-17690]]). 
 + 
 +=== Enabling extended range of numeric (float) values === 
 + 
 +Numeric (float) data type now supports precision of approximately 15 digits and range from approximately -1.79E+308 to 1.79E+308 (with exception of [[:​manual/​installation/​known_issues#​floating_point_values|PostgreSQL 11 and earlier versions]]). This is by default for new installations. However, when upgrading existing installations,​ a manual database upgrade patch must be applied. 
 + 
 +If you do not apply the patch, [[:​manual/​web_interface/​frontend_sections/​reports/​status_of_zabbix|System information]] in the frontend will display: %%"​%%Database history tables upgraded: No%%"​%%. 
 + 
 +<note important>​The patch will alter data columns of history and trends tables, which usually contain lots of data, therefore it is expected to take some time to complete. Since the exact estimate depends on server performance,​​ database management system configuration and version, and it cannot be predicted, it is recommended to first test the patch outside the production environment.</​note>​
  
 Please execute the appropriate patch (SQL file) for your database: Please execute the appropriate patch (SQL file) for your database:
Line 46: Line 52:
   * database/​postgresql/​double.sql   * database/​postgresql/​double.sql
   * database/​oracle/​double.sql   * database/​oracle/​double.sql
 +
 +Note that when upgrading using packages, you may find these scripts in the Zabbix Git repository for:
 +  * [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​raw/​database/​mysql/​double.sql|MySQL]]
 +  * [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​raw/​database/​postgresql/​double.sql|PostgreSQL]]
 +  * [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​raw/​database/​oracle/​double.sql|Oracle]]
 +
 +<note warning>​Important!\\ * Run these scripts for the server database only.\\ * Make sure Zabbix server is stopped before running these scripts. Restart the server afterwards.</​note>​
  
 Note that with TimescaleDB the [[:​manual/​appendix/​install/​timescaledb#​timescaledb_compression|compression support]] must only be turned on after applying this patch. Note that with TimescaleDB the [[:​manual/​appendix/​install/​timescaledb#​timescaledb_compression|compression support]] must only be turned on after applying this patch.
 +
 +<​note>​After upgrading database tables, please also set or update $DB['​DOUBLE_IEEE754'​] value to true in /​ui/​conf/​zabbix.conf.php.</​note>​
 +
 +=== Non-root permissions implemented for Docker images ===
 +
 +Zabbix Docker images have been updated to implement non-root container best practices. Due to the change:
 +
 +  * All directories have been restricted for the container user, except directories which are required for the container. For example, /​etc/​zabbix/​ with Zabbix component configuration files.
 +  * Ports 80 and 443 have been changed to 8080 and 8443, because usage of all ports <1024 is restricted for non-privileged users.
 +
 +A known issue: Nginx based images do not run under root. Will be fixed soon.
  
 ==== Informational ==== ==== Informational ====
 +
 +=== Changed Zabbix PHP file directory ===
 +
 +The downloaded Zabbix frontend PHP files are now located in the ui directory instead of frontends/​php. This is relevant when using Zabbix sources for the installation.
 +
 +=== Changed acknowledgement screen URL ===
 +
 +URL parameters of the problem update (acknowledgement) screen have changed. For example, if previously the page parameters were:
 +
 +  ?​action=acknowledge.edit&​eventids[]=100
 +
 +in the new version they are:
 +
 +  ?​action=popup&​popup_action=acknowledge.edit&​eventids[]=100
 +
 +In a related development,​ when successfully updating a problem from a dashboard widget, only the widget gets reloaded, not the whole page. So the content of another widget displaying the same problem will remain unchanged until the next scheduled widget refresh or complete page refresh.
 +=== No data triggers sensitive to proxy availability ===
 +
 +No data triggers are now, by default, sensitive to [[:​manual/​introduction/​whatsnew500#​no_data_triggers_sensitive_to_proxy_availability|proxy availability]].
  
 === Fullscreen mode replaced by hiding menu === === Fullscreen mode replaced by hiding menu ===
  
-The fullscreen mode has been removed from the Monitoring sections of the frontend. The same effect (showing only page title and content) now can be achieved by hiding the new [[:​manual/​web_interface/​menu|vertical menu]]. The kiosk mode (page content only, no page title at all) remains.+The fullscreen mode has been removed from the Monitoring sections of the frontend. Frontend URLs containing '​fullscreen'​ will work no more. The same effect (showing only page title and content) now can be achieved by hiding the new [[:​manual/​web_interface/​menu|vertical menu]]. The kiosk mode (page content only, no page title at all) remains.
  
 === Option for dropdown first entry removed === === Option for dropdown first entry removed ===
Line 61: Line 104:
 === Configuration parameters === === Configuration parameters ===
  
-The EnableRemoteCommands parameter is now deprecated. Remote commands are still disabled by default, but in the new configuration files that is expressed by using the new DenyKey parameter (''​DenyKey=system.run[*]''​)Remote ​commands ​can be enabled by removing (or commenting ​out) ''​DenyKey=system.run[*]''​ parameter.+EnableRemoteCommands ​agent [[:​manual/​appendix/​config/​zabbix_agentd|parameter]] is still supported (it may get deprecated and removed ​in the future) alongside ​the new [[manual:​config:​items:​restrict_checks|DenyKey/​AllowKey]] parametersWhen upgrading existing agents, remote ​commands ​will not be allowed unless you:  
 + 
 +  * Set EnableRemoteCommands=1  
 +  * Remove ​or comment ​out DenyKey=system.run[*] 
 + 
 +In this case remote commands will be allowed without restrictions. To create restrictions,​ use a combination of AllowKey and DenyKey parameters.
  
 === Item key limit === === Item key limit ===
Line 70: Line 118:
  
 It is now possible to manually clear the SNMP cache on Zabbix server and proxy. Due to adding a new runtime control [[:​manual/​concepts/​server#​running_server|option]],​ Net-SNMP version 5.3.0 or higher is now required for SNMP support. It is now possible to manually clear the SNMP cache on Zabbix server and proxy. Due to adding a new runtime control [[:​manual/​concepts/​server#​running_server|option]],​ Net-SNMP version 5.3.0 or higher is now required for SNMP support.
- + 
 +=== Redis plugin update === 
 +Configuration parameter ''​Plugins.Redis.Password''​ was removed and an opportunity to pass a password as a key parameter has now been added. See [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​src/​go/​plugins/​redis|Redis plugin]] for details.  
 + 
 +=== Supported Elasticsearch versions changed === 
 +Elasticsearch version 7.X is now supported. Support of the older versions has been dropped. ​