Instalei o zabbix 3.4.6 no centos 7 com postgree. Estava funcionando normalmente, mas repentinamente o serviço zabbix-server começou a reiniciar e fica constantemente assim.
Segue log . Nao identifiquei nada específico que possa estar causando o problema.
9355:20180218:173021.162 7ffec01a0000-7ffec01a2000 r-xp 00000000 00:00 0 [vdso]
9357:20180218:173021.162 ================================
9356:20180218:173021.162 7feb3beda000-7feb3c0d9000 ---p 0000d000 fd:00 34459642 /usr/lib64/libiksemel.so.3.1.1
9355:20180218:173021.162 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
9356:20180218:173021.162 7feb3c0d9000-7feb3c0da000 r--p 0000c000 fd:00 34459642 /usr/lib64/libiksemel.so.3.1.1
9355:20180218:173021.163 ================================
9356:20180218:173021.163 7feb3c0da000-7feb3c0db000 rw-p 0000d000 fd:00 34459642 /usr/lib64/libiksemel.so.3.1.1
9355:20180218:173021.163 Please consider attaching a disassembly listing to your bug report.
9356:20180218:173021.163 7feb3c0db000-7feb3c107000 r-xp 00000000 fd:00 34218506 /usr/lib64/libpq.so.5.5
9355:20180218:173021.163 This listing can be produced with, e.g., objdump -DSswx zabbix_server.
9356:20180218:173021.163 7feb3c107000-7feb3c306000 ---p 0002c000 fd:00 34218506 /usr/lib64/libpq.so.5.5
9355:20180218:173021.163 ================================
9356:20180218:173021.166 7feb3c306000-7feb3c308000 r--p 0002b000 fd:00 34218506 /usr/lib64/libpq.so.5.5
9353:20180218:173021.166 One child process died (PID:9355,exitcode/signal:1). Exiting ...
9356:20180218:173021.183 7feb3c308000-7feb3c30a000 rw-p 0002d000 fd:00 34218506 /usr/lib64/libpq.so.5.5
9353:20180218:173023.178 syncing history data...
9353:20180218:173023.219 syncing history data done
9353:20180218:173023.220 syncing trend data...
9353:20180218:173023.241 syncing trend data done
9353:20180218:173023.242 Zabbix Server stopped. Zabbix 3.4.6 (revision 76823).
Segue log . Nao identifiquei nada específico que possa estar causando o problema.
9355:20180218:173021.162 7ffec01a0000-7ffec01a2000 r-xp 00000000 00:00 0 [vdso]
9357:20180218:173021.162 ================================
9356:20180218:173021.162 7feb3beda000-7feb3c0d9000 ---p 0000d000 fd:00 34459642 /usr/lib64/libiksemel.so.3.1.1
9355:20180218:173021.162 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
9356:20180218:173021.162 7feb3c0d9000-7feb3c0da000 r--p 0000c000 fd:00 34459642 /usr/lib64/libiksemel.so.3.1.1
9355:20180218:173021.163 ================================
9356:20180218:173021.163 7feb3c0da000-7feb3c0db000 rw-p 0000d000 fd:00 34459642 /usr/lib64/libiksemel.so.3.1.1
9355:20180218:173021.163 Please consider attaching a disassembly listing to your bug report.
9356:20180218:173021.163 7feb3c0db000-7feb3c107000 r-xp 00000000 fd:00 34218506 /usr/lib64/libpq.so.5.5
9355:20180218:173021.163 This listing can be produced with, e.g., objdump -DSswx zabbix_server.
9356:20180218:173021.163 7feb3c107000-7feb3c306000 ---p 0002c000 fd:00 34218506 /usr/lib64/libpq.so.5.5
9355:20180218:173021.163 ================================
9356:20180218:173021.166 7feb3c306000-7feb3c308000 r--p 0002b000 fd:00 34218506 /usr/lib64/libpq.so.5.5
9353:20180218:173021.166 One child process died (PID:9355,exitcode/signal:1). Exiting ...
9356:20180218:173021.183 7feb3c308000-7feb3c30a000 rw-p 0002d000 fd:00 34218506 /usr/lib64/libpq.so.5.5
9353:20180218:173023.178 syncing history data...
9353:20180218:173023.219 syncing history data done
9353:20180218:173023.220 syncing trend data...
9353:20180218:173023.241 syncing trend data done
9353:20180218:173023.242 Zabbix Server stopped. Zabbix 3.4.6 (revision 76823).
Comment