Squid v3.5.7-20150821-r13895 Backtrace: Program received signal SIGSEGV, Segmentation fault. DiskdFile::writeDone (this=<optimized out>, M=0x7fffffffe140) at DiskIO/DiskDaemon/DiskdFile.cc:389 389 ioRequestor->writeCompleted (DISK_OK,M->status, writeRequest); Missing separate debuginfos, use: debuginfo-install glibc-2.17-78.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.12.2-14.el7.x86_64 libattr-2.4.46-12.el7.x86_64 libcap-2.22-8.el7.x86_64 libcom_err-1.42.9-7.el7.x86_64 libgcc-4.8.3-9.el7.x86_64 libselinux-2.2.2-6.el7.x86_64 libstdc++-4.8.3-9.el7.x86_64 nss-softokn-freebl-3.16.2.3-9.el7.x86_64 openssl-libs-1.0.1e-42.el7.9.x86_64 pcre-8.32-14.el7.x86_64 sssd-client-1.12.2-58.el7_1.6.x86_64 xz-libs-5.1.2-9alpha.el7.x86_64 zlib-1.2.7-13.el7.x86_64 (gdb) backtrace #0 DiskdFile::writeDone (this=<optimized out>, M=0x7fffffffe140) at DiskIO/DiskDaemon/DiskdFile.cc:389 #1 0x000000000070a0e4 in DiskdIOStrategy::handle (this=this@entry=0x1748950, M=M@entry=0x7fffffffe140) at DiskIO/DiskDaemon/DiskdIOStrategy.cc:303 #2 0x000000000070a1c5 in DiskdIOStrategy::callback (this=0x1748950) at DiskIO/DiskDaemon/DiskdIOStrategy.cc:556 #3 0x0000000000676a56 in StoreHashIndex::callback (this=<optimized out>) at store_dir.cc:1036 #4 0x0000000000616016 in StoreRootEngine::checkEvents (this=<optimized out>, timeout=<optimized out>) at main.cc:189 #5 0x00000000005a69bf in EventLoop::checkEngine (this=this@entry=0x7fffffffe350, engine=0x7fffffffe2d0, primary=primary@entry=false) at EventLoop.cc:33 #6 0x00000000005a6be2 in EventLoop::runOnce (this=this@entry=0x7fffffffe350) at EventLoop.cc:104 #7 0x00000000005a6e30 in EventLoop::run (this=this@entry=0x7fffffffe350) at EventLoop.cc:82 #8 0x000000000061487a in SquidMain (argc=<optimized out>, argv=<optimized out>) at main.cc:1533 #9 0x000000000050533d in SquidMainSafe (argv=<optimized out>, argc=<optimized out>) at main.cc:1258 #10 main (argc=<optimized out>, argv=<optimized out>) at main.cc:1251
If you want me to continue with more backtraces let me know. Also I can provide any configuration should you need them. -----Original Message----- From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf Of Amos Jeffries Sent: Thursday, August 20, 2015 11:05 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] ETA for Bug 3775 On 21/08/2015 1:14 p.m., Nicolaas Hyatt wrote: > Hey guys, > > I have been paying close attention to the list for a while and am just > beginning to realize the scale of things the squid team has in front > of them. So please understand that I'm _NOT_ begging here. I > understand other priority issues take precedence, and my little issue > is way on down the line. I was wondering if there was some sort of > schedule as to when this may be examined in case I need to provide any more > dumps. > > > > http://bugs.squid-cache.org/show_bug.cgi?id=3775 > Unknown again I'm afraid. That latest feedback was a painfully disappointing result from a very hopeful looking approach. If you have a dump that provides any new backtrace sequence to what we have already they may be useful. So far it all still seems to link back to a DeferredReader pausing a transaction read, then something else playing around with its I/O socket/FD/connection, then defer resumes and boom. But there is potentially some minutes of delay between those actions. PS. you may want to help with the testing of todays snapshot when its ready, it contains some patches to HTTPS and FTP connection handling that may have an impact on this bug (or not, grasping at straws here). Amos _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
