Description of problem: Squid in current RHEL3 doesn't work properly. There were discovered many issues between version used in RHEL3 and current stable and there are many backported patches. We need to start with new clear package with all fixes. The current upstream stable version may work properly (Bug 160704 Comment #34) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Thank you for this, Martin. I look forward to your release of a compiled version for testing under RHEL3 for i386. In specific: squid-2.5.STABLE11.
There is a related bug here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=170392
Page with packages from upstream and hopefully fixed packages for RHEL3/4 is here: http://people.redhat.com/stransky/squid/
Can you compile them, please?
okay, they are there too.
I put squid-2.5.STABLE11-1.RHEL3.i386.rpm into production today. It did not die after 10 minutes as the squid-2.5.STABLE3-6.3E.X branch did. This has been in production for four hours, and no crashes. I'll keep it in production and see how it goes. While no crashes, the cache.log continues to have these messages: 2005/10/21 13:39:41| ctx: enter level 0: 'http://megacharts.finance.lycos.com/ Megacharts/MChartISAPI.dll?...' 2005/10/21 13:39:41| WARNING: unparseable HTTP header field {HTTP/1.1 200 OK} 2005/10/21 13:55:45| httpReadReply: Excess data from "GET http://servedby. advertising.com/site=695501/mnum=262775/bins=1/rich=0"
(In reply to comment #6) > While no crashes, the cache.log continues to have these messages: It looks like your users visit some broken sites. Could you attach more lines from your cache.log?
Created attachment 120308 [details] cache.log for 2.5S11-1 Here is the cache.log file so far. This from squid-2.5.STABLE11-1.RHEL3.
(In reply to comment #9) > Here is the cache.log file so far. This from squid-2.5.STABLE11-1.RHEL3. It's not a bug. It's a feature. Squid checks response from servers and refuses pages if they aren't correct. You don't have to care about it if your users don't complain.
Do you think you will move squid-2.5.STABLE11 into an official RHEL3/4 update release?
I see that the Status has been changed to Closed with a Resolution of NextRelease. What will be the end-result of this? Does it mean that squid-2.5. STABLE11 will be used in the next official Update release of RHEL3/4?
It means that the latest stable release will be used in RHEL5 unless RH managers decide otherwise.
This bug report and the bug reports it supersedes are about problems with squid under RHEL3. How is preematively fixing the problems in RHEL5 going to solve the problems with RHEL3? When will the problem bugs be addressed in RHEL3? As far as I can tell they have not been addressed, yet you have closed them all in bugzilla, with the final resolution that the "latest stable release will be used in RHEL5". That does not address RHEL3 - does it? Please explain.
Fixed packages are available on my testing page. New stable packages will not be released for RHEL3/4. It's the fact and you and I can't do anything with it. This bug can be closed as WONTFIX as NEXTRELEASE, there isn't any difference. And, please, bugzilla is only a bug-tracking system, if you want to complain you have to use another way (Issue-tracker).