Description of problem: Version-Release number of selected component (if applicable): squid-2.4.STABLE7-0.73.3.legacy How reproducible: Always Steps to Reproduce: 1. Upgrade squid from Fedora legacy 2. 3. Actual results: Squid becomes very unreliable - restarting frequently under load. Expected results: It should be stable as was the previous version under the same load. Additional info: After upgrading squid to the latest Fedora legacy release about a month ago we've had a dramatic drop in reliability. Squid constantly restarts, sometimes has to be manually restarted. The previously installed squid-2.4.STABLE6-6.7.3.i386 was rock solid. Reverting to that fixes the current problem (which proves the upgrade is at fault) but leaves us open to a number of security holes. This is a fairly standard RH 7.3 squid box. We are using pam_auth for authentication and we use two upstream parent proxies for most external sites. The cache log shows nothing of interest. In many cases two restarts will follow each other with no intervening messages. Thanks -- Ian
(The package reported here was created in bug #152809.) I will look into this with the build team and we will see what we can come up with. Reporter- We may need your help reproducing this error. But first, do you have any error messages or entries in the system error log that accompany squid's failures?
Many entries in /var/log/messages like this: Apr 19 13:34:22 proxy squid[28692]: Squid Parent: child process 31687 started Apr 19 13:34:23 proxy squid[28692]: Squid Parent: child process 31687 exited due to signal 6 Apr 19 13:34:26 proxy squid[28692]: Squid Parent: child process 31706 started Apr 19 13:34:30 proxy squid[28692]: Squid Parent: child process 31706 exited due to signal 6 Apr 19 13:34:33 proxy squid[28692]: Squid Parent: child process 31726 started Apr 19 13:34:35 proxy squid[28692]: Squid Parent: child process 31726 exited due to signal 6 Eventually followed by this: Apr 19 13:34:35 proxy squid[28692]: Exiting due to repeated, frequent failures Nothing in squid's cache log other than the normal startup messages.
Ian, Would you give this package a try and get back to us as to whether or not it works for you? Thanks. http://turbosphere.fedoralegacy.org/logs/redhat-7.3-core/86-squid-2.4.STABLE7-0.73.4.legacy/i386/squid-2.4.STABLE7-0.73.4.legacy.i386.rpm Changelog: * Fri Apr 21 2006 David Eisenstein <deisenst> 7:2.4.STABLE7-0.73.4.legacy - Added DNS fix patch for Bug #189323, backported from RHEL4's patch for Bug #160704
Working fine so far (day 1). I'll report again at the end of the week.
Has been working flawlessly for a week now so I'd say the problem is solved (at least for us anyway). Thanks for your help.
You're welcome. It appears that this bug affects more than just RHL 7.3. It would appear to affect RHL 9, FC1, FC2, and FC3, because this issue was fixed in Red Hat Enterprise Linux versions 2.1, 3, and 4. References: * RHEL 3: <http://rhn.redhat.com/errata/RHSA-2006-0045.html>, Bug #165367 * RHEL 4: <http://rhn.redhat.com/errata/RHSA-2006-0052.html>, Bug #160704 * RHEL 2.1: (Can't find anything.) I will keep this bug report open as a reminder for us to include this fix for all our distros when the next security bug for Squid comes up... Thanks for bringing this to our attention, Ian! :)
Created attachment 128697 [details] Backported patch that applied to RHL 7.3's version of squid BTW- the original patch for RHEL 4's bug is attachment 120555 [details] (from Bug #160704 comment 53). We will have to determine if this patch will apply to squid versions later than RHL 7.3's. The backported patch that applied to RHL 7.3's sources is attached.
Fedora Legacy project is closed. This issue will not be fixed by Fedora Legacy.