RE: [squid-users] coredumps on 2.7

From: Mike Marchywka <marchywka_at_hotmail.com>
Date: Fri, 27 Nov 2009 07:41:15 -0500

----------------------------------------
> Date: Fri, 27 Nov 2009 02:03:06 -0800
> From: jdmls_at_yahoo.com
> To: squid-users_at_squid-cache.org
> Subject: Re: [squid-users] coredumps on 2.7
>
> From: Quin Guin
>> I am running 2.7-STABALE6 on many squid servers and just recently in the last
>> few days I am seeing a lot of coredumps. I have most of the coredumps still and
>> I would like to understand what happened?
>> I did search the mailing list and I used gdb to generate a stack trace but it
>> didn't give ME a lot of useful information.
>> [XXXXXX_at_cach2 cache]# gdb squid core.31033
>> GNU gdb Red Hat Linux (6.3.0.0-1.132.EL4rh)
>> Copyright 2004 Free Software Foundation, Inc.
>> GDB is free software, covered by the GNU General Public License, and you are
>> welcome to change it and/or distribute copies of it under certain conditions.
>> Type "show copying" to see the conditions.
>> There is absolutely no warranty for GDB. Type "show warranty" for details.
>> This GDB was configured as "i386-redhat-linux-gnu"...squid: No such file or
>> directory.
>> Core was generated by `(squid)'.
>> Program terminated with signal 6, Aborted.
>> #0 0x0054a7a2 in ?? ()
>> (gdb) where
>> #0 0x0054a7a2 in ?? ()
>> #1 0x0058f7a5 in ?? ()
>> #2 0x00000000 in ?? ()
>> (gdb)
>> So I was wondering if someone could point me to where I can find more
>> information on interpreting the coredumps.
>
> I think you would have to compile squid with debuging to see something usefull... no?
> "squid: No such file or directory."
> If it is squid that says this, do you see anything in the logs about a missing file or directory?
> Maybe try an strace and check what is the last access attempt before it coredumps.

Depending on your situation, it may help to backup and do
some simple things esp if you can't find any suspects that may cause
a problem to start a few days ago.
When I was just starting, I tried to invoke it in foreground from
command line, squid -f conf , and it either told me more or less what
was wrong or there was a log file telling me what it didn't like(  When
you get it working in fg, then it mysteriously dies as a service, in my
case it turned out to be things like ownership or permissions of swap
or log dirs). I'm not sure how long it takes to produce your dump but
invoking in fg may be an option for testing once you have suspects or
can get failures in an hour or so.
A gradually worsening problem suggests something is getting used up,
hard to know what else you may have working with squid. This could be anything,
is someone changing permissions on directories you use, etc.

>
> JD
>
>
>
                                               
_________________________________________________________________
Windows 7: I wanted simpler, now it's simpler. I'm a rock star.
http://www.microsoft.com/Windows/windows-7/default.aspx?h=myidea?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_myidea:112009
Received on Fri Nov 27 2009 - 12:41:22 MST

This archive was generated by hypermail 2.2.0 : Fri Nov 27 2009 - 12:00:04 MST