Bug 170390 - Squid is too old in RHEL3
Summary: Squid is too old in RHEL3
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: squid
Version: 3.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Martin Stransky
QA Contact:
Depends On:
Blocks: 170445
TreeView+ depends on / blocked
Reported: 2005-10-11 10:08 UTC by Martin Stransky
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2005-12-28 11:08:57 UTC

Attachments (Terms of Use)
cache.log for 2.5S11-1 (5.51 KB, application/octet-stream)
2005-10-24 16:13 UTC, Bob Gorman
no flags Details

Description Martin Stransky 2005-10-11 10:08:34 UTC
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:
Actual results:

Expected results:

Additional info:

Comment 1 Bob Gorman 2005-10-13 15:45:54 UTC
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.

Comment 2 Bob Gorman 2005-10-13 17:25:12 UTC
There is a related bug here:


Comment 3 Martin Stransky 2005-10-18 13:48:19 UTC
Page with packages from upstream and hopefully fixed packages for RHEL3/4 is here:


Comment 4 Bob Gorman 2005-10-18 14:14:22 UTC
Can you compile them, please?

Comment 5 Martin Stransky 2005-10-19 13:58:51 UTC
okay, they are there too.

Comment 6 Bob Gorman 2005-10-21 19:32:35 UTC
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/
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.

Comment 8 Martin Stransky 2005-10-24 14:50:43 UTC
(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?

Comment 9 Bob Gorman 2005-10-24 16:13:07 UTC
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.

Comment 10 Martin Stransky 2005-10-26 08:19:46 UTC
(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.

Comment 11 Bob Gorman 2005-10-28 16:52:25 UTC
Do you think you will move squid-2.5.STABLE11 into an official RHEL3/4 update 

Comment 12 Bob Gorman 2005-12-28 18:04:14 UTC
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?

Comment 13 Martin Stransky 2006-01-03 13:17:39 UTC
It means that the latest stable release will be used in RHEL5 unless RH managers
decide otherwise. 

Comment 14 Bob Gorman 2006-01-03 16:11:17 UTC
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.

Comment 15 Martin Stransky 2006-01-06 13:33:35 UTC
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).

Note You need to log in before you can comment on or make changes to this bug.