Red Hat Bugzilla – Bug 162025
Last modified: 2007-11-30 17:07:18 EST
Description of problem:
The problem appeared after updating to the latest release squid-2.5.STABLE6-3.4E.9.
After several hours squid crached...
So I had to roll back to use previous squid-2.5.STABLE6-3.4E.5
Version-Release number of selected component (if applicable):
Don't know how but try to use my configuration file squid.conf.
squid.conf and cache.log are included in the field Additional Information
service squid was not running.
and I noticed that md5 checksum of cache was not ok.
diskd was used to store cache.
should be working
cache.log has some comment, see "2005/06/28 18:53:09| Starting Squid Cache
version 2.5.STABLE6 for i386-redhat-linux-gnu..."
Created attachment 116116 [details]
zipped file with cache.log and squid.conf
IMHO dup of 160704
Could you please check STABLE6-3.4E.6 version? src.rpm is here:
Could you please enable debugging and send me the cache.log file, when squid
crashes? Please use this one: debug_options ALL,9
p.s.: The cache.log file will be very big...
downloaded and rebuilt. It is working fine from the half of July OK. ... Ok
I'll do upgrade to latest release thru RHN and set debug level to 9.
The log file location will be reported later.
Could you please attach the /etc/squid/cachemgr.conf file?
I do not have such a file... Maybe you mean squid.conf ?
cachemgr.conf is a new file provided by squid-2.5.STABLE6-3.4E.9, if you still
have the 3.4E.6 package, you won't have it. If you haven't modified it, you can
forget about it.
Could you please create and attach a strack trace when squid crashes? How to is
here - http://people.redhat.com/stransky/squid.html
Due to PIE gdb can't read symbols from the debug package. If your squid crashes
(and it isn't a problem with assertion) and you can't obtain a stack-trace there
are new packages which aren't compiled with PIE:
*** This bug has been marked as a duplicate of 165367 ***