On 09/10/2014 1:11 AM, Mathieu Parent (Debian) wrote:
2014-09-09 19:06 GMT+02:00 Dale Schroeder <d...@briannassaladdressing.com>:
[...]
Here's a picture of the screen when I type "run squid3" under gdb
[...]
If I did my research correctly, here's the backtrace output:
#0 0xb7fde424 in __kernel_vsyscall ()
#1 0xb792f267 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#2 0xb7930923 in __GI_abort () at abort.c:89
#3 0x801312f4 in xassert (msg=0x803d4c28 "size == StrPoolsAttrs[i].obj_size",
file=0x803dbf5c "mem.cc", line=281) at debug.cc:565
#4 0x801cc057 in memFreeString (size=529, buf=0xb7aa8450 <main_arena+48>) at
mem.cc:281
#5 0x8020892a in String::clean (this=0x80650fd4) at String.cc:159
#6 0x80341e4c in Adaptation::AccessRule::~AccessRule (this=0x80650fd0,
__in_chrg=<optimized out>) at AccessRule.cc:15
#7 0x80342cc5 in Adaptation::Config::FreeAccess () at Config.cc:370
#8 0x803430a4 in Adaptation::Config::freeService (this=0x80645e00
<Adaptation::Icap::TheConfig>) at Config.cc:177
#9 0x803430f8 in Adaptation::Config::~Config (this=0x80645e00
<Adaptation::Icap::TheConfig>, __in_chrg=<optimized out>) at Config.cc:396
#10 0x8035d914 in Adaptation::Icap::Config::~Config (this=0x80645e00
<Adaptation::Icap::TheConfig>, __in_chrg=<optimized out>) at Config.cc:54
#11 0xb7932081 in __run_exit_handlers (status=status@entry=0, listp=0xb7aa83c4
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#12 0xb79320dd in __GI_exit (status=0) at exit.c:104
#13 0x801c951f in watch_child (argv=<optimized out>) at main.cc:1679
#14 SquidMain (argc=2, argv=0xbffff7d4) at main.cc:1441
#15 0x800cd089 in SquidMainSafe (argv=0xbffff7d4, argc=2) at main.cc:1242
#16 main (argc=2, argv=0xbffff7d4) at main.cc:1234
Great! This is what I wanted. But I couldn't find any releavant change
in the 3.3 (> 3.3.8) changelog.
Can you reproduce the crash while using c-icap without squidclamav?
Can you provide a network capture (using tcpdump host 127.0.0.1 port
1344)?
I'm using backported squid 3.3.8 with c-icap without a problem...
With the squidclamav service commented out in c-icap.conf and
squidclamav package uninstalled, this is the backtrace output:
Starting program: /usr/sbin/squid3
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Program received signal SIGABRT, Aborted.
0xb7fde424 in __kernel_vsyscall ()
#0 0xb7fde424 in __kernel_vsyscall ()
#1 0xb792f267 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#2 0xb7930923 in __GI_abort () at abort.c:89
#3 0x801312f4 in xassert (msg=0x803d4c28 "size ==
StrPoolsAttrs[i].obj_size", file=0x803dbf5c "mem.cc", line=281) at
debug.cc:565
#4 0x801cc057 in memFreeString (size=529, buf=0xb7aa8450
<main_arena+48>) at mem.cc:281
#5 0x8020892a in String::clean (this=0x80650fd4) at String.cc:159
#6 0x80341e4c in Adaptation::AccessRule::~AccessRule (this=0x80650fd0,
__in_chrg=<optimized out>) at AccessRule.cc:15
#7 0x80342cc5 in Adaptation::Config::FreeAccess () at Config.cc:370
#8 0x803430a4 in Adaptation::Config::freeService (this=0x80645e00
<Adaptation::Icap::TheConfig>) at Config.cc:177
#9 0x803430f8 in Adaptation::Config::~Config (this=0x80645e00
<Adaptation::Icap::TheConfig>, __in_chrg=<optimized out>) at Config.cc:396
#10 0x8035d914 in Adaptation::Icap::Config::~Config (this=0x80645e00
<Adaptation::Icap::TheConfig>, __in_chrg=<optimized out>) at Config.cc:54
#11 0xb7932081 in __run_exit_handlers (status=status@entry=0,
listp=0xb7aa83c4 <__exit_funcs>,
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#12 0xb79320dd in __GI_exit (status=0) at exit.c:104
#13 0x801c951f in watch_child (argv=<optimized out>) at main.cc:1679
#14 SquidMain (argc=1, argv=0xbffff7d4) at main.cc:1441
#15 0x800cd089 in SquidMainSafe (argv=0xbffff7d4, argc=1) at main.cc:1242
#16 main (argc=1, argv=0xbffff7d4) at main.cc:1234
squidclamav directives were active in squid.conf. As mentioned in a
previous email, commenting the squidclamav directives in squid.conf
allows squid3 to start/restart without error.
I have had no luck with tcpdump using the following command:
tcpdump -w /root/capture.log host 127.0.0.1 and port 1344
I tried this both with and without squidclamav being activated. The log
file is always empty. If the command needs to be altered, please let me
know. Thanks for all the help.
Dale
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
