From owner-freebsd-stable Thu Oct 23 09:35:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA08672 for stable-outgoing; Thu, 23 Oct 1997 09:35:12 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from home.shvetc.marka.net.ua (home.shvetc.marka.net.ua [193.193.219.185]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08644 for ; Thu, 23 Oct 1997 09:34:44 -0700 (PDT) (envelope-from eugene@shvetc.marka.net.ua) Received: from eugene.shvetc.marka.net.ua (eugene.shvetc.marka.net.ua [193.193.219.187]) by home.shvetc.marka.net.ua (8.8.7/8.8.7) with SMTP id TAA01433; Thu, 23 Oct 1997 19:30:46 +0300 (EEST) From: "Eugene Shvetc" To: "Ernie Elu" Cc: Subject: Re: Squid 1.1.16 breaking under load Date: Thu, 23 Oct 1997 19:30:43 +0300 Message-ID: <01bcdfd1$024d23a0$bbdbc1c1@eugene.shvetc.marka.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >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. > I have installed squid-1.1.16 at October, 6 and does not have any problems with it, I even does not use RunCache, run it as "/usr/local/sbin/squid -DsY &" in my rc.local file, and it does not fly out.