Re: Squid 1.1.7 Segment Violation at Startup

Natchu Vishnu Priya:
> On Thu, 27 Feb 1997, Balint Nagy Endre wrote:
>
> > > > On Thu, 27 Feb 1997, Bryan Christianson wrote:
> > > > | I attempted to upgrade my Squid 1.1.5 to 1.1.7 and receive the following
> > > > | messages in cache.log. The FATAL seems to occur when the first access is
> > > > | made to the cache by a client.
> > > On Thu, 27 Feb 1997, Michael J. Maravillo wrote:
> > > > same case here but doesn't happen at startup. i upgraded from
> > > > 1.1.6 to 1.1.7 yesterday. today, as of this writing, squid has
> > > > died five times: 9:26 am, 12:22 pm, 1:07 pm, 1:51 pm, 1:54 pm.
> > > > i'm using linux 2.0.29.
> > > As the others have had problems, so have I. Firstly it ran OK for
> > > a couple of hours, then degraded to crashing every 10 mins or so, with an
> > > error message about an ABORT TRAP, then eventually, it wouldnt even start
> > > up.
> > Hmm. Linux-2.0.28, Squid-1.1.7, libc-5.3.12-8,
> > 370 conn in one day on the one
> > 196 conn in 9 hours on the other
> > no crashes.
> Hmm. Linux-2.0.27, Squid-1.1.7, libc-5.0..9 :)
> 22675 connections a day
> crashed 8 timed in 20 hrs.
> > The standard question:
> > Did you re-run configure before make?
> Yes I did.... all patches on.
> maybe diff.. I had useragent and mime header logs on.
First try a libc upgrade, the try to turn off useragent and mime header logs -
I never used that part of code. Now I'll upgrade the third (linux) squid and
do some stress-test on it (but that will be a few thousand requests only).
Andrew.
Received on Thu Feb 27 1997 - 00:23:20 MST