[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
** Changed in: squid Status: Unknown = Fix Released ** Changed in: squid Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
This bug was fixed in the package squid3 - 3.1.14-1ubuntu0.2 --- squid3 (3.1.14-1ubuntu0.2) oneiric-proposed; urgency=low * Add 16-skip-read-if-closed.dpatch: Check if connection is still open and bail out if not before attempting to read more data. Fixes crash in squid proxy with message, assertion failed: comm.cc:349: !fd_table[fd].closing(). Patch is a cherrypick of an upstream patch to fix Squid Bug 3131. (LP: #955883) -- Bryce Harrington br...@ubuntu.com Thu, 22 Mar 2012 16:09:42 -0700 ** Changed in: squid3 (Ubuntu Oneiric) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
Hi, 3rd day after implementing the patch no crash of squid3 was daemon seen. So from my point i would say it seems to be stable. Cheers, ubuntu user -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
Hello, i have implement the patch yesterday on the live system. Actualy i doesn't have a valid test scenario, but i will check the logs in the next days. Hope the best. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
** Branch linked: lp:ubuntu/oneiric-proposed/squid3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
Hello Ubuntu, or anyone else affected, Accepted squid3 into oneiric-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: squid3 (Ubuntu Oneiric) Status: Triaged = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
** Description changed: - The Squid Proxy crash sometimes a day with this Message: + [Impact] + fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + + [Development Fix] + fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + + [Stable Fix] + fill me in by pointing out a minimal patch applicable to the stable version of the package. + + [Text Case] + fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + + [Original Report] + The Squid Proxy crash sometimes a day with this Message: assertion failed: comm.cc:349: !fd_table[fd].closing() In the Squid3 Bug Tracker i see there is the same issue fixed: http://bugs.squid-cache.org/show_bug.cgi?id=3131 Can you please fix this in Ubuntu too ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
** Description changed: [Impact] - fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + The Squid Proxy crash sometimes a day with this Message: + assertion failed: comm.cc:349: !fd_table[fd].closing() [Development Fix] - fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + Fixed in http://bugs.squid-cache.org/show_bug.cgi?id=3131, which is part of the 3.1.19 upstream release. The fix checks if the connection is still open and if not it bails out without attempting to read more data. This version was merged from Debian into Precise on Feb 21, 2012 as version 3.1.19-1ubuntu1. [Stable Fix] - fill me in by pointing out a minimal patch applicable to the stable version of the package. + Cherrypick of upstream patch (https://launchpadlibrarian.net/97717160/squid3_fix_955883.patch) applies to the squid3 3.1.14 from oneiric. [Text Case] fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. 1. 2. 3. - Broken Behavior: - Fixed Behavior: + Broken Behavior: + Fixed Behavior: [Regression Potential] - fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. [Original Report] The Squid Proxy crash sometimes a day with this Message: assertion failed: comm.cc:349: !fd_table[fd].closing() In the Squid3 Bug Tracker i see there is the same issue fixed: http://bugs.squid-cache.org/show_bug.cgi?id=3131 Can you please fix this in Ubuntu too ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
I had to rejigger the patch to get it to apply with the proper path. Verified it's the same change as upstream. Packaged as dpatch and verified it builds. Upload sponsored, thanks for your contribution to Ubuntu. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
--- client_side.cc.org 2012-03-21 10:12:58.0 +
+++ client_side.cc 2012-03-21 10:15:43.0 +
@@ -2934,6 +2934,9 @@
{
if (!handleRequestBodyData())
return;
+// fix of Squid Bug 3131
+if (!isOpen() || closing()) // too late to read more body
+ return;
readSomeData();
}
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/955883
Title:
Squid3 Crash assertion failed: comm.cc:349
To manage notifications about this bug go to:
https://bugs.launchpad.net/squid/+bug/955883/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
** Patch added: squid3_fix_955883.patch https://bugs.launchpad.net/ubuntu/oneiric/+source/squid3/+bug/955883/+attachment/2909089/+files/squid3_fix_955883.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
Hi, the version installed on the System is: Squid3 - 3.1.14-1ubuntu0.1 squid3-common - 3.1.14-1ubuntu0.1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
Thanks, sounds like it is worthwhile to consider for SRU to 11.10. Perhaps you could isolate the change from the upstream bug and post it here as a patch? If you are able to do that, subscribe 'ubuntu-sponsors' and hopefully someone with upload rights can get it into oneiric- proposed. ** Also affects: squid3 (Ubuntu Oneiric) Importance: Undecided Status: New ** Changed in: squid3 (Ubuntu Oneiric) Status: New = Triaged ** Changed in: squid3 (Ubuntu Oneiric) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
Hello ms193, can you run 'apport-collect 955883' on the affected system so we can get enough details to confirm this is the same upstream bug, and so we can figure out what version of squid3 you have installed? Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
BTW that particular bug is fixed in 3.1.19 which is available in the latest dev release, precise. As such, I'm marking this bug as Fix Released. It seems serious enough to accept a backport to earlier releases as well. ** Bug watch added: Squid Bugzilla #3131 http://bugs.squid-cache.org/show_bug.cgi?id=3131 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=3131 Importance: Unknown Status: Unknown ** Changed in: squid3 (Ubuntu) Status: New = Fix Released ** Changed in: squid3 (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
