Zabbix Documentation 4.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_400

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_400 [2019/07/19 08:04]
martins-v plain text protocol dropped
manual:installation:upgrade_notes_400 [2020/05/11 08:35] (current)
martins-v upgrade with MariaDB 10.2.1 and before may fail; compact row format (ZBX-17690)
Line 33: Line 33:
 As a consequence,​ Zabbix agents that are older than version 1.4 are no longer supported. Also, messages from self-written senders will be rejected if the header is absent. Whereas previously Zabbix trappers would accept messages without headers as well as messages with headers, now they will only accept messages with protocol header. As a consequence,​ Zabbix agents that are older than version 1.4 are no longer supported. Also, messages from self-written senders will be rejected if the header is absent. Whereas previously Zabbix trappers would accept messages without headers as well as messages with headers, now they will only accept messages with protocol header.
  
-Requests from an older Zabbix get version to the new agent will fail. In this case the following error message is displayed:+Requests from an older Zabbix get version to the new agent will fail. Note that in this case the following error message is displayed:
  
   Check access restrictions in Zabbix agent configuration   Check access restrictions in Zabbix agent configuration
Line 53: Line 53:
  
 Note that this syntax was never used by official Zabbix item keys, nor was it ever officially documented as supported. It only existed for backward compatibility with such solutions as [[http://​www.kjkoster.org/​zapcat/​Zapcat_JMX_Zabbix_Bridge.html|Zapcat JMX Zabbix Bridge]]. Note that this syntax was never used by official Zabbix item keys, nor was it ever officially documented as supported. It only existed for backward compatibility with such solutions as [[http://​www.kjkoster.org/​zapcat/​Zapcat_JMX_Zabbix_Bridge.html|Zapcat JMX Zabbix Bridge]].
 +
 +Note that this change does not affect single-level parameters. See [[:​manual/​config/​items/​itemtypes/​aggregate|aggregate items]] for information about supported syntax. ​
  
 === MySQL 8.0 support === === MySQL 8.0 support ===
Line 74: Line 76:
  
 HTTP basic-authentication specific code was removed from API, therefore the ''​password''​ field is now mandatory for the API ''​user.login''​ action. HTTP basic-authentication specific code was removed from API, therefore the ''​password''​ field is now mandatory for the API ''​user.login''​ action.
 +
 +=== Upgrade with MariaDB 10.2.1 and before ===
 +
 +Upgrading Zabbix may fail if database tables were created with MariaDB 10.2.1 and before, because in those versions the default row format is compact. This can be fixed by changing the row format to dynamic (see also [[https://​support.zabbix.com/​browse/​ZBX-17690|ZBX-17690]]).
 +
 ==== Informational ==== ==== Informational ====