squid3[27598]: segfault at 00000000 eip 0810f3e9 esp bfaa73f4 error 4 squid3[32012]: segfault at 00000000 eip 0810f3e9 esp bfeb7804 error 4 squid3[32042]: segfault at 00000000 eip 0810f3e9 esp bfcdf634 error 4 squid3[32569]: segfault at 00000000 eip 0810f3e9 esp bfea9ff4 error 4 squid3[32599]: segfault at 00000000 eip 0810f3e9 esp bfe47f94 error 4 squid3[32648]: segfault at 00000000 eip 0810f3e9 esp bff898d4 error 4 squid3[32678]: segfault at 00000000 eip 0810f3e9 esp bfa8e3e4 error 4 squid3[335]: segfault at 00000000 eip 0810f3e9 esp bf8a79f4 error 4 squid3[365]: segfault at 00000000 eip 0810f3e9 esp bf9c2b14 error 4 squid3[1741]: segfault at 00000000 eip 0810f3e9 esp bff9d8f4 error 4 squid3[1833]: segfault at 00000000 eip 0810f3e9 esp bf824974 error 4 squid3[2174]: segfault at 00000000 eip 0810f3e9 esp bf9acb04 error 4 squid3[24311]: segfault at 00000008 eip 08118881 esp bf8d09d0 error 4 squid3[7007]: segfault at 00000000 eip 0810f3e9 esp bfc92a44 error 4 its solved by compiling pristine squid source from squid-cache.org
tags 486211 +moreinfo thanks Hi Armin, I'm sure you notice that your bug report is rather uninformative. I understand that squid3 segfaults under unknown condition (you attached no log file which could help identify the cause) and that a custom built binary doesn't show the same behaviour (but you didn't specify which compile option or runtime configuration was used in your build). Can you please test the latest version of squid3 in debian (3.0.STABLE6-1) with the same configuration and provide details on how to reproduce your bug, if it's still there? Regards, L
The issue is still here , its 3.0.STABLE6-2 , issue fixed by STABLE6 Jun 22, 2008 from squid-cache.org result of dmesg : root@CacheServer:~# dmesg | grep -i squid squid3[1923]: segfault at 00000000 eip 0810fb39 esp bfb86cd4 error 4 squid3[6611]: segfault at 00000000 eip 0810fb39 esp bfee1034 error 4 squid3[7501]: segfault at 00000000 eip 0810fb39 esp bff688b4 error 4 squid3[24151]: segfault at 00000000 eip 0810fb39 esp bfae6c34 error 4 squid3[30831]: segfault at 00000000 eip 0810fb39 esp bfee4034 error 4 squid3[30978]: segfault at 00000000 eip 0810fb39 esp bfcc7e14 error 4 squid3[31024]: segfault at 00000000 eip 0810fb39 esp bffa78f4 error 4 squid3[31332]: segfault at 00000000 eip 0810fb39 esp bfd746c4 error 4 squid3[31381]: segfault at 00000000 eip 0810fb39 esp bf83d994 error 4 squid3[3999]: segfault at 00000000 eip 0810fb39 esp bfab0c04 error 4 squid3[4315]: segfault at 00000000 eip 0810fb39 esp bfe527a4 error 4 squid3[4008]: segfault at 00000000 eip 0810fb39 esp bf8dc224 error 4 squid3[4130]: segfault at 00000000 eip 0810fb39 esp bfcc4e14 error 4 squid3[13179]: segfault at 00000000 eip 0810fb39 esp bfc7a5c4 error 4 squid3[13421]: segfault at 00000000 eip 0810fb39 esp bf904254 error 4 squid3[13869]: segfault at 00000000 eip 0810fb39 esp bfaa53f4 error 4 squid3[6542]: segfault at 00000000 eip 0810fb39 esp bfaddc34 error 4 squid3[6686]: segfault at 00000000 eip 0810fb39 esp bfa533a4 error 4 squid3[6830]: segfault at 00000000 eip 0810fb39 esp bffc2914 error 4 squid3[6898]: segfault at 00000000 eip 0810fb39 esp bfab3404 error 4 squid3[21608]: segfault at 00000000 eip 0810fb39 esp bfd926e4 error 4 squid3[23656]: segfault at 00000000 eip 0810fb39 esp bf8efa44 error 4 squid3[24836]: segfault at 00000000 eip 0810fb39 esp bfa25374 error 4 squid3[5266]: segfault at 00000000 eip 0810fb39 esp bfcb4604 error 4 squid3[5598]: segfault at 00000000 eip 0810fb39 esp bfe41794 error 4
The issue is still here , its 3.0.STABLE6-2 , issue fixed by STABLE6 Jun 22, 2008 from squid-cache.org result of dmesg : root@CacheServer:~# dmesg | grep -i squid squid3[1923]: segfault at 00000000 eip 0810fb39 esp bfb86cd4 error 4 squid3[6611]: segfault at 00000000 eip 0810fb39 esp bfee1034 error 4 squid3[7501]: segfault at 00000000 eip 0810fb39 esp bff688b4 error 4 squid3[24151]: segfault at 00000000 eip 0810fb39 esp bfae6c34 error 4 squid3[30831]: segfault at 00000000 eip 0810fb39 esp bfee4034 error 4 squid3[30978]: segfault at 00000000 eip 0810fb39 esp bfcc7e14 error 4 squid3[31024]: segfault at 00000000 eip 0810fb39 esp bffa78f4 error 4 squid3[31332]: segfault at 00000000 eip 0810fb39 esp bfd746c4 error 4 squid3[31381]: segfault at 00000000 eip 0810fb39 esp bf83d994 error 4 squid3[3999]: segfault at 00000000 eip 0810fb39 esp bfab0c04 error 4 squid3[4315]: segfault at 00000000 eip 0810fb39 esp bfe527a4 error 4 squid3[4008]: segfault at 00000000 eip 0810fb39 esp bf8dc224 error 4 squid3[4130]: segfault at 00000000 eip 0810fb39 esp bfcc4e14 error 4 squid3[13179]: segfault at 00000000 eip 0810fb39 esp bfc7a5c4 error 4 squid3[13421]: segfault at 00000000 eip 0810fb39 esp bf904254 error 4 squid3[13869]: segfault at 00000000 eip 0810fb39 esp bfaa53f4 error 4 squid3[6542]: segfault at 00000000 eip 0810fb39 esp bfaddc34 error 4 squid3[6686]: segfault at 00000000 eip 0810fb39 esp bfa533a4 error 4 squid3[6830]: segfault at 00000000 eip 0810fb39 esp bffc2914 error 4 squid3[6898]: segfault at 00000000 eip 0810fb39 esp bfab3404 error 4 squid3[21608]: segfault at 00000000 eip 0810fb39 esp bfd926e4 error 4 squid3[23656]: segfault at 00000000 eip 0810fb39 esp bf8efa44 error 4 squid3[24836]: segfault at 00000000 eip 0810fb39 esp bfa25374 error 4 squid3[5266]: segfault at 00000000 eip 0810fb39 esp bfcb4604 error 4 squid3[5598]: segfault at 00000000 eip 0810fb39 esp bfe41794 error 4
Hi Armin, thanks for your follow-up on this bug. Still I have not enough information to reproduce it. Can you please provide: - configuration file, - cache.log (in /var/log/squid) lines preceding segfault, - core file if present, - configuration options you used while building the upstream sources. - a brief description of your environmente. Regards, L
Hi,
I have a similar problem. It looks like this:
...
2008/10/25 21:00:18.404| eventRun:
2008/10/25 21:00:18.404| cbdataReferenceValid: 0x9f86328
2008/10/25 21:00:18.404| Engine 0xbf9a4764 is idle.
2008/10/25 21:00:18.404| cbdataReferenceValid: 0x9f86328
2008/10/25 21:00:18.404| cbdataUnlock: 0x9f86328=0
2008/10/25 21:00:18.404| EventDispatcher::dispatch: Running 'storeRebuild'
2008/10/25 21:00:18.404| store.cc(359) new StoreEntry 0xbf9a4548
2008/10/25 21:00:18.404| commonUfsDirRebuildFromDirectory: DIR #0
2008/10/25 21:00:18.404| commonUfsDirGetNextFile: flag=0, 0: /00/00
2008/10/25 21:00:18.415| commonUfsDirGetNextFile: Directory /home/squid/cache/00/00
2008/10/25 21:00:18.415| commonUfsDirGetNextFile: Opening /home/squid/cache/00/00/0000007A
2008/10/25 21:00:18.423| file_open: FD 15
2008/10/25 21:00:18.423| fd_open FD 15 /home/squid/cache/00/00/0000007A
2008/10/25 21:00:18.423| file_in: fd=15 0000007A
2008/10/25 21:00:18.432| file_close: FD 15, really closing
2008/10/25 21:00:18.432| fd_close FD 15 /home/squid/cache/00/00/0000007A
2008/10/25 21:00:18.432| commSetSelect(FD 15,type=1,handler=(nil),client_data=(nil),timeout=0)
2008/10/25 21:00:18.432| commSetSelect(FD 15,type=2,handler=(nil),client_data=(nil),timeout=0)
2008/10/25 21:00:18.432| commonUfsDirRebuildFromDirectory: successful swap meta unpacking
2008/10/25 21:00:18.432| storeGet: looking up 8650FC0D2FD4C71A79C4CEB1CF9E890D
FATAL: Received Segment Violation...dying.
2008/10/25 21:00:18.432| Not currently OK to rewrite swap log.
2008/10/25 21:00:18.432| storeDirWriteCleanLogs: Operation aborted.
CPU Usage: 0.064 seconds = 0.036 user + 0.028 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 0
Memory usage for squid via mallinfo():
total space in arena: 2980 KB
Ordinary blocks: 2880 KB 1 blks
Small blocks: 0 KB 3 blks
Holding blocks: 1500 KB 7 blks
Free Small blocks: 0 KB
Free Ordinary blocks: 99 KB
Total in use: 4380 KB 147%
Total free: 99 KB 3%
Aborted
I couldn't recompile because of too many build-dependencies, and have
this package installed:
ii squid3 3.0.PRE5-5 A full featured Web Proxy cache (HTTP proxy)
In my case, deleting everything under /home/squid/cache solved the
problem, as far as I can see now.
Kind regards,
--Toni++
Hello, I just see this on a Lenny machine: Mar 11 09:30:49 debian squid[28429]: Squid Parent: child process 28667 exited due to signal 11 Mar 11 09:30:49 debian kernel: [2286744.975364] squid3[28667]: segfault at 0 ip b7c70d03 sp bfffcb18 error 4 in libc-2.7.so[b7bfb000+155000] Mar 11 09:30:52 debian squid[28429]: Squid Parent: child process 29732 started ... Mar 11 09:36:59 debian kernel: [2287157.293463] squid3[29732]: segfault at 0 ip b7cdbd03 sp bfffed58 error 4 in libc-2.7.so[b7c66000+155000] Mar 11 09:36:59 debian squid[28429]: Squid Parent: child process 29732 exited due to signal 11 Mar 11 09:37:02 debian squid[28429]: Squid Parent: child process 30086 started Mar 11 09:37:09 debian kernel: [2287168.626192] squid3[30086]: segfault at 0 ip b7ca4d03 sp bfffd0c8 error 4 in libc-2.7.so[b7c2f000+155000] Mar 11 09:37:09 debian squid[28429]: Squid Parent: child process 30086 exited due to signal 11 Mar 11 09:37:12 debian squid[28429]: Squid Parent: child process 30089 started Mar 11 09:37:20 debian squid[28429]: Squid Parent: child process 30089 exited due to signal 11 Mar 11 09:37:20 debian kernel: [2287179.883161] squid3[30089]: segfault at 0 ip b7c96d03 sp bfffd458 error 4 in libc-2.7.so[b7c21000+155000] Mar 11 09:37:23 debian squid[28429]: Squid Parent: child process 30126 started Mar 11 09:37:30 debian kernel: [2287191.250330] squid3[30126]: segfault at 0 ip b7ca4d03 sp bfffd6e8 error 4 in libc-2.7.so[b7c2f000+155000] Mar 11 09:37:30 debian squid[28429]: Squid Parent: child process 30126 exited due to signal 11 Mar 11 09:37:33 debian squid[28429]: Squid Parent: child process 30142 started Mar 11 09:37:40 debian kernel: [2287202.839088] squid3[30142]: segfault at 0 ip b7d18d03 sp bfffd148 error 4 in libc-2.7.so[b7ca3000+155000] Mar 11 09:37:40 debian squid[28429]: Squid Parent: child process 30142 exited due to signal 11 Mar 11 09:37:43 debian squid[28429]: Squid Parent: child process 30147 started Mar 11 09:37:54 debian squid[28429]: Squid Parent: child process 30147 exited due to signal 11 Mar 11 09:37:54 debian kernel: [2287217.485505] squid3[30147]: segfault at 0 ip b7d39d03 sp bfffe188 error 4 in libc-2.7.so[b7cc4000+155000] Mar 11 09:37:57 debian squid[28429]: Squid Parent: child process 30151 started Mar 11 09:38:04 debian kernel: [2287228.490721] squid3[30151]: segfault at 0 ip b7ce9d03 sp bfffd6e8 error 4 in libc-2.7.so[b7c74000+155000] Mar 11 09:38:04 debian squid[28429]: Squid Parent: child process 30151 exited due to signal 11 Mar 11 09:38:07 debian squid[28429]: Squid Parent: child process 30196 started Mar 11 09:38:14 debian squid[28429]: Squid Parent: child process 30196 exited due to signal 11 Mar 11 09:38:14 debian kernel: [2287240.096270] squid3[30196]: segfault at 0 ip b7ce3d03 sp bfffdee8 error 4 in libc-2.7.so[b7c6e000+155000] Mar 11 09:38:17 debian squid[28429]: Squid Parent: child process 30199 started Mar 11 09:38:24 debian squid[28429]: Squid Parent: child process 30199 exited due to signal 11 Mar 11 09:38:24 debian kernel: [2287249.988608] squid3[30199]: segfault at 0 ip b7d15d03 sp bfffe2d8 error 4 in libc-2.7.so[b7ca0000+155000] Mar 11 09:38:27 debian squid[28429]: Squid Parent: child process 30203 started Mar 11 09:38:29 debian kernel: [2287255.138989] squid3[30203]: segfault at 0 ip b7ca8d03 sp bfffc468 error 4 in libc-2.7.so[b7c33000+155000] Mar 11 09:38:29 debian squid[28429]: Squid Parent: child process 30203 exited due to signal 11 Mar 11 09:38:32 debian squid[28429]: Squid Parent: child process 30206 started Mar 11 09:38:35 debian kernel: [2287261.897126] squid3[30206]: segfault at 0 ip b7c5bd03 sp bfffdc98 error 4 in libc-2.7.so[b7be6000+155000] Mar 11 09:38:35 debian squid[28429]: Squid Parent: child process 30206 exited due to signal 11 Mar 11 09:38:35 debian squid[28429]: Exiting due to repeated, frequent failures The machine is equipped with ECC ram, so I don't expect this to be a problem. Also, other applications run on this machine w/o noticable problems. Kind regards, --Toni++
Toni, unfortunately your bug report is rather uninformative. Can you please provide - configuration file, - cache.log (in /var/log/squid) lines preceding segfault, - core file if present, - strace of running process? Thanks, L
Hi Luigi, agreed. I have attached a configuration file. I'm sorry, but no, I can't provide you with this log file because I don't have it any longer. I ran Lenny's version of squid3 for only very few days until I *had* to replace it. Nope again. I have no core file. :( I may be able to provide such a trace for the running version of Squid3 (= my backport), which is different from what is in Lenny. Do you want a section where it crashes? That would be difficult to come by atm...
Hi Luigi, Apr 13 03:15:29 nw2 squid[11017]: assertion failed: client_side.cc:2479: "conn->in.abortedSize == (size_t)conn->bodySizeLeft()" HTH, --Toni++
Hi Toni, this is probably a completely different bug. Can you please provide information about the environment e configuration in use while this bug occurred? As usual, at least package version, configuration and log are required. Regards, L Il giorno 13/apr/2010, alle ore 10.37, Toni Mueller ha scritto:
Dear Maintainer, any caching configuration (or even my not much more modified one) causes the child process to sigfault. It's a major problem since while restarting it always spin up my hard disks. If the server is started with totally default configuration so no caching, no localnet, i seem to not have this issue. Unfortunally i think a lot of people use Debian because of its stability for server not as client, so using a proxy that works only for localhost seems really pointless to me. Since this is my first report with this system and i don't know if my syslog is attached i report the significan lines showing this problem. /var/log/syslog ================================ Oct 15 02:43:53 hostname squid[13706]: Squid Parent: child process 13738 exited due to signal 11 with status 0 Oct 15 02:43:53 hostname kernel: [11235.873645] squid3[13738]: segfault at 0 ip 00007f69b52298f3 sp 00007fff9c69a718 error 4 in squid3[7f69b507e000+301000] Oct 15 02:43:56 hostname squid[13706]: Squid Parent: child process 13805 started Oct 15 02:48:53 hostname squid[13706]: Squid Parent: child process 13805 exited due to signal 11 with status 0 Oct 15 02:48:53 hostname kernel: [11535.301936] squid3[13805]: segfault at 0 ip 00007f871eb168f3 sp 00007fff8a071988 error 4 in squid3[7f871e96b000+301000] Oct 15 02:48:56 hostname squid[13706]: Squid Parent: child process 13816 started ================================
I've just upgraded two servers from squeeze to wheezy, and i've hit this bug in one of that. I repeatedlt receive: Mar 25 12:33:02 kaa kernel: [943353.343797] squid3[16919]: segfault at 58 ip 00007fd34cea2396 sp 00007fff192e1b60 error 4 in squid3[7fd34ccaf000+301000] Mar 25 12:33:02 kaa squid[40048]: Squid Parent: child process 16919 exited due to signal 11 with status 0 roughly 5-10 time at distance of some minutes, then nothing for hour... and happens roughly 10-50 times at day. Both server (kaa and lupus) are 64bit debian wheezy. lupus seems does not have that trouble; configuration are roughly the same. The only difference between kaa and lupus, is that kaa is a medium-heavy-loaded server, while lupus does little job, so seems ''load-related''. Say me if more info are needed... thanks.