-
Problem report
-
Resolution: Fixed
-
Blocker
-
5.2.1
-
Sprint 70 (Nov 2020)
-
1
Zabbix has been upgraded yesterday from Zabbix 5.0.2 to 5.2.1.
This morning zabbix it started to crash.
8410:20201113:070520.966 Got signal [signal:11(SIGSEGV),reason:1,refaddr:(nil)]. Crashing ... ... 8410:20201113:070520.966 === Backtrace: === 8410:20201113:070520.968 12: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](zbx_backtrace+0x4e) [0x555bf09ce4eb] 8410:20201113:070520.968 11: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](zbx_log_fatal_info+0x17f) [0x555bf09ce7e0] 8410:20201113:070520.968 10: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](+0x1f5029) [0x555bf09cf029] 8410:20201113:070520.968 9: /lib/x86_64-linux-gnu/libpthread.so.0(+0x12980) [0x7faf8ccf3980] 8410:20201113:070520.968 8: /lib/x86_64-linux-gnu/libc.so.6(+0xa9c6a) [0x7faf89a3bc6a] 8410:20201113:070520.968 7: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](+0x12fb79) [0x555bf0909b79] 8410:20201113:070520.968 6: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](lld_manager_thread+0x361) [0x555bf090a4e3] 8410:20201113:070520.968 5: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](zbx_thread_start+0x37) [0x555bf09dd969] 8410:20201113:070520.968 4: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](MAIN_ZABBIX_ENTRY+0x1076) [0x555bf0825862] 8410:20201113:070520.968 3: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](daemon_start+0x2ff) [0x555bf09ce0be] 8410:20201113:070520.968 2: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](main+0x305) [0x555bf082478d] 8410:20201113:070520.968 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7faf899b3bf7] 8410:20201113:070520.968 0: /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.888605 sec](_start+0x2a) [0x555bf08237ba] ... 8306:20201113:070520.973 One child process died (PID:8410,exitcode/signal:1). Exiting ... 8306:20201113:070521.015 syncing history data... ... 8306:20201113:071302.180 Zabbix Server stopped. Zabbix 5.2.1 (revision 4d0d532fb0).
There are some troubles with DB (cluster, galera) where one node failed, but do not think it could be related.
- caused by
-
ZBXNEXT-6247 Skip identical values in LLD processing
- Closed
- is duplicated by
-
ZBX-18731 Zabbix server 5.2.1 LLD manager SIGSEGV
- Closed