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/06/20 13:37]
richlv renumber
manual:installation:upgrade_notes [2017/02/16 10:13] (current)
martins-v note about case-sensitive MySQL database
Line 1: Line 1:
-==== Upgrade notes for 2.0.0 ====+==== Upgrade notes for 2.0.0 ====
  
 === - Requirement changes === === - Requirement changes ===
Line 13: Line 13:
     * PHP XML Reader     * PHP XML Reader
     * PHP XML Writer     * PHP XML Writer
 +
 +=== - 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.
  
 === - Frontend specific upgrade notes === === - Frontend specific upgrade notes ===
Line 28: Line 32:
 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//​.
  
 +Dropdown choice in //​Administration -> General// is not remembered anymore.
 === - Database upgrading notes === === - Database upgrading notes ===
  
Line 71: Line 76:
 === - 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 85: 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 97: 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.
Line 103: Line 108:
 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: [[:2.0/manual/appendix/compatibility|Version compatibility]].+See also: [[manual:appendix:compatibility|Version compatibility]].
  
 === - Upgrade notes for web monitoring === === - Upgrade notes for web monitoring ===
Line 112: Line 117:
 {IPADDRESS} macro deprecated, use {HOST.IP} {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 [[2.0:manual:​appendix:​macros:​supported_by_location|this page]] for details.+"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.