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 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 .
Some Linux distributions like Debian, Ubuntu do not support encrypted private keys (with passphrase) if the libssh2 library is installed from packages. Please see for more details.
Áú»¢¶Ä²© server or proxy that uses MySQL as its database may or may not work correctly with MySQL ODBC library due to an . Please see for more information and available workarounds.
XML data queried from Microsoft SQL Server may get truncated to 2033 characters due to a Microsoft .
Web scenarios using the https protocol and Áú»¢¶Ä²© 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 for more information and available workarounds.
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 for more details.
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 Áú»¢¶Ä²© server if the SourceIP parameter is set in the Áú»¢¶Ä²© 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 Áú»¢¶Ä²© server to stop working. A local patch for the net-snmp package on OpenBSD was applied and will be released with OpenBSD 6.3.
Instances of a Áú»¢¶Ä²© server alerter process crash have been encountered in Centos/RHEL 7. Please see for details.
Áú»¢¶Ä²© server leaks memory on CentOS 6, CentOS 7 and possibly other related Linux distributions due to an when "SSL verify peer" is enabled in web scenarios. Please see for more information and available workarounds.
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.
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.
Changes to Daylight Saving Time (DST) result in irregularities when displaying X axis labels (date duplication, date missing, etc).
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 for more information).
Áú»¢¶Ä²© server generates slow select queries in case of non-existing values for items. This is caused by a known 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 .
The output parameter does not work properly with the history.get
method.
A large number of open user sessions can be created when using custom scripts with the user.login
method without a following user.logout
.
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 .
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: .
:
colon in Reports ¡ú Action log.zabbix_agentd -t proc.num[,,,apache2]
), two extra processes are counted, as the agent counts itself twice.