-
Problem report
-
Resolution: Fixed
-
Critical
-
3.0.14, 3.4.5
-
Team C
-
Sprint 27
-
0.5
Hi! I have problem with stopping zabbix server every 5-6 hours operation.
There text from server log files:
1295:20180206:155238.984 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0xffffffb0]. Crashing ...
1295:20180206:155238.984 ====== Fatal information: ======
1295:20180206:155238.984 program counter not available for this architecture
1295:20180206:155238.984 === Registers: ===
1295:20180206:155238.984 register dump not available for this architecture
1295:20180206:155238.984 === Backtrace: ===
1295:20180206:155238.985 3: 0x4a422b <zbx_log_fatal_info+0x9b> at /usr/local/sbin/zabbix_server
1295:20180206:155238.985 2: 0x4a464b <zbx_set_common_signal_handlers+0x29b> at /usr/local/sbin/zabbix_server
1295:20180206:155238.985 1: 0x80440ab37 <pthread_sigmask+0x507> at /lib/libthr.so.3
1295:20180206:155238.985 0: 0x80440a22c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
1295:20180206:155238.985 === Memory map: ===
1287:20180206:155238.985 item "500280f6-d8d8-cf3c-e4fa-c37815b0f90b:vmware.vm.net.if.in[{$URL},{HOST.HOST},4000,pps]" became supported
1295:20180206:155238.985 memory map not available for this platform
1295:20180206:155238.985 ================================
1277:20180206:155238.987 One child process died (PID:1295,exitcode/signal:1). Exiting ...
1319:20180206:155239.003 cannot read preprocessing service request
1277:20180206:155241.016 syncing history data...
1277:20180206:155241.024 syncing history data done
1277:20180206:155241.024 syncing trend data...
1277:20180206:155241.516 syncing trend data done
1277:20180206:155241.516 cannot remove shared memory for self-monitoring collector: [22] Invalid argument
1277:20180206:155241.516 Zabbix Server stopped. Zabbix 3.4.6 (revision 76823).
and
19769:20180203:232516.217 Got signal [signal:10(SIGBUS),reason:3,refaddr:0x803a1862d]. Crashing ... 19769:20180203:232516.217 ====== Fatal information: ====== 19769:20180203:232516.217 program counter not available for this architecture 19769:20180203:232516.217 === Registers: === 19769:20180203:232516.217 register dump not available for this architecture 19769:20180203:232516.217 === Backtrace: === 19769:20180203:232516.218 3: 0x4a422b <zbx_log_fatal_info+0x9b> at /usr/local/sbin/zabbix_server 19769:20180203:232516.218 2: 0x4a464b <zbx_set_common_signal_handlers+0x29b> at /usr/local/sbin/zabbix_server 19769:20180203:232516.218 1: 0x804409b37 <pthread_sigmask+0x507> at /lib/libthr.so.3 19769:20180203:232516.218 0: 0x80440922c <pthread_getspecific+0xe1c> at /lib/libthr.so.3 19769:20180203:232516.218 === Memory map: === 19769:20180203:232516.218 memory map not available for this platform 19769:20180203:232516.218 ================================ 19749:20180203:232516.221 One child process died (PID:19769,exitcode/signal:1). Exiting ... 19749:20180203:232518.273 syncing history data... 19749:20180203:232518.276 syncing history data done 19749:20180203:232518.276 syncing trend data... 19749:20180203:232518.422 syncing trend data done 19749:20180203:232518.422 cannot remove shared memory for self-monitoring collector: [22] Invalid argument 19749:20180203:232518.422 Zabbix Server stopped. Zabbix 3.4.6 (revision 76823).
