Zabbix Documentation 2.0

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

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 [2012/05/11 13:12]
richlv [4 Upgrade notes] shift -> command
manual:installation:upgrade_notes [2017/02/16 10:13] (current)
martins-v note about case-sensitive MySQL database
Line 1: Line 1:
-==== -#4 Upgrade notes ====+==== Upgrade notes for 2.0.0 ====
  
-Database upgrade to 2.0 for MySQL will run UPDATE statement that fixes web monitoring item units for all items including the ones with correct unit. This should be harmless and only result in some additional UPDATEs.+=== - Requirement changes ===
  
-Option %%--with-pgsql%% ​for **configure** script ​has been changed to %%--with-postgresql%%.+  * Dropping MSIE 6 and 7 support ​for Zabbix frontend 
 +  ​MySQL 5.0 
 +  ​Windows 2000 (should specify minimum SP level) 
 +  ​Minimum supported PHP version ​has been changed to 5.1.6 
 +  * Note that with the use of jQuery for the Zabbix frontend browser compatibility might have suffered somewhat ​most notably, Konqueror does not work anymore. 
 +  * Minimum supported PostgreSQL version has been changed to 8.1 
 +  * Frontend now requires: 
 +    * PHP gettext 
 +    * PHP XML Reader 
 +    * PHP XML Writer
  
-During database upgrade with MySQL //ERROR 1436 (HY000): Thread stack overrun// ​increase **thread_stack** in **my.cnf**. 256K should be enough.+=== Case-sensitive MySQL database ===
  
