On 18/02/2015 10:44 a.m., HackXBack wrote: > root@dotspot:~# gdb /usr/sbin/squid /var/spool/squid/cache/squid/core.53359 > GNU gdb (GDB) 7.4.1-debian
> Core was generated by `(squid-1) -YC -f /etc/squid/squid.conf'. > Program terminated with signal 6, Aborted. > #0 0x00007f81777ab165 in raise () from /lib/x86_64-linux-gnu/libc.so.6 > (gdb) backtrace > #0 0x00007f81777ab165 in raise () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x00007f81777ae3e0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 > #2 0x000000000055b10f in xassert (msg=<optimized out>, file=<optimized > out>, line=<optimized out>) at debug.cc:566 > #3 0x00000000006adbc8 in commSetConnTimeout (conn=..., timeout=15, > callback=...) at comm.cc:769 > #4 0x000000000052d9ca in ConnStateData::getSslContextDone > (this=this@entry=0x1895518b8, sslContext=<optimized out>, > sslContext@entry=0x1890abac0, isNew=isNew@entry=false) at > client_side.cc:3997 > #5 0x000000000052e530 in ConnStateData::getSslContextStart > (this=this@entry=0x1895518b8) at client_side.cc:3907 > #6 0x000000000052eb49 in ConnStateData::httpsPeeked (this=0x1895518b8, > serverConnection=...) at client_side.cc:4069 > #7 0x0000000000596188 in UnaryMemFunT<ConnStateData, > RefCount<Comm::Connection>, RefCount<Comm::Connection> >::doDial > (this=0x188dcda00) at base/AsyncJobCalls.h:113 The client is disconnecting or some other error is happening to close the connection before the SSL context is setup. The SSL-bump code in 3.4 and older does not handle that at all well. If you are able can you please try 3.5 and see if the problem is resolved. There was some timeout handling added there, but I'm not sure if it covers this particular case. Amos _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
