-
Incident report
-
Resolution: Won't fix
-
Critical
-
None
-
2.2.10
-
None
zabbix_proxy process quit soon every time I restart it, it should OOM killer killed it from my examining zabbix log and dmesg,but I am not sure why this happened
zabbix proxy log
26899:20151130:085816.446 proxy #62 started java poller #13
26901:20151130:085816.457 proxy #64 started java poller #15
26900:20151130:085816.462 proxy #63 started java poller #14
26898:20151130:085816.464 proxy #61 started java poller #12
26902:20151130:085816.468 proxy #65 started java poller #16
26903:20151130:085816.469 proxy #66 started self-monitoring #1
26800:20151130:085822.273 One child process died (PID:26838,exitcode/signal:9). Exiting ...
26800:20151130:085833.619 syncing history data...
26800:20151130:085833.619 syncing history data done
26800:20151130:085833.622 Zabbix Proxy stopped. Zabbix 2.2.10 (revision 54806).
dmesg log
Out of memory: Kill process 26800 (zabbix_proxy) score 34 or sacrifice child
Killed process 26839 (zabbix_proxy) total-vm:1264300kB, anon-rss:17420kB, file-rss:4kB