Date: Thu, 23 Oct 1997 17:45:37 +1000 (EST) From: Ernie Elu <ernie@spooky.eis.net.au> To: freebsd-isp@freebsd.org Subject: Squid 1.1.16 breaking under load Message-ID: <199710230745.RAA26944@spooky.eis.net.au>
next in thread | raw e-mail | index | archive | help
Anyone had squid 1.1.16 break under load? It comes up with a can't xmalloc memory error and squid quits with a signal 6 for a few minutes until RunCache restarts it. Seem to not happen under light loads. The kern.log is full of messages like the following: Oct 23 15:03:08 gammy /kernel: pid 637 (squid), uid 65534: exited on signal 6 Oct 23 15:11:40 gammy /kernel: pid 739 (squid), uid 65534: exited on signal 6 Oct 23 15:22:53 gammy /kernel: pid 814 (squid), uid 65534: exited on signal 6 Oct 23 15:39:28 gammy /kernel: pid 861 (squid), uid 65534: exited on signal 6 Oct 23 15:50:59 gammy /kernel: pid 1829 (squid), uid 65534: exited on signal 6 Oct 23 16:00:06 gammy /kernel: pid 2445 (squid), uid 65534: exited on signal 6 Oct 23 16:13:38 gammy /kernel: pid 2539 (squid), uid 65534: exited on signal 6 It's only started happening since I went from 1.1.15 to 1.1.16 yesterday. I also cvsup'd the latest 2.2.2-STABLE and built a fresh kernel at the same time to complicate things. I am keen to know if anyone else has had the same problem, or is it just unique to my server in which case I will set up a fresh drive and swap it out. - Ernie.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710230745.RAA26944>