[squid-users] assertion failed: client_side.cc:1515: "connIsUsable(http->getConn())

Dan Charlesworth dan at getbusi.com
Thu Feb 26 23:25:30 UTC 2015


Alright I got abrtd on board, finally.

Here’s a a backtrace from this morning (bt and bt full versions included separately):


I’ll go put these in http://bugs.squid-cache.org/show_bug.cgi?id=3930 <http://bugs.squid-cache.org/show_bug.cgi?id=3930> as well.


> On 25 Feb 2015, at 4:12 pm, dan at getbusi.com wrote:
> 
> I’d be happy to provide a recent backtrace to match the config details but abrtd always seems to shit the bed:
> 
> Feb 25 10:19:14 hostname abrt[10776]: Saved core dump of pid 63925 (/usr/sbin/squid) to /var/spool/abrt/ccpp-2015-02-25-10:19:08-63925 (525869056 bytes)
> Feb 25 10:19:14 hostname abrtd: Directory 'ccpp-2015-02-25-10:19:08-63925' creation detected
> Feb 25 10:19:15 hostname squid[63923]: Squid Parent: (squid-1) process 63925 exited due to signal 6 with status 0
> Feb 25 10:19:15 hostname abrtd: Package 'squid' isn't signed with proper key
> Feb 25 10:19:15 hostname abrtd: 'post-create' on '/var/spool/abrt/ccpp-2015-02-25-10:19:08-63925' exited with 1
> Feb 25 10:19:15 hostname abrtd: Deleting problem directory '/var/spool/abrt/ccpp-2015-02-25-10:19:08-63925’
> 
> Not sure what counts as a “proper key” we compile our own squid RPMs and sign them ourselves for our own private repo.
> 
> 
>  
> 
> 
> On Wed, Feb 25, 2015 at 2:03 PM, Amos Jeffries <squid3 at treenet.co.nz <mailto:squid3 at treenet.co.nz>> wrote:
> 
> On 2015-02-25 15:11, dan at getbusi.com wrote: 
> > By the way, I think Eliezer suggested I should file a bug report. 
> > There is in fact one already filed here: 
> > http://bugs.squid-cache.org/show_bug.cgi?id=3930 
> > 
> > 
> > Which brings me to my next question ... 
> > 
> > 
> > 
> > Amos, is it possible to sponsor bug fixes? 
> 
> Of course. Though be aware that if its an outstanding bug it means we 
> are having difficulty resolving it for some reason so we can't really 
> provide any guarantees about what it will take to fix. 
> 
> So far the issue seems to be a lack of information, with a stack trace 
> only coming in recently and the build and config details having come 
> from someone other than the one with stack trace. Ideally we need all 
> the details from a single proxy instance encountering the crash. 
> 
> Amos 
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150227/f05dad5c/attachment-0003.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: connisusable-bt1.txt
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150227/f05dad5c/attachment-0002.txt>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150227/f05dad5c/attachment-0004.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: connisusable-bt-full1.txt
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150227/f05dad5c/attachment-0003.txt>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150227/f05dad5c/attachment-0005.html>


More information about the squid-users mailing list