Hi Amos, > On 30/07/2014 10:44 p.m., Labusch, Christian (regio iT) wrote: >> - 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" > http://bugs.squid-cache.org/show_bug.cgi?id=3696 Just for the record, I got the same error (same assert) when I tried to enable client_delay_pools. But using CentOS 6.4 ou a 64-bit Xeon Dell server and squid 3.4.6 installed from Eliezer RPMs. Very different machine and OS, so it's not something specific to Christian setup. I took a look at the bug and comments give the impression that people thought it was reladted to the older delay_pools (not client_delay) when they reported "works fine for me". The bug state could be moved to something other than UNCONFIRMED. And I have to remember how to get debug symbols for the RPM and generate a stack trace. ;-) []s, Fernando Lozano
