Zabbix Documentation 5.2

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:installation:known_issues

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
Last revision Both sides next revision
manual:installation:known_issues [2019/05/17 07:57]
martins-v php 7.3 opcache configuration issue
manual:installation:known_issues [2020/06/08 12:39]
martins-v proxy startup issue with MySQL8 (ZBX-17801)
Line 1: Line 1:
 ==== 7 Known issues ==== ==== 7 Known issues ====
  
 +=== Proxy startup with MySQL 8.0.0-8.0.17 ===
 +
 +zabbix_proxy on MySQL versions 8.0.0-8.0.17 fails with the following %%"​%%access denied%%"​%% error:
 +
 +  [Z3001] connection to database '​zabbix'​ failed: [1227] Access denied; you need (at least one of) the SUPER, SYSTEM_VARIABLES_ADMIN or SESSION_VARIABLES_ADMIN privilege(s) for this operation
 +
 +That is due to MySQL 8.0.0 starting to enforce special permissions for setting session variables. However, in 8.0.18 this behaviour was removed: [[https://​dev.mysql.com/​doc/​refman/​8.0/​en/​server-system-variables.html|As of MySQL 8.0.18, setting the session value of this system variable is no longer a restricted operation.]]
 +
 +The workaround is based on granting additional privileges to the ''​zabbix''​ user:
 +
 +For MySQL versions 8.0.14 - 8.0.17:
 +
 +  grant SESSION_VARIABLES_ADMIN on *.* to '​zabbix'​@'​localhost';​
 +
 +For MySQL versions 8.0.0 - 8.0.13:
 +
 +  grant SYSTEM_VARIABLES_ADMIN on *.* to '​zabbix'​@'​localhost';​
 +
 +=== Timescale DB ===
 +
 +PostgreSQL versions 9.6-12 use too much memory when updating tables with a large number of partitions ([[https://​www.postgresql-archive.org/​memory-problems-and-crash-of-db-when-deleting-data-from-table-with-thousands-of-partitions-td6108612.html|see problem report]]). This issue manifests itself when Zabbix updates trends on systems with TimescaleDB if trends are split into relatively small (e.g. 1 day) chunks. This leads to hundreds of chunks present in the trends tables with default housekeeping settings - the condition where PostgreSQL is likely to run out of memory.
 +
 +The issue has been resolved since Zabbix 5.0.1 for new installations with TimescaleDB,​ but if TimescaleDB was set up with Zabbix before that, please see [[https://​support.zabbix.com/​browse/​ZBX-16347?​focusedCommentId=430816&​page=com.atlassian.jira.plugin.system.issuetabpanels:​comment-tabpanel#​comment-430816|ZBX-16347]] for the migration notes.
 +
 +=== 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]]).
 === Global event correlation === === Global event correlation ===
  
 Events may not get correlated correctly if the time interval between the first and second event is very small, i.e. half a second and less. Events may not get correlated correctly if the time interval between the first and second event is very small, i.e. half a second and less.
 +
 +=== Numeric (float) data type range with PostgreSQL 11 and earlier ===
 +
 +PostgreSQL 11 and earlier versions only support floating point value range of approximately -1.34E-154 to 1.34E+154.
  
 === IPMI checks === === IPMI checks ===
Line 16: Line 47:
 Zabbix server or proxy that uses MySQL as its database may or may not work correctly with MySQL ODBC library due to an [[https://​bugs.mysql.com/​bug.php?​id=73709|upstream bug]]. Please see  [[https://​support.zabbix.com/​browse/​ZBX-7665|ZBX-7665]] for more information and available workarounds. Zabbix server or proxy that uses MySQL as its database may or may not work correctly with MySQL ODBC library due to an [[https://​bugs.mysql.com/​bug.php?​id=73709|upstream bug]]. Please see  [[https://​support.zabbix.com/​browse/​ZBX-7665|ZBX-7665]] for more information and available workarounds.
  
-XML data queried from Microsoft SQL Server may get truncated ​to 2033 characters due to a Microsoft [[https://​support.microsoft.com/​en-us/​help/​310378/​the-xml-data-row-is-truncated-at-2-033-characters-when-you-use-the-sql|issue]].+XML data queried from Microsoft SQL Server may get truncated ​in various ways on Linux and UNIX systems.
  
 === HTTPS checks === === HTTPS checks ===
Line 34: Line 65:
 If the OpenBSD operating system is used, a use-after-free bug in the Net-SNMP library up to the 5.7.3 version can cause a crash of Zabbix server if the SourceIP parameter is set in the Zabbix server configuration file. As a workaround, please do not set the SourceIP parameter. The same problem applies also for Linux, but it does not cause Zabbix server to stop working. If the OpenBSD operating system is used, a use-after-free bug in the Net-SNMP library up to the 5.7.3 version can cause a crash of Zabbix server if the SourceIP parameter is set in the Zabbix server configuration file. As a workaround, please do not set the SourceIP parameter. The same problem applies also for Linux, but it does not cause Zabbix server to stop working.
 A local patch for the net-snmp package on OpenBSD was applied and will be released with OpenBSD 6.3. A local patch for the net-snmp package on OpenBSD was applied and will be released with OpenBSD 6.3.
 +
 +=== SNMP data spikes ===
 +
 +Spikes in SNMP data have been observed that may be related to certain physical factors like voltage spikes in the mains. See [[https://​support.zabbix.com/​browse/​ZBX-14318|ZBX-14318]] more details.
 +
 +=== Alerter process crash in Centos/RHEL 7 ===
 +
 +Instances of a Zabbix server alerter process crash have been encountered in Centos/RHEL 7. Please see [[https://​support.zabbix.com/​browse/​ZBX-10461|ZBX-10461]] for details.
 +
 +=== Compiling Zabbix agent on HP-UX ===
 +
 +If you install the PCRE library from a popular HP-UX package site http://​hpux.connect.org.uk,​ for example from file ''​pcre-8.42-ia64_64-11.31.depot'',​ you get only the 64-bit version of the library installed in the /​usr/​local/​lib/​hpux64 directory.
 +
 +In this case, for successful agent compilation customized options need to be used for the %%"​%%configure%%"​%% script, e.g.: 
 +
 +  CFLAGS="​+DD64"​ ./configure --enable-agent --with-libpcre-include=/​usr/​local/​include --with-libpcre-lib=/​usr/​local/​lib/​hpux64
  
 === Flipping frontend locales === === Flipping frontend locales ===
  
-It has been observed that frontend locales may flip without apparent logic. ​A known workaround to this is to disable multithreading in PHP and ApachePlease see  [[https://​support.zabbix.com/​browse/​ZBX-10911|ZBX-10911]] for more information.+It has been observed that frontend locales may flip without apparent logic, iesome pages (or parts of pages) are displayed in one language while other pages (or parts of pages) in a different languageTypically the problem may appear when there are several users, some of whom use one locale, while others use another.
  
 +A known workaround to this is to disable multithreading in PHP and Apache.
 +
 +The problem is related to how setting the locale works [[https://​www.php.net/​manual/​en/​function.setlocale|in PHP]]: locale information is maintained per process, not per thread. So in a multi-thread environment,​ when there are several projects run by same Apache process, it is possible that the locale gets changed in another thread and that changes how data can be processed in the Zabbix thread.
 +
 +For more information,​ please see related problem reports:
 +
 +  * [[https://​support.zabbix.com/​browse/​ZBX-10911|ZBX-10911]] (Problem with flipping frontend locales)
 +  * [[https://​support.zabbix.com/​browse/​ZBX-16297|ZBX-16297]] (Problem with number processing in graphs using the ''​bcdiv''​ function of BC Math functions)
 === Compatibility issue with PHP 7.0 === === Compatibility issue with PHP 7.0 ===
  
Line 75: Line 130:
 Failed login attempt message will display only the first 39 characters of a stored IP address as that's the character limit in the database field. That means that IPv6 IP addresses longer than 39 characters will be shown incompletely. Failed login attempt message will display only the first 39 characters of a stored IP address as that's the character limit in the database field. That means that IPv6 IP addresses longer than 39 characters will be shown incompletely.
  
-=== IE11 issue with map resizing in dashboard widgets ​=== +=== Zabbix agent checks on Windows ​===  
- +Non-existing DNS entries ​in a ''​Server''​ parameter of Zabbix agent configuration file (zabbix_agentd.confmay increase Zabbix agent response time on Windows. This happens because Windows DNS caching daemon doesn'​t cache negative responses for IPv4 addresses. However, for IPv6 addresses negative responses are cached, so a possible workaround to this is disabling IPv4 on the host.
-Maps, in Internet Explorer 11, are cut off on the right side if the map content is larger than the dashboard widget area (instead of being resized proportionately). This is intentional because of an IE11-related issue with proper resizing of SVG images.+