graphite-ch-optimizer doesn't close connections
Closed this issue · 0 comments
Secathor commented
Looks like we've found some strange behaviour with graphite-ch-optimizer not closing unix sockets.
In logs it looks as follows and graphite-ch-optimizer exits:
Dec 27 10:42:50 host graphite-ch-optimizer[8343]: time="2019-12-27 10:42:50 CET" level=error msg="Fail: could not load time location: too many open files"
Dec 27 10:42:50 host graphite-ch-optimizer[8343]: time="2019-12-27 10:42:50 CET" level=fatal msg="Ping ClickHouse server failed: could not load time location: too many open files"
Dec 27 10:42:50 host systemd[1]: graphite-ch-optimizer.service: Main process exited, code=exited, status=1/FAILURE
Dec 27 10:42:50 host systemd[1]: graphite-ch-optimizer.service: Failed with result 'exit-code'.
It was also visible in our Zabbix: