Why dont you try increasing debug_options and looking for answers in Cache.log ? That usually works. Salu2 Diego Amadey -----Mensaje original----- De: Diego Woitasen [mailto:diegows@xxxxxxxxxxxx] Enviado el: Miércoles, 30 de Diciembre de 2009 09:45 a.m. Para: squid-users@xxxxxxxxxxxxxxx Asunto: Squid Core Dump Hi, My Squid is crashing with a segfault several times a day. I've enabled coredumps, squid is compiled with -g and I've installed debug libraries (libc6-dbg) but I can't find where Squid crash. root@mrelpy01:/mnt/coredumps/proxy1# gdb /usr/sbin/squid core.30115 GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"... Core was generated by `(squid) -D -YC'. Program terminated with signal 11, Segmentation fault. [New process 30115] [New process 30336] [New process 30335] [New process 30334] [New process 30333] [New process 30332] [New process 30331] [New process 30330] [New process 30329] [New process 30328] [New process 30327] [New process 30326] [New process 30325] [New process 30324] [New process 30323] [New process 30322] [New process 30321] #0 0x00007ff59a5f828d in ?? () (gdb) bt #0 0x00007ff59a5f828d in ?? () #1 0x00007fff72b41f30 in ?? () #2 0x00007fff72b42150 in ?? () #3 0x0000000000000208 in ?? () #4 0x0000000000000000 in ?? () (gdb) What can I do to see where is crashing? May be this is a gdb question but is Squid related so I post it here. Regards, Diego -- Diego Woitasen XTECH No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.431 / Virus Database: 270.14.123/2594 - Release Date: 12/30/09 07:27:00
