Re: [squid-users] Squid 3.1.0.13: assertion failed: src/store_client.cc:430: "STORE_DISK_CLIENT == getType()"

> From: Amos Jeffries <squid3_at_treenet.co.nz>
> Date: Mon, 31 Aug 2009 21:02:18 +1200
>
> Silamael wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hello everyone,
>>
>> We're running Squid version 3.1.0.12 with the fix for the DoS
>> vulnerability applied and have from time to time crashes due to this
>> assertion:
>> assertion failed: src/store_client.cc:430: "STORE_DISK_CLIENT == getType()"
>>
>> I searched in Squids Bugzilla and only found the Bug#2155 which is
>> marked as resolved fixed.
>> Can anyone confirm that this problem got fixed in version 3.1.0.13?
>>
>> Thanks in advance!
>>
>> - -- Matthias
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.9 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAkqbfIEACgkQGgHcOSur6dRIwgCgzW/cd3Bd3kyBsYn6CqMYTunZ
>> JBQAn20Zvg4AjKqkRXkETt92doOKXnql
>> =M+mD
>> -----END PGP SIGNATURE-----
>
> 2155 was cosed as it looked identical to 2127 which was resolved in
> 3.1.0.10.
>
> I think it's not actually fixed or not properly since you two are still
> seeing it.
>
Hi all. I am "third" : ) .
I run small proxy(NAT)-server at CentOS 5.3 for 100...120 users and
testing squid 3.1.0.14 with it for full transparent squid.
(/sbin/iptables -t nat -A PREROUTING -p tcp -s 10.9.10.0/23 --dport 80 -j REDIRECT --to-ports 3128)
Now I seen load to cpu and into cache.log:
2009/10/14 22:14:36| assertion failed: store_client.cc:430: "STORE_DISK_CLIENT == getType()"
2009/10/14 22:14:39| Starting Squid Cache version 3.1.0.14 for x86_64-redhat-linux-gnu...
2009/10/14 22:15:11| assertion failed: store_client.cc:430: "STORE_DISK_CLIENT == getType()"
2009/10/14 22:15:14| Starting Squid Cache version 3.1.0.14 for x86_64-redhat-linux-gnu...
2009/10/15 17:25:24| assertion failed: store_client.cc:430: "STORE_DISK_CLIENT == getType()"
2009/10/15 17:25:28| Starting Squid Cache version 3.1.0.14 for x86_64-redhat-linux-gnu...

Will I hope this known bug will close at new version?
Received on Thu Oct 15 2009 - 20:18:10 MDT