Zabbix Documentation 1.8

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:about:installation_and_upgrade

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:about:installation_and_upgrade [2012/04/11 08:40]
richlv [3.3.5 For version 1.8.8] further updates to duplicate host detection
manual:about:installation_and_upgrade [2014/09/25 15:01] (current)
sasha Links adapted because of a move operation
Line 3: Line 3:
 === - Installation === === - Installation ===
  
-See the [[:1.8/manual/installation/installation_from_source]] section for full details.+See the [[manual:installation:installation_from_source]] section for full details.
  
 === - Version compatibility === === - Version compatibility ===
Line 42: Line 42:
  
 The shutdown upon detection of duplicate hosts, introduced in 1.8.8, has been removed. The shutdown upon detection of duplicate hosts, introduced in 1.8.8, has been removed.
 +
 +== - For version 1.8.16 ==
 +
 +Accepted data limit of 128MB was introduced when using Zabbix protocol. Any other data (including older Zabbix protocols) stays limited at 16MB.
 +
 +== - For version 1.8.18 ==
 +
 +Zabbix server now correctly enables SSL host verification when using Ez Texting service to send alerts.
 +
 +== - For version 1.8.20 ==
 +
 +If Zabbix is logging to syslog then after an upgrade to Zabbix 1.8.20 you will see changes in the application names appearing in syslog:
 +     ​Zabbix Agent  -> zabbix_agent
 +     ​Zabbix Agent  -> zabbix_agentd
 +     ​Zabbix Proxy  -> zabbix_proxy
 +     ​Zabbix Server -> zabbix_server
 +     ​Zabbix Get    -> zabbix_get
 +     ​Zabbix Sender -> zabbix_sender
 +The old, incorrect names (on the left) contained a space which is not allowed by RFC 5424 for APP-NAME.
 +If you are using regular expressions in monitoring of syslog you may want to adjust them for the new application names.
 === - System requirement changes === === - System requirement changes ===
  
Line 50: Line 70:
   * Maximal PHP POST size should be at least 16MB (option **post_max_size**).   * Maximal PHP POST size should be at least 16MB (option **post_max_size**).
  
-Also see requirement changes for versions [[:​1.8/​manual/​about/​what_s_new_1.8.2#​frontend_requirement_changes|1.8.2]],​ [[:​1.8/​manual/​about/​what_s_new_1.8.3#​requirement_changes|1.8.3]] and [[:​1.8/​manual/​about/​what_s_new_1.8.9#​supported_postgresql_version_changes|1.8.9]].+Also see requirement changes for versions [[what_s_new_1.8.2#​frontend_requirement_changes|1.8.2]],​ [[what_s_new_1.8.3#​requirement_changes|1.8.3]] and [[what_s_new_1.8.9#​supported_postgresql_version_changes|1.8.9]].
  
 === - Known problems === === - Known problems ===
Line 61: Line 81:
   * Sorting in frontend is not performed for entities with positional variables (like item names with $1 etc).   * Sorting in frontend is not performed for entities with positional variables (like item names with $1 etc).
   * XML export includes SNMP and other information for all items.   * XML export includes SNMP and other information for all items.
-  * Hostnames with spaces do not work when sending data from a file with **[[:1.8/manual/processes/zabbix_sender|zabbix_sender]]** (fixed in 1.8.2).+  * Hostnames with spaces do not work when sending data from a file with **[[manual:processes:zabbix_sender|zabbix_sender]]** (fixed in 1.8.2).
   * Uploading of images for network maps may fail if database is not configured properly. Make sure database, tables and fields are set to UTF-8 encoding.   * Uploading of images for network maps may fail if database is not configured properly. Make sure database, tables and fields are set to UTF-8 encoding.
   * Precompiled binaries (agent, sender, get) might not work on 64bit systems with glibc versions older than 2.5. Common symptom is failing to start with the error message: //Floating point exception//​. Use older versions, or compile from the scratch on the target system.   * Precompiled binaries (agent, sender, get) might not work on 64bit systems with glibc versions older than 2.5. Common symptom is failing to start with the error message: //Floating point exception//​. Use older versions, or compile from the scratch on the target system.
Line 85: Line 105:
 Make a backup copy of Zabbix binaries, configuration files and PHP files. Make a backup copy of Zabbix binaries, configuration files and PHP files.
 == - Install new server binaries == == - Install new server binaries ==
-You may use pre-compiled binaries or [[:1.8/manual/installation/installation_from_source|compile your own]].+You may use pre-compiled binaries or [[manual:installation:installation_from_source|compile your own]].
  
 == - Review Server configuration parameters == == - Review Server configuration parameters ==
 Some parameters of zabbix_server.conf were changed in 1.8, new parameters added. You may want to review them. Some parameters of zabbix_server.conf were changed in 1.8, new parameters added. You may want to review them.
  
-  * Configuration option **StartDBSyncers** [[:​1.8/​manual/​about/​what_s_new#​added_configuration_data_cache_module|has been removed]] from Zabbix server and proxy configuration files.+  * Configuration option **StartDBSyncers** [[what_s_new#​added_configuration_data_cache_module|has been removed]] from Zabbix server and proxy configuration files.
  
 == - Upgrade database == == - Upgrade database ==
Line 141: Line 161:
  
 == - Install new Zabbix GUI == == - Install new Zabbix GUI ==
-Follow [[:1.8/manual/installation/installation_from_source#​zabbix_web_interface|installation instructions]].+Follow [[manual:installation:installation_from_source#​zabbix_web_interface|installation instructions]].
 == - Start new Zabbix binaries == == - Start new Zabbix binaries ==
 Start new binaries. Check log files to see if the binaries have started successfully. Start new binaries. Check log files to see if the binaries have started successfully.