-User group access property "API access"​ has been removedStarting with Zabbix 2.0all users have full access ​to the API.+A case-sensitive MySQL database is required for proper server workIt is [[:​manual/​appendix/​install/​db_scripts#​mysql|recommended]] to create a case-sensitive MySQL database during new installationsIf you created a MySQL database with the utf8 character set previouslyin order to support case sensitiveness of stored data, you need to convert ​the charset to utf8_bin.
  
-{IPADDRESS} macro deprecated, use {HOST.IP}+=== - Frontend specific upgrade notes ===
  
-Directory **misc/​conf** was moved to be just **conf** in the top level source directory.+User group access property "API access"​ has been removed. Starting with Zabbix 2.0, all users have full access ​to the API.
  
 Variables TRIGGER_FALSE_PERIOD and TRIGGER_BLINK_PERIOD in include/​defines.inc.php have been removed. These settings may now be configured in //​Administration -> General -> Trigger displaying options//. Variables TRIGGER_FALSE_PERIOD and TRIGGER_BLINK_PERIOD in include/​defines.inc.php have been removed. These settings may now be configured in //​Administration -> General -> Trigger displaying options//.
- 
-"Host profiles"​ were renamed to "host inventory"​. New host inventory macros {INVENTORY.*} were introduced. {PROFILE.*} macros are still supported but it's highly recommended to change those to {INVENTORY.*} . See [[2.0:​manual:​appendix:​macros:​supported_by_location|this page]] for details. 
- 
-Upgrading to 2.0.0 may increase configuration cache usage, because it now additionally caches general configuration and trigger information. 
  
 Graph item type //​Aggregated//​ has been removed. If such items are present, upgrade procedure will convert them to normal items. Graph item type //​Aggregated//​ has been removed. If such items are present, upgrade procedure will convert them to normal items.
Line 26: Line 31:
  
 Multiple element selecting in maps while holding down //Shift// was removed. On Mac OSX multiple elements can now be selected by holding down //​Command//​. Multiple element selecting in maps while holding down //Shift// was removed. On Mac OSX multiple elements can now be selected by holding down //​Command//​.
-=== - Requirement changes === 
  
-  * Dropping MSIE 6 and 7 support for Zabbix frontend +Dropdown choice in //​Administration -> General// is not remembered anymore
-  * MySQL 5.0 +=== - Database upgrading notes === 
-  * Windows 2000 (should specify minimum SP level) + 
-  * Minimum supported PHP version has been changed ​to 5.1.6 +Database upgrade ​to 2.0 for MySQL will run UPDATE statement ​that fixes web monitoring item units for all items including ​the ones with correct unit. This should be harmless and only result in some additional UPDATEs. 
-  * Note that with the use of jQuery ​for the Zabbix frontend browser compatibility might have suffered somewhat ​most notablyKonqueror does not work anymore. + 
-  * Minimum supported PostgreSQL version has been changed to 8.1 +For better performance,​ especially with large databases on MySQL, increasing [[http://​dev.mysql.com/​doc/​refman/​5.5/​en/​innodb-parameters.html#​sysvar_innodb_buffer_pool_size|innodb_buffer_pool_size]] before upgrading is highly suggested. Alsodisable binlog, if it is not needed, or increase [[http://​dev.mysql.com/​doc/​refman/​5.1/​en/​replication-options-binary-log.html#​sysvar_binlog_cache_size|binlog_cache_size]]. 
-  * Frontend now requires: + 
-    PHP gettext +During database upgrade with MySQL //ERROR 1436 (HY000): Thread stack overrun// - increase ​**thread_stack** in **my.cnf**. 256K should be enough. 
-    ​PHP XML Reader + 
-    ​PHP XML Writer+=== - Zabbix server related notes === 
 + 
 +Upgrading to 2.0.0 may increase Zabbix server configuration cache usage, because it now additionally caches general configuration and trigger information. 
 === - Changed default configuration directories === === - Changed default configuration directories ===
  
Line 62: Line 69:
  
 Database creation files have been moved in **database** directory. It contains one directory per supported database type. Database creation files have been moved in **database** directory. It contains one directory per supported database type.
 +
 +Option %%--with-pgsql%% for **configure** script has been changed to %%--with-postgresql%%.
 +
 +Directory **misc/​conf** was moved to be just **conf** in the top level source directory.
  
 === - Item changes === === - Item changes ===
  
-**net.tcp.dns** and **net.tcp.dns.query** have been [[:2.0/manual/introduction/whatsnew200#​improved_items|renamed]] to **net.dns** and **net.dns.record**,​ respectively. Old syntax still supported as an alias.+**net.tcp.dns** and **net.tcp.dns.query** have been [[manual:introduction:whatsnew200#​improved_items|renamed]] to **net.dns** and **net.dns.record**,​ respectively. Old syntax still supported as an alias.
  
 All items that return text (character, log, text types of information),​ including user parameters and external checks, now can return whitespace only as well, setting the return value to an empty string. All items that return text (character, log, text types of information),​ including user parameters and external checks, now can return whitespace only as well, setting the return value to an empty string.
Line 79: Line 90:
 <note important>​After upgrading, it is recommended to manually review all external checks that have more than one parameter in the key for any possible conversion errors to correct.</​note>​ <note important>​After upgrading, it is recommended to manually review all external checks that have more than one parameter in the key for any possible conversion errors to correct.</​note>​
  
-The format of [[:2.0:manual:​config:​items:​itemtypes:​simple_checks|simple checks]] has been changed. The possibility of using IP addresses in simple checks has been added. Database upgrade process converts all existing simple check keys to the new syntax.+The format of [[manual:​config:​items:​itemtypes:​simple_checks|simple checks]] has been changed. The possibility of using IP addresses in simple checks has been added. Database upgrade process converts all existing simple check keys to the new syntax.
  
-A **status** item has been removed. Instead of it a new [[2.0:manual:​config:​items:​itemtypes:​internal|internal item]] - **zabbix[host,​agent,​available]** has been added. The database upgrade process **doesn'​t convert** all existing '​status'​ keys and associated triggers to the new syntax, so they have to be converted manually.+A **status** item has been removed. Instead of it a new [[manual:​config:​items:​itemtypes:​internal|internal item]] - **zabbix[host,​agent,​available]** has been added. The database upgrade process **doesn'​t convert** all existing '​status'​ keys and associated triggers to the new syntax, so they have to be converted manually.
  
 === - Upgrade notes for proxies === === - Upgrade notes for proxies ===
  
-<note warning>​Older Zabbix proxies (1.6 and 1.8) can not be used with Zabbix 2.0 server. All proxies must be upgraded at the same time as the server.</​note>​+<note warning>​Older Zabbix proxies (1.6 and 1.8) cannot ​be used with Zabbix 2.0 server; similarly, a Zabbix 2.0 proxy cannot be used with Zabbix 1.8 or older server. All proxies must be upgraded at the same time as the server.</​note>​
  
 Zabbix 1.8 proxies may continue collecting data while the server database is upgraded. In this case proxy database must be converted before the new server is started up. Proxy will send all collected and converted values to the server once both server and proxy are upgraded and started up. Zabbix 1.8 proxies may continue collecting data while the server database is upgraded. In this case proxy database must be converted before the new server is started up. Proxy will send all collected and converted values to the server once both server and proxy are upgraded and started up.
Line 91: Line 102:
 === - Upgrade notes for agents === === - Upgrade notes for agents ===
  
-Server parameter has been changed. Entries in it will never be used for active checks, only for passive. Only entries from **ServerActive** will be used for active checks.+**Server** parameter has been changed. Entries in it will never be used for active checks, only for passive. Only entries from **ServerActive** will be used for active checks.
  
 Parameter **ServerPort** has been removed. If it will be still specified in the configuration file, agent will not start up. Parameter **ServerPort** has been removed. If it will be still specified in the configuration file, agent will not start up.
  
 Parameters **DisableActive** and **DisablePassive** have been removed. Instead, not specifying **ServerActive** will not do any active item processing, and specifying **StartAgents**=0 will disable processing of incoming connections for passive items.\\ If these parameters will be still specified in the configuration file, agent will not start up. Parameters **DisableActive** and **DisablePassive** have been removed. Instead, not specifying **ServerActive** will not do any active item processing, and specifying **StartAgents**=0 will disable processing of incoming connections for passive items.\\ If these parameters will be still specified in the configuration file, agent will not start up.
 +
 +See also: [[manual:​appendix:​compatibility|Version compatibility]].
 +
 +=== - Upgrade notes for web monitoring ===
 +
 +If a host was assigned to be monitored by a proxy before upgrading to 2.0 and it had a web scenario assigned to it, this web scenario would be performed from the Zabbix server. After upgrade such a web scenario may stop working. After upgrading to 2.0 the proxy that this host is assigned to should be compiled with web monitoring support and be able to access websites, used in the scenario.
 +=== - General notes ===
 +
 +{IPADDRESS} macro deprecated, use {HOST.IP}
 +
 +"Host profiles"​ were renamed to "host inventory"​. New host inventory macros {INVENTORY.*} were introduced. {PROFILE.*} macros are still supported but it's highly recommended to change those to {INVENTORY.*} . See [[manual:​appendix:​macros:​supported_by_location|this page]] for details.