Re: [squid-users] Squid 3.3.5 dump core

On Jun 5, 2013, at 3:09 AM, C. Pelissier <Pelissier.C_at_onera.fr> wrote:

> Under Solaris 10 squid 3.3.5 dump core every 10 minutes even with a very
> low traffic.
> squid 3.3.4 was stable.
>
>
> pstack core.squid.9897
> core 'core.squid.9897' of 9897: (squid-1) -s
> fea6c067 _lwp_kill (1, 6) + 7
> fea13883 raise (6) + 1f
> fe9f29e1 abort (83e6f08, 84aacd0, 8046e18, 82cf171, 83b575e,
> 83b4703) + cd
> 08166d5c _Z8ctx_exiti (83b575e, 83b4703, 11f, 84aacd0)
> 082cf171 _ZN12ACLChecklist9matchNodeERK7ACLListb (8e1dc80, 8601df8, 0,
> 0) + d1
> 082cf7db _ZN12ACLChecklist10matchNodesEPK7ACLListb (8e1dc80, 8601de0,
> 0, 83e6f08, 8cf9978, 83e6f08) + 53
> 082cfc93 _ZN12ACLChecklist12matchAclListEPK7ACLListb (8e1dc80, 8601de0,
> 0, 84aace0) + 23
> 082cff77 _ZN12ACLChecklist15checkAccessListEv (8e1dc80, 1, 40, 7,
> 83e6f08, 8e1dce4) + 3f
> 082d02b9 _ZN12ACLChecklist16matchNonBlockingEv (8e1dc80, 83b58bd, 0,
> 16) + 89
> 082d07b1 _ZN12ACLChecklist16nonBlockingCheckEPFv7allow_tPvES1_
> (8e1dc80, 815b810, 8c29a90, 81255bd) + 41
> 0815b8fc _ZN20ClientRequestContext17clientAccessCheckEv (8c29a90, 0, 0,
> 0, 0, 0) + b8
> 081593dc _ZN17ClientHttpRequest10doCalloutsEv (8d05980, 8d080b0,
> 8047148, 8382fcf, 85fdb20, 0) + 110
> 0815d121 _ZN20ClientRequestContext16hostHeaderVerifyEv (8c29a90,
> 8c7a630, a, 80471b0, 80471b0, 8047250) + 92d
> 08159331 _ZN17ClientHttpRequest10doCalloutsEv (8d05980, 8d05980, 0, 1)
> + 65
> 0813c2b9 _ZN13ConnStateData19clientParseRequestsEv (8cf9978, 83a5441,
> 814109a, 8cf9978) + 1bd5
> 081410ac _ZN13ConnStateData17clientReadRequestERK14CommIoCbParams
> (8cf9978, 8d26ff8, 8047608, 8d26fec) + 2dc
> 0814bd31 _ZN13CommCbMemFunTI13ConnStateData14CommIoCbParamsE6doDialEv
> (8d26fec, 8d26fd0, 0, 8d26fd0) + 2d
> 0814bdd2 _ZN9JobDialerI13ConnStateDataE4dialER9AsyncCall (8d26fec,
> 8d26fd0, 8047648, 83e6f08) + 2e
> 0814bf83
> _ZN10AsyncCallTI13CommCbMemFunTI13ConnStateData14CommIoCbParamsEE4fireEv
> (8d26fd0, f0, 8047698, 82d11ca) + 13
> 082d12e1 _ZN9AsyncCall4makeEv (8d26fd0, 857a1c8, 8047698, 82d4c3b, 0,
> 0) + 125
> 082d4e1d _ZN14AsyncCallQueue8fireNextEv (8603720, 80476e0, 8e7305c,
> 82d5027) + 1f5
> 082d5041 _ZN14AsyncCallQueue4fireEv (8603720, 80477f0, 8047728,
> 81850ab, 8047750, 8047828) + 2d
> 081850b4 _ZN9EventLoop13dispatchCallsEv (8047820, 80477f0, 1, 0) + 14
> 0818541c _ZN9EventLoop7runOnceEv (8047820, 8047828, 8185582, 8047820) +
> f8
> 0818558d _ZN9EventLoop3runEv (8047820, 80477f0, 8047c78, 81ffcc3) + 19
> 081ff4a9 _Z9SquidMainiPPc (2, 8047cd8, 83e6f08, 849d2a8) + 585
> 081ffd66 main (2, 8047cd8, 8047ce4) + 16
> 080fc3dc _start (2, 8047dc0, 8047dca, 0, 8047dcd, 8047dda) + 80
>

Is the message

2013/06/02 20:15:40 kid1| assertion failed: Checklist.cc:287: "!needsAsync && !matchFinished"

in your cache.log? If so, I've encountered this as well, and have seen it with other versions of squid. I'm using this patch so squid doesn't die when this occurs, but I don't know whether this could cause other problems.

Index: src/acl/Checklist.cc
===================================================================
--- src/acl/Checklist.cc (revision 143)
+++ src/acl/Checklist.cc (working copy)
@@ -285,7 +285,13 @@
 
     if (nodeMatched) {
         // matches() should return false in all special cases
- assert(!needsAsync && !matchFinished);
+ //assert(!needsAsync && !matchFinished);
+ if (needsAsync || matchFinished) {
+ debugs(28, DBG_CRITICAL, HERE << this <<
+ " nodeMatched=" << nodeMatched <<
+ " needsAsync=" << needsAsync <<
+ " matchFinished=" << matchFinished);
+ }
         return nmrMatch;
     }
 
Received on Wed Jun 05 2013 - 14:02:14 MDT