- 7 Known issues
- Global event correlation
- IPMI checks
- SSH checks
- ODBC checks
- Incorrect request method parameter in items
- HTTPS checks
- Web monitoring and HTTP agent
- Simple checks
- SNMP checks
- Alerter process crash in Centos/RHEL 7
- Flipping frontend locales
- Compatibility issue with PHP 7.0
- PHP 7.3 opcache configuration
- Graphs
- Log file monitoring
- Slow MySQL queries
- API
- API login
- IPv6 address issue in SNMPv3 traps
- Trimmed long IPv6 IP address in failed login information
- IE11 issue with map resizing in dashboard widgets
- Known issues in 4.2.0, 4.2.1
- Known issues in 4.2.2
7 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 in various ways on Linux and UNIX systems.
Incorrect request method parameter in items
The request method parameter, used only in HTTP checks, may be incorrectly set to '1', a non-default value for all items as a result of upgrade from a pre-4.0 Zabbix version. For details on how to fix this situation, see ZBX-19308.
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
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 upstream bug when "SSL verify peer" is enabled in web scenarios or HTTP agent. Please see 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
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.
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 Apache. Please see ZBX-10911 for more information.
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.
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 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 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 (fixed in 4.2.5).
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.
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.
IE11 issue with map resizing in dashboard widgets
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.
Known issues in 4.2.0, 4.2.1
- IPMI pollers are unable to process more than 60 items per minute. Fixed in 4.2.2.
- You may encounter the issue of 100% CPU usage by IPMI pollers if using OpenIPMI version 2.0.26 and above. Fixed in 4.2.2.
Known issues in 4.2.2
- This version requires write permissions to the
assetsdirectory for the web server user. This requirement, however, would break those installations of the frontend where the web server has no write permissions to the document root (see ZBX-16180 for details). As a result, this requirement is rolled back in 4.2.3.