-
Incident report
-
Resolution: Duplicate
-
Critical
-
None
-
3.4.3
Dear Sirs,
Please note that since we have upgraded zabbix from 3.2.6 to 3.4.3 , we have experienced an intermittent crash on zabbix server.
we are solving the problem by restarting the running services.
the logs shows that there'ss "too many open files", we have increased the open file limit but still crashing, although the files opened are not reaching the cap.
Below are the logs of the latest crash, please advise if anything can be done to prevent this issue from happening again:
22626:20171106:072016.091 server #2597 started [icmp pinger #326] 22625:20171106:072016.091 server #2596 started [icmp pinger #325] 22630:20171106:072016.091 server #2601 started [icmp pinger #330] 22647:20171106:072016.092 server #2617 started [icmp pinger #346] 22601:20171106:072016.092 server #2577 started [icmp pinger #306] 22639:20171106:072016.092 server #2610 started [icmp pinger #339] 22636:20171106:072016.094 server #2607 started [icmp pinger #336] 22656:20171106:072017.059 server #2624 started [preprocessing worker #1] 22657:20171106:072017.725 server #2625 started [preprocessing worker #2] 22658:20171106:072017.733 server #2626 started [preprocessing worker #3] 19062:20171106:072023.712 sending configuration data to proxy "Zabbix Access proxy" at "193.227.188.106", datalen 403791 19032:20171106:072029.168 sending configuration data to proxy "Zabbix System proxy" at "194.126.19.42", datalen 1678500 18978:20171106:072040.535 item "Nutanix system:cstControllerVMStatus[0733bc58-aaf7-4beb-8eaa-7e721cdc3749.]" became not supported: snmp_parse_oid(): cannot parse OID "cstControllerVMStatus.2". zabbix_server [22654]: failed to open log file: [24] Too many open files zabbix_server [22654]: failed to write [cannot accept incoming IPC connection: [24] Too many open files] into log file 22656:20171106:072046.939 cannot read preprocessing service request 22657:20171106:072046.939 cannot read preprocessing service request 22658:20171106:072046.940 cannot read preprocessing service request 20318:20171106:072046.941 cannot write to IPC socket: Broken pipe 20176:20171106:072046.941 cannot write to IPC socket: Broken pipe 20318:20171106:072046.942 cannot send data to preprocessing service 20176:20171106:072046.942 cannot send data to preprocessing service 20304:20171106:072046.942 cannot write to IPC socket: Broken pipe 20304:20171106:072046.942 cannot send data to preprocessing service 19965:20171106:072046.943 cannot write to IPC socket: Broken pipe 19965:20171106:072046.943 cannot send data to preprocessing service 19957:20171106:072046.943 cannot write to IPC socket: Broken pipe 20316:20171106:072046.943 cannot write to IPC socket: Broken pipe 19957:20171106:072046.943 cannot send data to preprocessing service 20316:20171106:072046.943 cannot send data to preprocessing service 17457:20171106:072046.944 One child process died (PID:22654,exitcode/signal:1). Exiting ... 19811:20171106:072047.209 cannot write to IPC socket: Broken pipe 19635:20171106:072047.212 cannot write to IPC socket: Broken pipe 19614:20171106:072047.212 cannot write to IPC socket: Broken pipe 20223:20171106:072047.214 cannot write to IPC socket: Broken pipe 17457:20171106:072048.969 syncing history data... 17457:20171106:072049.009 syncing history data done 17457:20171106:072049.009 syncing trend data... 17457:20171106:072052.278 syncing trend data done 17457:20171106:072052.278 Zabbix Server stopped. Zabbix 3.4.3 (revision 73588).
Thank you in advance
Regards,
- duplicates
-
ZBX-12984 Zabbix Server restarting continuously after upgrade to 3.4.3
-
- Closed
-