Re: [squid-users] assertion failed: Server.cc:244: "r->body_pipe != NULL"

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Wed, 30 Jan 2013 18:41:07 +1300

On 30/01/2013 5:24 a.m., John Hay wrote:
> Hi Guys,
>
> I have been seeing this pretty often lately, with both 3.2.5 and 3.2.6.
> I'm using FreeBSD 8.x in 64 bit mode and also IPv6.
>
> The message in cache.log is:
>
> 2013/01/29 17:23:39 kid1| assertion failed: Server.cc:244: "r->body_pipe != NULL"
> 2013/01/29 17:23:42 kid1| Starting Squid Cache version 3.2.6 for amd64-portbld-freebsd8.2...
>
> A backtrace with gdb looks like this:
>
> #######################
> proxy# gdb work/squid-3.2.6/src/squid /var/squid/cache/squid.core
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd"...
> Core was generated by `squid'.
> Program terminated with signal 6, Aborted.
> Reading symbols from /usr/lib/librt.so.1...done.
> Loaded symbols for /usr/lib/librt.so.1
> Reading symbols from /usr/lib/libgssapi.so.10...done.
> Loaded symbols for /usr/lib/libgssapi.so.10
> Reading symbols from /usr/lib/libheimntlm.so.10...done.
> Loaded symbols for /usr/lib/libheimntlm.so.10
> Reading symbols from /usr/lib/libkrb5.so.10...done.
> Loaded symbols for /usr/lib/libkrb5.so.10
> Reading symbols from /usr/lib/libhx509.so.10...done.
> Loaded symbols for /usr/lib/libhx509.so.10
> Reading symbols from /usr/lib/libcom_err.so.5...done.
> Loaded symbols for /usr/lib/libcom_err.so.5
> Reading symbols from /lib/libcrypto.so.6...done.
> Loaded symbols for /lib/libcrypto.so.6
> Reading symbols from /usr/lib/libasn1.so.10...done.
> Loaded symbols for /usr/lib/libasn1.so.10
> Reading symbols from /usr/lib/libroken.so.10...done.
> Loaded symbols for /usr/lib/libroken.so.10
> Reading symbols from /lib/libcrypt.so.5...done.
> Loaded symbols for /lib/libcrypt.so.5
> Reading symbols from /usr/lib/libstdc++.so.6...done.
> Loaded symbols for /usr/lib/libstdc++.so.6
> Reading symbols from /lib/libm.so.5...done.
> Loaded symbols for /lib/libm.so.5
> Reading symbols from /lib/libgcc_s.so.1...done.
> Loaded symbols for /lib/libgcc_s.so.1
> Reading symbols from /lib/libthr.so.3...done.
> Loaded symbols for /lib/libthr.so.3
> Reading symbols from /lib/libc.so.7...done.
> Loaded symbols for /lib/libc.so.7
> Reading symbols from /libexec/ld-elf.so.1...done.
> Loaded symbols for /libexec/ld-elf.so.1
> #0 0x0000000801d6dfcc in kill () from /lib/libc.so.7
> [New Thread 8020041c0 (LWP 102238)]
> (gdb) bt
> #0 0x0000000801d6dfcc in kill () from /lib/libc.so.7
> #1 0x0000000801d6cdcb in abort () from /lib/libc.so.7
> #2 0x00000000005398dd in xassert (msg=0x792152 "r->body_pipe != NULL",
> file=0x791dc7 "Server.cc", line=244) at debug.cc:567
> #3 0x0000000000621d1f in ServerStateData::startRequestBodyFlow (
> this=0x8042a1058) at Server.cc:244
> #4 0x000000000056c08b in FtpStateData::readStor (this=0x8042a1058)
> at ftp.cc:3077
> #5 0x000000000056c425 in ftpReadStor (ftpState=0x8042a1058) at ftp.cc:3068
> #6 0x00000000005645f7 in FtpStateData::handleControlReply (this=0x8042a1058)
> at ftp.cc:1861
> #7 0x0000000000564d73 in FtpStateData::ftpReadControlReply (this=0x8042a1058,
> io=@0x80482db48) at ftp.cc:1810
> #8 0x00000000005759aa in CommCbMemFunT<FtpStateData, CommIoCbParams>::doDial (
> this=0x80482db30) at CommCalls.h:198
> #9 0x0000000000575dbc in JobDialer<FtpStateData>::dial (this=0x80482db30,
> call=@0x80482db00) at AsyncJobCalls.h:175
> #10 0x0000000000575fdd in AsyncCallT<CommCbMemFunT<FtpStateData, CommIoCbParams> >::fire (this=0x80482db00) at AsyncCall.h:142
> #11 0x00000000006ab5a4 in AsyncCall::make (this=0x80482db00) at AsyncCall.cc:36
> #12 0x00000000006af98c in AsyncCallQueue::fireNext (this=0x802018300)
> at AsyncCallQueue.cc:54
> #13 0x00000000006afaef in AsyncCallQueue::fire (this=0x802018300)
> ---Type <return> to continue, or q <return> to quit---
> #####################################
>
> It looks a lot like bug 3498 in bugzilla:
> http://bugs.squid-cache.org/show_bug.cgi?id=3498
>
> Any ideas?

Yes it does appear to be that bug.
We don't have a fix for it yet. Any assitance you canprovide towards
finding one would be helpful.

Amos
Received on Wed Jan 30 2013 - 05:41:18 MST

This archive was generated by hypermail 2.2.0 : Thu Jan 31 2013 - 12:00:04 MST