Bug 170392
Summary: | Squid is too old in RHEL4 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Martin Stransky <stransky> |
Component: | squid | Assignee: | Martin Bacovsky <mbacovsk> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | bob, bojan, laroche, rambler8 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | RHEL4U3NAK | ||
Fixed In Version: | RHBA-2007-0251 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-05-01 23:27:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 176344 |
Description
Martin Stransky
2005-10-11 10:13:11 UTC
Redhat needs to promptly release an update to completely resolve all issues that have been resolved in squid-2.5.STABLE-11 plus the delay pool problem solved prior to STABLE-12 or I will be recommending that we not renew our 3 RHEL ES subscriptions. The reasons I recommended RHEL in the first place was 1)quality controll and 2) RHN provided time and cost savings value when looking for and installing updates. Unfortunately neither benefit is being realized. The current squid packages are critically broken and have been for 3+ months. Our squid servers were crashing once or twice per day with the current RHEL released squid package. Redhat has tried unsucessfully for 3+ months to back port patches to resolve the issues. I have built, installed and used an RPM from the squid-2.5.STABLE-11 source which resolved all problems encountered with the RHEL squid packages. I installed these RPMs two weeks ago and squid has not crashed since. Redhat has built and distributed a squid RPM package for Fedora 4 that is also built from squid-2.5.STABLE-11 and includes the delay pool patch. If an update will not be released within the next week, I an invite the RHEL managers to explain, in this forum, why they will not allow a new package to be released that fixes these critical service interrupting bugs and why, in that case, we should renew our RHN subscriptions if we are not receiving the updates that we paid for. Page with packages from upstream and hopefully fixed packages for RHEL3/4 is here: http://people.redhat.com/stransky/squid/ Yes, please. Current version of Squid in RHEL4 has problems with Java/NTLM, which makes it really annoying in most corporate environments. Current stable version, as of 30 May 2006, is squid-2.5.STABLE14: http://www.squid-cache.org/Versions/v2/2.5/ The latest 2.5 and 2.6 packages for RHEL4 are available on my squid page... This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Testing packages are here: http://people.redhat.com/stransky/squid/ so anybody can check them. Could you build 2.6.STABLE6 for RHEL4 and upload to the above page? TIA! (In reply to comment #12) > Could you build 2.6.STABLE6 for RHEL4 and upload to the above page? TIA! I'm going to update directly to STABLE7 there, it should be here in a week. Thanks. Much appreciated. The page was updated. Excellent! Thanks. Are the "Differences between current RHEL4 package and the latest upstream package" up-to-date for the squid-2.6.STABLE7-1.RHEL4 package? (In reply to comment #17) > Are the "Differences between current RHEL4 package and the latest upstream > package" up-to-date for the squid-2.6.STABLE7-1.RHEL4 package? No, it's for the latest 2.5 line (i.e. for STABLE14). An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0251.html |