Zabbix Documentation 3.4

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:installation:upgrade_notes_340

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
manual:installation:upgrade_notes_340 [2018/02/06 06:42]
martins-v bringing some important entries higher up
manual:installation:upgrade_notes_340 [2019/02/12 06:39] (current)
martins-v formatting change
Line 1: Line 1:
 ==== 10 Upgrade notes for 3.4.0 ==== ==== 10 Upgrade notes for 3.4.0 ====
  
-These notes are for upgrading from Zabbix 3.2.x to Zabbix 3.4.0.+These notes are for upgrading from Zabbix 3.2.x to Zabbix 3.4.0. ​All notes are grouped into: 
 + 
 +  * ''​Critical''​ - the most critical information related to the upgrade process and the changes in Zabbix functionality 
 +  * ''​Informational''​ - all remaining information describing the changes in Zabbix functionality
  
 It is possible to upgrade to Zabbix 3.4.0 from versions before Zabbix 3.2.0. See the [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions. It is possible to upgrade to Zabbix 3.4.0 from versions before Zabbix 3.2.0. See the [[:​manual/​installation/​upgrade|upgrade procedure]] section for all relevant information about upgrading from previous Zabbix versions.
 +
 +==== Critical ====
  
 === Dropping SQLite support for server/​frontend === === Dropping SQLite support for server/​frontend ===
Line 18: Line 23:
  
 ===  Additional dependencies === ===  Additional dependencies ===
-  * libpcre3 ​- the PCRE library is now mandatory when compiling Zabbix server. It is required for [[https://​en.wikipedia.org/​wiki/​Perl_Compatible_Regular_Expressions|Perl Compatible Regular Expression]] (PCRE) support. The naming may differ depending on the GNU/Linux distribution;​+  * libpcre ​- the PCRE library is now mandatory when compiling Zabbix server. It is required for [[https://​en.wikipedia.org/​wiki/​Perl_Compatible_Regular_Expressions|Perl Compatible Regular Expression]] (PCRE) support. The naming may differ depending on the GNU/Linux distribution, for example '​libpcre3'​ or '​libpcre1'​. Note that you need exactly PCRE (v8.x); PCRE2 (v10.x) library is not used;
   * libevent (version 1.4 or later) library is now mandatory: ​   * libevent (version 1.4 or later) library is now mandatory: ​
     * for Zabbix server always;     * for Zabbix server always;
Line 40: Line 45:
  
 Due to command/​script exit code check [[manual/​introduction/​whatsnew340#​return_code_check_for_scripts_and_commands|introduction]] in Zabbix 3.4, [[manual/​config/​notifications/​media/​script|alertscripts]] can be executed multiple times if their exit code is different from 0. Previously configured items with user parameters executed by Zabbix server, external check items, and **system.run** items whose exit code is not 0 may become “Not supported” due to additional checks for exit code; behaviour of the items with "​nowait"​ flag is not changed though. Due to command/​script exit code check [[manual/​introduction/​whatsnew340#​return_code_check_for_scripts_and_commands|introduction]] in Zabbix 3.4, [[manual/​config/​notifications/​media/​script|alertscripts]] can be executed multiple times if their exit code is different from 0. Previously configured items with user parameters executed by Zabbix server, external check items, and **system.run** items whose exit code is not 0 may become “Not supported” due to additional checks for exit code; behaviour of the items with "​nowait"​ flag is not changed though.
 +
 +===  Configuration parameters ===
 +
 +The ''​SenderFrequency''​ [[:​manual/​appendix/​config/​zabbix_server|configuration]] parameter has been removed. It must be removed from server configuration for 3.4 when upgrading, otherwise you will get an error and the server **will not** start. Retry frequency of failed alerts is now looked up in the [[:​manual/​config/​notifications/​media/​email#​options|media type]] configuration (//Attempt interval// parameter) and is 10 seconds by default. The default of SenderFrequency used to be 30 seconds.
  
 === URL-encoding in web scenarios === === URL-encoding in web scenarios ===
Line 50: Line 59:
 If you have already manually URL-encoded values they will be left as is and will not be double URL-encoded. If you have already manually URL-encoded values they will be left as is and will not be double URL-encoded.
  
-===  ​Configuration parameters ​===+=== Upgrading Java gateway === 
 + 
 +Zabbix Java gateway has to be upgraded to support the new functionality of:  
 + 
 +  * [[:​manual/​introduction/​whatsnew340#​configurable_jmx_endpoints|configurable JMX endpoints]];​ 
 +  * [[:​manual/​discovery/​low_level_discovery/​jmx|low-level discovery of JMX objects]]. 
 + 
 +=== JMX item protocol changes === 
 + 
 +An example of the new protocol: 
 + 
 +<​code>​ 
 +{"​request":"​java gateway jmx","​jmx_endpoint":"​service:​jmx:​rmi:///​jndi/​rmi://​127.0.0.1:​12345/​jmxrmi","​keys":​["​jmx[\"​java.lang:​type={#​FSNAME}\",​\"​HeapMemoryUsage.used\"​]"​]} 
 +</​code>​ 
 + 
 +==== Informational ====
  
-The ''​SenderFrequency''​ [[:​manual/​appendix/​config/​zabbix_server|configuration]] parameter has been removed. It must be removed from server configuration for 3.4 when upgrading, otherwise you will get an error and the server will not start. Retry frequency of failed alerts is now looked up in the [[:​manual/​config/​notifications/​media/​email#​options|media type]] configuration (//Attempt interval// parameter) and is 10 seconds by default. The default of SenderFrequency used to be 30 seconds.+=== Configuration parameters ===
  
 A new configuration parameter ''​SocketDir''​ has been added to Zabbix server and proxy configurations. This parameter points to the directory where internal Zabbix socket files are stored (/tmp by default). Server and proxy use different socket file names so it's safe to use the same ''​SocketDir''​ for server and proxy running on the same system. However, running multiple servers or proxies in the same system will require different ''​SocketDir''​ configurations. A new configuration parameter ''​SocketDir''​ has been added to Zabbix server and proxy configurations. This parameter points to the directory where internal Zabbix socket files are stored (/tmp by default). Server and proxy use different socket file names so it's safe to use the same ''​SocketDir''​ for server and proxy running on the same system. However, running multiple servers or proxies in the same system will require different ''​SocketDir''​ configurations.
Line 68: Line 92:
  
 See also: [[:​manual/​config/​visualisation/​maps/​map#​access_based_on_permissions|Network map configuration]] See also: [[:​manual/​config/​visualisation/​maps/​map#​access_based_on_permissions|Network map configuration]]
- 
-=== Upgrading Java gateway === 
- 
-Zabbix Java gateway has to be upgraded to support the new functionality of:  
- 
-  * [[:​manual/​introduction/​whatsnew340#​configurable_jmx_endpoints|configurable JMX endpoints]];​ 
-  * [[:​manual/​discovery/​low_level_discovery/​jmx|low-level discovery of JMX objects]]. 
- 
-=== JMX item protocol changes === 
- 
-An example of the new protocol: 
- 
-<​code>​ 
-{"​request":"​java gateway jmx","​jmx_endpoint":"​service:​jmx:​rmi:///​jndi/​rmi://​127.0.0.1:​12345/​jmxrmi","​keys":​["​jmx[\"​java.lang:​type={#​FSNAME}\",​\"​HeapMemoryUsage.used\"​]"​]} 
-</​code>​ 
  
 === Using templates for network devices === === Using templates for network devices ===
Line 164: Line 173:
 === API changes === === API changes ===
  
-Deprecated ''​isreadable()''​ and ''​iswritable()''​ methods as well as the ''​proxy.interfaces''​ parameter have been removed.+  * Deprecated ''​isreadable()''​ and ''​iswritable()''​ methods as well as the ''​proxy.interfaces''​ parameter have been removed. 
 +  * Validation of "​period"​ field has been added disallowing a trailing semicolon. All existing trailing semicolons will be removed by proxy/​server during upgrade.  ​
  
 === Changed housekeeper defaults === === Changed housekeeper defaults ===
Line 173: Line 183:
  
 Socket-based inter-process communication has been added in Zabbix 3.4. On systems where SELinux is enabled it may be required to add SELinux rules to allow Zabbix create/use UNIX domain sockets in the ''​SocketDir''​ directory. Currently socket files are used by server (alerter, preprocessing,​ IPMI) and proxy (IPMI). Socket files are persistent, meaning are present while the process is running. Socket-based inter-process communication has been added in Zabbix 3.4. On systems where SELinux is enabled it may be required to add SELinux rules to allow Zabbix create/use UNIX domain sockets in the ''​SocketDir''​ directory. Currently socket files are used by server (alerter, preprocessing,​ IPMI) and proxy (IPMI). Socket files are persistent, meaning are present while the process is running.
 +
 +==== See also ====
 +
 +  * [[:​manual/​installation/​template_changes|Template changes]]