Search squid archive

Re: squid crashes rapidly with glibc errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



fre 2007-04-27 klockan 15:46 +0400 skrev Anton Golubev:
> Hello squid users,
> 
> I'm trying to figure out, why usually quite stable squid started to
> crash rapidly on newly installed server with CentOS 4.4. Time to crash
> is up to several seconds, then moderate requests load is applied.
> Relevant log records are following:
> 
> 2007/04/25 17:42:54|   Validated 10907 Entries
> 2007/04/25 17:42:54|   store_swap_size = 107484k
> 2007/04/25 17:42:54| storeLateRelease: released 0 objects
> *** glibc detected *** corrupted double-linked list: 0x0a378818 ***

Ugh.. something stomped on anothers memory.

Can you try if this problem can be trapped in more detail using
valgrind?

Install valgrind and valgrind-devel

Rebuild Squid with the --with-valgrind option

Start Squid using valgrind and try making it crash (or at least get ugly
warnings from valgrind). Squid will run a bit slower, so some patience
may be needed.

Regards
Henrik

Attachment: signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux