I started my computer with the modified squid configuration which already crashed the daemon here:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1218345
...why does increasing the timeouts crash the whole server? I don't want long connections to time out after 1-2 minutes, and a timeout of 48 hours is totally okay for a server which is only accessible on my LAN - at least that's what I thought.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: squid3 3.3.8-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Thu Aug 29 13:37:53 2013
ExecutablePath: /usr/lib/squid3/pinger
InstallationDate: Installed on 2011-09-04 (725 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
MarkForUpload: True
ProcCmdline: (pinger)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x7f226477ab7d <malloc_consolidate+125>: cmp 0x18(%rax),%r12
PC (0x7f226477ab7d) ok
source "0x18(%rax)" (0x23a240970098) not located in a known VMA region (needed readable region)!
destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: squid3
StacktraceTop:
malloc_consolidate (av=av@entry=0x7f2264abb740 <main_arena>) at malloc.c:4081
_int_free (av=0x7f2264abb740 <main_arena>, p=0x7f226717fb10, have_lock=0) at malloc.c:3973
std::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >::~basic_ostringstream() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
?? ()
?? ()
Title: pinger crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: Upgraded to saucy on 2013-02-11 (199 days ago)
UserGroups: winbindd_priv
mtime.conffile..etc.squid3.squid.conf: 2013-08-29T13:29:34.960762
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1214379, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.