Re: [squid-users] 2.4 S 2 aborts after first request

Sorry, i should have sent more data
It is a Linux 7.1 system, with gcc version 2.96-81. When using GDB to debug I get the following after a request:
Starting program: /usr/local/squid/bin/squid -N
Program received signal SIGSEGV, Segmentation fault.
dlinkAdd (data=0x8439898, m=0x843a29c, list = 0x818c4c0) at tools.c:769
tools.c: no such file or directory. in tools.c

Also in the cache.log I see
FATAL: Received Segment Violation...dying
page faults with pyhsical i/o: 351
Memory usage
total space in arena: 2184KB
Ordinary blocks: 2162KB 2 blks
Small blocks: 0 KB 0 blks
holding blocks: 176KB 1 blks
Free Small blocks 0 KB
Free ordinary blocks: 21 KB
Total in use 2338 KB 107%

I hope that this helps.

> On Wed, Aug 29, 2001, tim pearson wrote:
> > I just created a server with Squid 2.4 stable 2 in hopes of fixing an issue where stable 1 would randomly abort. Now it will abort after the first request. This is on a dual pIII 1gig with 1 gig of memory.
> > To diskd is enabled, but I am still figuring out what to set in the squid.conf file. Also we are forced to use smartfilter by corporate so that is installed. Smartfilter will edit the source files to so it has an entry in the squid.conf file. Any suggestions?
> >
>
> Whats the abort look like? Which platform is it running on?
> Which version of which compiler?
>
> Also, can you run squid inside gdb (gdb squid, then run -N) and
> when it panics tell us where it panics?
>
>
>
>
> Adrian
>
>

-- 
_______________________________________________
Talk More, Pay Less with Net2Phone Direct(R), up to 1500 minutes free! 
http://www.net2phone.com/cgi-bin/link.cgi?143