Zabbix Documentation 2.2

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:installation:upgrade_notes_220

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_220 [2014/03/28 14:53]
asaveljevs Documented system.uname changes.
manual:installation:upgrade_notes_220 [2017/02/16 10:09] (current)
martins-v note about case-sensitive MySQL database
Line 1: Line 1:
-==== -#Upgrade notes for 2.2.0 ====+==== -#Upgrade notes for 2.2.0 ====
  
 === Requirement changes === === Requirement changes ===
Line 7: Line 7:
   * The "​mysqli"​ PHP extension is required instead of "​mysql"​   * The "​mysqli"​ PHP extension is required instead of "​mysql"​
   * Accepted data limit when using Zabbix protocol was changed from 128MB to 64MB.   * Accepted data limit when using Zabbix protocol was changed from 128MB to 64MB.
 +
 +=== Case-sensitive MySQL database ===
 +
 +A case-sensitive MySQL database is required for proper server work. It is [[:​manual/​appendix/​install/​db_scripts#​mysql|recommended]] to create a case-sensitive MySQL database during new installations. If you created a MySQL database with the utf8 character set previously, in order to support case sensitiveness of stored data, you need to convert the charset to utf8_bin.
  
 === New upgrade procedure === === New upgrade procedure ===
  
-There are no upgrade SQL scripts anymore - database upgrade is performed by the Zabbix server.+There are no upgrade SQL scripts anymore - database upgrade is performed by the Zabbix server/proxy.
  
 <note warning>​Database upgrade is automatic - make sure to have a backup before starting the new Zabbix server binary.</​note>​ <note warning>​Database upgrade is automatic - make sure to have a backup before starting the new Zabbix server binary.</​note>​
 +
 +<​note>​Automatic database upgrade for SQLite is not supported.</​note>​
  
 === Permission changes === === Permission changes ===
  
 Since Zabbix 2.2 "​Read-write"​ permissions have precedence over "​Read"​ permissions. Previously, if a user (through two different user groups) had both "​Read"​ and "​Read-write"​ permissions to a specific host, the host was only "​Read"​ to them. Now it will be "​Read-write"​. Since Zabbix 2.2 "​Read-write"​ permissions have precedence over "​Read"​ permissions. Previously, if a user (through two different user groups) had both "​Read"​ and "​Read-write"​ permissions to a specific host, the host was only "​Read"​ to them. Now it will be "​Read-write"​.
 +
 +=== Trigger calculation changes with item history=0 ===
 +
 +Previously you could set the //Keep history// option in item configuration to 0 and still have those triggers working that used only the last value in calculation. Starting with the introduction of [[:​manual/​introduction/​whatsnew220#​value_cache_for_faster_access_to_history_data|value cache]] in Zabbix 2.2, no trigger functions will be calculated if item history is set to 0.
  
 === Changed maintenance period logic === === Changed maintenance period logic ===
  
-Previously, a maintenance period for every second/​third/​etc day would first occur on the second/​third/​etc day after the //Active since// day. Now the first occurence ​will take place on the //Active since// day and then every second/​third/​etc day.+Previously, a maintenance period for every second/​third/​etc day would first occur on the second/​third/​etc day after the //Active since// day. Now the first occurrence ​will take place on the //Active since// day and then every second/​third/​etc day.
  
 === 64-bit range for object IDs === === 64-bit range for object IDs ===
Line 82: Line 92:
 Zabbix server and proxy daemons will now correctly use the Timeout configuration parameter when performing SNMP checks. Additionally now the daemons will not perform retries after single unsuccessful (the timeout/​wrong credentials) SNMP request. Previously the SNMP library default timeout and retries values (1 second and 5 retries respectively) were actually used. Zabbix server and proxy daemons will now correctly use the Timeout configuration parameter when performing SNMP checks. Additionally now the daemons will not perform retries after single unsuccessful (the timeout/​wrong credentials) SNMP request. Previously the SNMP library default timeout and retries values (1 second and 5 retries respectively) were actually used.
  
-=== Changes item parameter validation ===+=== Changes ​in item parameter validation ===
  
 A more strict parameter validation by Zabbix agent has been introduced. Whereas previously parameters for items that do not support parameters would be ignored, now the items will return ZBX_NOTSUPPORTED and become unsupported. A more strict parameter validation by Zabbix agent has been introduced. Whereas previously parameters for items that do not support parameters would be ignored, now the items will return ZBX_NOTSUPPORTED and become unsupported.
Line 88: Line 98:
 Since 2.2 Zabbix agent will return ZBX_NOTSUPPORTED in case of invalid //timeout// or //count// values of **net.dns** check. Previously there was no validation and default or 0 values were used. From now on zero value will be also treated as an error. Since 2.2 Zabbix agent will return ZBX_NOTSUPPORTED in case of invalid //timeout// or //count// values of **net.dns** check. Previously there was no validation and default or 0 values were used. From now on zero value will be also treated as an error.
  
-=== Changes in item system.uname === +=== Changes in system.uname ​item ===
- +
-Before Zabbix 2.2, the value for **system.uname** was obtained by invoking "uname -a" utility on Unix systems. Since Zabbix 2.2, the value is obtained by using uname() system call. Hence, the value of this item might change after the upgrade and no longer include additional information that "uname -a" prints based on other sources.+
  
 +Before Zabbix 2.2, the value for **system.uname** was obtained by invoking "uname -a" on Unix systems. Since Zabbix 2.2, the value is obtained by using the uname() system call. Hence, the value of this item might change after the upgrade and no longer includes the additional information that "uname -a" prints based on other sources.
 === Changes in {EVENT.*} macros === === Changes in {EVENT.*} macros ===
  
Line 98: Line 107:
 Previously, when used in recovery messages they would return information of the recovery event. In Zabbix 2.2 they will return information of the original problem event. Previously, when used in recovery messages they would return information of the recovery event. In Zabbix 2.2 they will return information of the original problem event.
  
-To return information about the recovery event, separate recovery (EVENT.RECOVERY.* ) macros are introduced - {EVENT.RECOVERY.ID},​ {EVENT.RECOVERY.TIME},​ etc. For more information see [[:2.2/manual/appendix/macros/supported_by_location|Macros supported by location]].+To return information about the recovery event, separate recovery (EVENT.RECOVERY.* ) macros are introduced - {EVENT.RECOVERY.ID},​ {EVENT.RECOVERY.TIME},​ etc. For more information see [[manual:appendix:macros:supported_by_location|Macros supported by location]].
  
 === Changes in {ESC.HISTORY} macro === === Changes in {ESC.HISTORY} macro ===
Line 106: Line 115:
 === Regular expression testing === === Regular expression testing ===
  
-The logic of displaying testing results of regular expressions has been [[:2.2/manual/introduction/whatsnew220#​miscellaneous_improvements|improved]]. Results are shown after applying the condition, not before.+The logic of displaying testing results of regular expressions has been [[manual:introduction:whatsnew220#​miscellaneous_improvements|improved]]. Results are shown after applying the condition, not before.
  
 === API changes === === API changes ===
Line 118: Line 127:
 === Housekeeper changes === === Housekeeper changes ===
  
-The **DisableHousekeeping** server configuration option is supported no more. Instead, finer controls are located in the frontend, in //​Administration -> General -> [[:2.2/manual/web_interface/frontend_sections/administration/general|Housekeeper]]//,​ allowing to selectively enable/​disable housekeeping processes for specific tables.+The **DisableHousekeeping** server configuration option is supported no more. Instead, finer controls are located in the frontend, in //​Administration -> General -> [[manual:web_interface:frontend_sections:administration:general|Housekeeper]]//,​ allowing to selectively enable/​disable housekeeping processes for specific tables.
  
-<note warning>​Housekeeper is disabled by default after upgrading ​to 2.2. The desired housekeeper ​functionality ​should ​be enabled manually.</​note>​+Due to the changes in how latest item values are stored, values of items with history storage period set to "​0"​ will not be displayed in the //​Monitoring -> Latest data// and //​Monitoring -> Overview// pages. The //​{ITEM.LASTVALUE}//​ macro in the frontend will also not work for such items. To avoid breaking this functionality ​the history storage period will be automatically changed from "​0"​ to "​1"​ for all existing items.
  
 +<note warning>​Housekeeper is disabled by default after upgrading to 2.2. The desired housekeeper functionality should be enabled manually.</​note>​
 === JSON validation in server === === JSON validation in server ===
  
Line 170: Line 180:
  
 Zabbix server now correctly enables SSL host verification when using Ez Texting service to send alerts. Zabbix server now correctly enables SSL host verification when using Ez Texting service to send alerts.
 +
 +=== Queue changes ===
 +As the queue (Administration → Queue) is now retrieved directly from the server it is available only when Zabbix server is running and if the frontend has direct access to Zabbix server.
 +
 +=== Logging changes ===
 +
 +Before Zabbix 2.2.0, server and proxy would log messages about the availability of a particular type of checks on a host in the following format:
 +  SNMP item [ifInOctets.3] on host [gateway] failed: first network error, wait for 15 seconds
 +Starting with Zabbix 2.2.0, the type specification for SNMP, IPMI and JMX checks now includes the additional word "​agent":​
 +  SNMP agent item [ifInOctets.3] on host [gateway] failed: first network error, wait for 15 seconds