AW: [squid-users] assertion failed: cbdata.cc:464: "c->locks > 0

Hi Amos,

i added the needed infos to: http://bugs.squid-cache.org/show_bug.cgi?id=3696

thanks.

cheers,
Chris

-----Ursprüngliche Nachricht-----
Von: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Gesendet: Mittwoch, 30. Juli 2014 13:06
An: squid-users_at_squid-cache.org
Betreff: Re: [squid-users] assertion failed: cbdata.cc:464: "c->locks > 0

On 30/07/2014 10:44 p.m., Labusch, Christian (regio iT) wrote:
> Hello all,
>
> i have a little Problem with the "new" Directive "client_delay_pools". Our old Config with the normal delay_classes works fine. But we need additional a Upload-Limit.
>
> Testmachine with very simple standard config:
>
> - OS: Linux debian 3.2.0-4-486 #1 Debian 3.2.60-1+deb7u1 i686
> GNU/Linux
> - Squid Cache: Version 3.4.6. (configure options:
> '--enable-delay-pools')
>
> Squid.conf (Limitation 1 Mbit/s):
>
> client_delay_pools 1
> client_delay_initial_bucket_level 100
> client_delay_access 1 allow localnet
> client_delay_access 1 deny all
> client_delay_parameters 1 128000 128000
>
> To start the squid-Daemon brings the following error:
>
> Cache.log:
>
> 2014/07/30 10:33:02 kid1| assertion failed: cbdata.cc:464: "c->locks > 0"

<snip>

> Do you have any ideas?

http://bugs.squid-cache.org/show_bug.cgi?id=3696

We require a stack trace to identify the cause of this one. If you can obtain one from 3.4.6 (or better a current 3.HEAD tarball) that would be very helpful. Please ensure that it actually has the function names rather than hex numbers and add to the bug report along with the "squid -v" output.

Amos
Received on Thu Jul 31 2014 - 12:42:50 MDT