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
manual:installation:known_issues [2020/12/07 11:46]
martins-v net-snmp-perl has been removed in RHEL/CentOS 8.0-8.2; re-added in RHEL 8.3 (ZBX-17192)
manual:installation:known_issues [2020/12/08 08:39]
martins-v database TLS connection is not supported with the 'verify_ca' option with MariaDB (ZBX-18548)
Line 1: Line 1:
-==== 8 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';​ 
- 
-=== Database connection encryption === 
- 
-Database connection encryption is not supported on RHEL/CentOS 7, because these systems ship with packages that are too old: 
- 
-  Name        : mariadb-libs 
-  Version ​    : 5.5.65 
-  ​ 
-  Name        : postgresql-libs 
-  Version ​    : 9.2.24 
- 
-=== 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 === 
- 
-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. 
- 
-=== NetBSD 8.0 and newer === 
- 
-Various Zabbix processes may randomly crash on startup on the NetBSD versions 8.X and 9.X. That is due to the too small default stack size (4MB), which must be increased by running: 
- 
-  ulimit -s 10240 
- 
-For more information,​ please see the related problem report: [[https://​support.zabbix.com/​browse/​ZBX-18275|ZBX-18275]]. 
- 
- 
-=== IPMI checks === 
- 
-IPMI checks will not work with the standard OpenIPMI library package on Debian prior to 9 (stretch) and Ubuntu prior to 16.04 (xenial). To fix that, recompile OpenIPMI library with OpenSSL enabled as discussed in [[https://​support.zabbix.com/​browse/​ZBX-6139|ZBX-6139]]. 
-=== SSH checks === 
- 
-Some Linux distributions like Debian, Ubuntu do not support encrypted private keys (with passphrase) if the libssh2 library is installed from packages. Please see  [[https://​support.zabbix.com/​browse/​ZBX-4850|ZBX-4850]] for more details. 
- 
-When using libssh 0.9.x on CentOS 8 with OpenSSH 8 SSH checks may occasionally report %%"​Cannot read data from SSH server"​%%. This is caused by a libssh [[https://​gitlab.com/​libssh/​libssh-mirror/​-/​merge_requests/​101|issue]] ([[https://​bugs.libssh.org/​T231|more detailed report]]). The error is expected to have been fixed by a stable libssh 0.9.5 release. See also [[https://​support.zabbix.com/​browse/​ZBX-17756|ZBX-17756]] for details. 
- 
-=== ODBC checks === 
- 
-  * MySQL unixODBC driver should not be used with Zabbix server or Zabbix proxy compiled against MariaDB connector library and vice versa, if possible it is also better to avoid using the same connector as the driver due to an [[https://​bugs.mysql.com/​bug.php?​id=73709|upstream bug]]. Suggested setup: 
- 
-  PostgreSQL, SQLite or Oracle connector -> MariaDB or MySQL unixODBC driver 
-  MariaDB connector -> MariaDB unixODBC driver 
-  MySQL connector -> MySQL unixODBC driver 
- 
-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 in various ways on Linux and UNIX systems. 
- 
-  * It has been observed that using ODBC checks on CentOS 8 for monitoring Oracle databases using Oracle Instant Client for Linux 11.2.0.4.0 causes the Zabbix server to crash. The issue can be solved by upgrading Oracle Instant Client to 12.1.0.2.0, 12.2.0.1.0, 18.5.0.0.0 or 19. See also [[https://​support.zabbix.com/​browse/​ZBX-18402|ZBX-18402]]. 
- 
-=== HTTPS checks === 
- 
-Web scenarios and HTTP agent items using the https protocol, Zabbix agent checks ''​net.tcp.service[https...]''​ and ''​net.tcp.service.perf[https...]''​ may fail if the target server is configured to disallow TLS v1.0 protocol or below. ​ Please see  [[https://​support.zabbix.com/​browse/​ZBX-9879|ZBX-9879]] for more information and available workarounds. 
- 
-=== Web monitoring and HTTP agent === 
- 
-Zabbix server leaks memory on CentOS 6, CentOS 7 and possibly other related Linux distributions due to an [[https://​bugzilla.redhat.com/​show_bug.cgi?​id=1057388|upstream bug]] when %%"​%%SSL verify peer%%"​%% is enabled in web scenarios or HTTP agent. Please see [[https://​support.zabbix.com/​browse/​ZBX-10486|ZBX-10486]] for more information and available workarounds. 
- 
-=== Simple checks === 
- 
-There is a bug in **fping** versions earlier than v3.10 that mishandles duplicate echo replay packets. This may cause unexpected results for ''​icmpping'',​ ''​icmppingloss'',​ ''​icmppingsec''​ items. It is recommended to use the latest version of **fping**. Please see  [[https://​support.zabbix.com/​browse/​ZBX-11726|ZBX-11726]] for more details. 
- 
-=== SNMP checks === 
- 
-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. 
- 
-=== 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. 
- 
-=== SNMP traps === 
- 
-The %%"​net-snmp-perl"​%% package, needed for SNMP traps, has been removed in RHEL/CentOS 8.0-8.2; re-added in RHEL 8.3.  
- 
-So if you are using RHEL 8.0-8.2, the best solution is to upgrade to RHEL 8.3; if you are using CentOS 8.0-8.2, you may wait for CentOS 8.3 or use a package from EPEL. 
- 
-Please also see [[https://​support.zabbix.com/​browse/​ZBX-17192|ZBX-17192]] for more information. 
- 
-=== 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 === 
- 
-It has been observed that frontend locales may flip without apparent logic, i. e. some pages (or parts of pages) are displayed in one language while other pages (or parts of pages) in a different language. Typically 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) 
- 
-=== PHP 7.3 opcache configuration === 
- 
-If %%"​%%opcache%%"​%% is enabled in the PHP 7.3 configuration,​ Zabbix frontend may show a blank screen when loaded for the first time. This is a registered [[https://​bugs.php.net/​bug.php?​id=78015|PHP bug]]. To work around this, please set the %%"​%%opcache.optimization_level%%"​%% parameter to ''​0x7FFFBFDF''​ in the PHP configuration (php.ini file). 
- 
-=== Graphs === 
- 
-Changes to Daylight Saving Time (DST) result in irregularities when displaying X axis labels (date duplication,​ date missing, etc). 
- 
-=== Log file monitoring === 
- 
-''​log[]''​ and ''​logrt[]''​ items repeatedly reread log file from the beginning if file system is 100% full and the log file is being appended (see [[https://​support.zabbix.com/​browse/​ZBX-10884|ZBX-10884]] for more information). 
- 
-=== Slow MySQL queries === 
- 
-Zabbix server generates slow select queries in case of non-existing values for items. This is caused by a known [[https://​bugs.mysql.com/​bug.php?​id=74602|issue]] in MySQL 5.6/5.7 versions. A workaround to this is disabling the index_condition_pushdown optimizer in MySQL. For an extended discussion, see [[https://​support.zabbix.com/​browse/​ZBX-10652|ZBX-10652]]. 
- 
-=== API === 
- 
-The **output** parameter does not work properly with the ''​history.get''​ method. 
- 
-=== API login === 
- 
-A large number of open user sessions can be created when using custom scripts with the ''​user.login''​ [[:​manual/​api/​reference/​user/​login|method]] without a following ''​user.logout''​. 
- 
-=== IPv6 address issue in SNMPv3 traps === 
- 
-Due to a net-snmp bug, IPv6 address may not be correctly displayed when using SNMPv3 in SNMP traps. For more details and a possible workaround, see [[https://​support.zabbix.com/​browse/​ZBX-14541|ZBX-14541]]. 
- 
-=== Trimmed long IPv6 IP address in failed login information === 
- 
-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. 
- 
-=== Zabbix agent checks on Windows ===  
-Non-existing DNS entries in a ''​Server''​ parameter of Zabbix agent configuration file (zabbix_agentd.conf) may 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.