Добрый день!
На прошлой неделе обновился до версии 2.2.2
А в пятницу споткнулся о то, что Zabbix Server свалился. Дважды.
Кусочки информации о краше, взятые из лога:
Code:
21591:20140221:153138.268 Got signal [signal:11(SIGSEGV),reason:1,refaddr:(nil)]. Crashing ... 21591:20140221:153138.268 ====== Fatal information: ====== 21591:20140221:153138.268 Program counter: 0xb51c81 21591:20140221:153138.268 === Registers: === ......... 21591:20140221:153138.270 === Backtrace: === 21591:20140221:153138.320 15: zabbix_server: history syncer #4 [synced 1 items in 0.042935 sec, syncing history](print_fatal_info+0x454) [0x80bb614] 21591:20140221:153138.320 14: zabbix_server: history syncer #4 [synced 1 items in 0.042935 sec, syncing history]() [0x80bbe30] 21591:20140221:153138.320 13: [0xa6140c] 21591:20140221:153138.320 12: /lib/libc.so.6() [0xb51c81] 21591:20140221:153138.320 11: /lib/libc.so.6(__strdup+0x25) [0xb51965] ............... 21591:20140221:153138.334 ================================ 21591:20140221:153138.334 Please consider attaching a disassembly listing to your bug report. 21591:20140221:153138.334 This listing can be produced with, e.g., objdump -DSswx zabbix_server. 21591:20140221:153138.334 ================================ 21567:20140221:153138.339 One child process died (PID:21591,exitcode/signal:255). Exiting ... 21567:20140221:153140.340 syncing history data... 21567:20140221:153140.344 syncing history data done 21567:20140221:153140.344 syncing trends data... 21567:20140221:153142.693 syncing trends data done 21567:20140221:153142.704 Zabbix Server stopped. Zabbix 2.2.2 (revision 42525).
Code:
26808:20140221:173135.397 Got signal [signal:11(SIGSEGV),reason:1,refaddr:(nil)]. Crashing ... 26808:20140221:173135.398 ====== Fatal information: ====== 26808:20140221:173135.398 Program counter: 0x431c81 26808:20140221:173135.398 === Registers: === .............. 26808:20140221:173135.401 === Backtrace: === 26808:20140221:173135.402 15: zabbix_server: history syncer #1 [synced 1 items in 0.006843 sec, syncing history](print_fatal_info+0x454) [0x80bb614] 26808:20140221:173135.402 14: zabbix_server: history syncer #1 [synced 1 items in 0.006843 sec, syncing history]() [0x80bbe30] 26808:20140221:173135.402 13: [0x56640c] 26808:20140221:173135.402 12: /lib/libc.so.6(-0xff4ae37f) [0x431c81] 26808:20140221:173135.402 11: /lib/libc.so.6(__strdup+0x25) [0x431965] ............... 26808:20140221:173135.417 ================================ 26808:20140221:173135.417 Please consider attaching a disassembly listing to your bug report. 26808:20140221:173135.418 This listing can be produced with, e.g., objdump -DSswx zabbix_server. 26808:20140221:173135.418 ================================ 26787:20140221:173135.421 One child process died (PID:26808,exitcode/signal:255). Exiting ... 26787:20140221:173137.422 syncing history data... 26787:20140221:173137.427 syncing history data done 26787:20140221:173137.427 syncing trends data... 26787:20140221:173139.724 syncing trends data done 26787:20140221:173139.724 Zabbix Server stopped. Zabbix 2.2.2 (revision 42525).
Comment