8 Known issues

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.

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 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 ZBX-4850 for more details.

ODBC checks

Zabbix server or proxy that uses MySQL as its database may or may not work correctly with MySQL ODBC library due to an upstream bug. Please see 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 issue.

HTTPS checks

Web scenarios using the https protocol and 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 ZBX-9879 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 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.

Alerter process crash in Centos/RHEL 7

Instances of a Zabbix server alerter process crash have been encountered in Centos/RHEL 7. Please see ZBX-10461 for details.

Web monitoring

Zabbix server leaks memory on CentOS 6, CentOS 7 and possibly other related Linux distributions due to an upstream bug when "SSL verify peer" is enabled in web scenarios. Please see ZBX-10486 for more information and available workarounds.

Macro functions

When \0 is used as the output option in macro functions it will work as designed, i.e. return the matched text, when server does the resolving (in trigger tags, notification messages), but not in cases when frontend does the resolving.

Compatibility issue with PHP 7.0

It has been observed that with PHP 7.0 importing a template with web monitoring triggers may fail due to incorrectly added double quotes to the web monitoring items in the trigger expressions. The issue goes away when upgrading PHP to 7.1.

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 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 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 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 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 ZBX-14541.

Known issues for 3.4.0 - 3.4.1

• The link for expanding macros when editing a map is missing in these versions.
• User macros do not work in the trapper item "Allowed hosts" field.

Known issues for 3.4.2

• When editing a network map with 'Expand macros' on, {HOST.*} macros are not resolved for trigger elements.

Known issues for 3.4.0 - 3.4.8

The logic of the Interface {#IFMACRO}: Link down trigger prototype in several SNMP module templates (e.g. Template Module Interfaces SNMPv2) leads to a problem resolving prematurely. Fixed by adding a recovery expression disallowing this in 3.4.9. For details, see: ZBX-13278.

Known issues for 3.4.0 - 3.4.9

• Remote commands executed on Zabbix server are displayed with an initial : colon in Reports → Action log.

Known issues for 3.4.0 - 3.4.10

• When proc.mem, proc.num agent items are invoked from the command line and contain a command line parameter (e.g. using the agent test mode: zabbix_agentd -t proc.num[,,,apache2]), two extra processes are counted, as the agent counts itself twice.

Known issues for 3.4.10

• Zabbix server 3.4.10 can only work with Zabbix proxies 3.4.10. Compatibility with other proxies from 3.4.x versions has been lost. Fixed for 3.4.11.

Known issues for 3.4.0 - 3.4.13

• In the hexadecimal to decimal conversion, in item value preprocessing, values containing a space aren't supported in numeric format. As a workaround, you may use a regular expression preprocessing step removing the space before the hexadecimal to decimal step.