Public bug reported:
Squid crashes unexpectedly after some time under moderate to high load.
Symptoms:
systemctl status squid.service shows Active: failed (Result: exit-code)
journalctl -xeu squid.service shows:
squid.service: Killing process <PID> (pinger) with signal SIGKILL.
squid.service: Failed with result 'exit-code'.
Multiple: squid.service: Unit process <PID> (pinger) remains running
after unit stopped.
Many leftover pinger child processes after Squid stops.
No CPU/RAM exhaustion at crash time.
No “Too many open files” after raising LimitNOFILE to 65534.
After disabling pinger with:
text
pinger_enable off
in squid.conf, Squid becomes stable and no further crashes occur.
This suggests the known pinger/ICMP bug (buffer overrun / crash in
pinger, especially with ICMPv6) affects this newer version.
** Affects: squid (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2157783
Title:
Squid 5.9 crashes under load due to pinger process; many leftover
pinger processes, systemd kills pinger with SIGKILL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2157783/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
