-
Problem report
-
Resolution: Fixed
-
Critical
-
5.2.0rc2
-
None
-
GNU/Linux
-
Sprint 69 (Oct 2020)
-
0.25
Steps to reproduce:
Request diagnostics like
zabbix_server -R diaginfo
or
zabbix_server -R diaginfo=locks
Result:
In server log file:
zabbix_server [49846]: ERROR [file:diag.c,line:903] Something impossible has just happened. 49846:20201022:215144.593 === Backtrace: === 49846:20201022:215144.593 6: sbin/zabbix_server(zbx_backtrace+0x53) [0x55b113114433] 49846:20201022:215144.593 5: sbin/zabbix_server(zbx_diag_log_info+0x5a2) [0x55b11329b212] 49846:20201022:215144.593 4: sbin/zabbix_server(MAIN_ZABBIX_ENTRY+0xc52) [0x55b112cf44a2] 49846:20201022:215144.593 3: sbin/zabbix_server(daemon_start+0x1e7) [0x55b113113f27] 49846:20201022:215144.593 2: sbin/zabbix_server(main+0x42b) [0x55b112cd1a7b] 49846:20201022:215144.593 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7fae0f6a5cca] 49846:20201022:215144.593 0: sbin/zabbix_server(_start+0x2a) [0x55b112cf236a]
Expected:
Statistics logged.
Patch diag_add_locks_info.patch helps.
Discovered by zux.