Date: Fri, 24 Oct 1997 10:15:17 +0000 (GMT) From: "Jonathan A. Zdziarski" <jonz@netrail.net> To: Ernie Elu <ernie@spooky.eis.net.au> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Squid 1.1.16 breaking under load Message-ID: <Pine.BSF.3.95q.971024101416.12178B-100000@netrail.net> In-Reply-To: <199710230745.RAA26944@spooky.eis.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
When I was experimenting with squid under Digital Unix, the process had the tendency to grow in virtual size until it would take up all the memory and die out. It's possible something similar's happening here, you can find out by doing a ps aux and looking at the vsize for a few hours while it's running. You may also want to install Gnu Malloc if you can find it. ------------------------------------------------------------------------- Jonathan A. Zdziarski NetRail Incorporated Systems Engineering Manager 230 Peachtree St. Suite 500 jonz@netrail.net Atlanta, GA 30303 http://www.netrail.net (888) - NETRAIL ------------------------------------------------------------------------- On Thu, 23 Oct 1997, Ernie Elu wrote: :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?Pine.BSF.3.95q.971024101416.12178B-100000>