Re: [squid-users] squid is dying
On mån, 2008-11-03 at 11:26 +0545, Anuj Shrestha wrote: i m using squid in freebsd 7.0 below are the compile options, proxy01# squid -v Squid Cache: Version 3.0.STABLE9 below are the cache.log errors FATAL: Received Segment Violation...dying. You may want to try upgrading to 3.0.STABLE10. Or at a minimum file a bug report including a stack backtrace. http://wiki.squid-cache.org/SquidFaq/TroubleShooting#head-7067fc0034ce967e67911becaabb8c95a34d576d proxy01# tail -f /var/log/squid/cache.log 2008/11/03 17:14:17| clientParseRequestMethod: Unsupported method in request 'REGISTER sip:68.142.233.183:80;transport=tcp SIP/2.0__From: sip:[EMAIL PROTECTED]:80;ta' Hmm.. SIP requests sent to Squid? Why is that? SIP is not HTTP even if it borrows much of the syntax from HTTP. Regards Henrik signature.asc Description: This is a digitally signed message part
[squid-users] squid is dying
i m using squid in freebsd 7.0 below are the compile options, proxy01# squid -v Squid Cache: Version 3.0.STABLE9 configure options: '--bindir=/usr/local/sbin' '--sysconfdir=/usr/local/etc/squid' '--datadir=/usr/local/etc/squid' '--libexecdir=/usr/local/libexec/squid' '--localstatedir=/usr/local/squid' '--enable-removal-policies=lru heap' '--enable-storeio=aufs,ufs,diskd,null' '--enable-delay-pools' '--enable-snmp' '--enable-cache-digests' '--enable-underscores' '--enable-useragent-log' '--enable-time-hack' '--with-large-files' '--enable-large-cache-files' '--prefix=/usr/local' '--enable-follow-x-forwarded-for' '--enable-forward-log' '--enable-kill-parent-hack' '--with-maxfd=32000' '--enable-ipfw-transparent' below are the cache.log errors FATAL: Received Segment Violation...dying. proxy01# tail -f /var/log/squid/cache.log 2008/11/03 17:14:17| clientParseRequestMethod: Unsupported method in request 'REGISTER sip:68.142.233.183:80;transport=tcp SIP/2.0__From: sip:[EMAIL PROTECTED]:80;ta' 2008/11/03 17:14:17| clientProcessRequest: Invalid Request 2008/11/03 17:14:29| clientParseRequestMethod: Unsupported method: This is not a bug. see squid.conf extension_methods 2008/11/03 17:14:29| clientParseRequestMethod: Unsupported method in request 'NICK pztuookb_USER i' 2008/11/03 17:14:29| clientProcessRequest: Invalid Request 2008/11/03 17:14:45| comm_old_accept: FD 9: (53) Software caused connection abort 2008/11/03 17:14:45| httpAccept: FD 9: accept failure: (53) Software caused connection abort 2008/11/03 17:14:59| clientParseRequestMethod: Unsupported method: This is not a bug. see squid.conf extension_methods 2008/11/03 17:14:59| clientParseRequestMethod: Unsupported method in request 'NICK rormjcph_USER u' 2008/11/03 17:14:59| clientProcessRequest: Invalid Request 2008/11/03 17:15:10| clientParseRequestMethod: Unsupported method: This is not a bug. see squid.conf extension_methods 2008/11/03 17:15:10| clientParseRequestMethod: Unsupported method in request 'REGISTER sip:68.142.233.164:80;transport=tcp SIP/2.0__From: sip:[EMAIL PROTECTED]:80;tag=70' 2008/11/03 17:15:10| clientProcessRequest: Invalid Request did i made any mistakes while compiling squid or there are some extra options i have to add on squid.conf thanks anuj shrestha
Re: [squid-users] Squid ramdomly dying
Michael Loftis wrote: --On May 4, 2006 1:29:00 PM -0300 [EMAIL PROTECTED] wrote: Hello! Squid is dying with no apparent reason from time to time... I only see in cache.log: FATAL: Received Segment Violation...dying. Segfaults are usually one of about three things (most common to least common) -- bad programming, bad memory, or bad CPU fan. Are you using async I/O? In the past I've had lots of issues with that. Outside of that what follows are more or less general recommendations... No, I am using diskd. I don't run 2.5.13 on FreeBSD 5.4 nor AMD64 so I can't vouch for it's stability there however on Linux and FreeBSD 4.x it's been very stable. If you can take the machine down for a few hours download memtest86 from Memtest86.com burn the ISO to a disc, and boot off of it. Let it run a pass or two. If it comes up with any errors, there's your problem, bad memory most likely. If it locks up, reboots, or shuts down, you've got a cooling issue. I can't let the machine down for a minute :) Anyway, I don't think we have a hardware issue. It's a Dell PowerEdge 830 with ECC memory. First we had 1GB of RAM, but as Squid grew, we bought 2GB and exchanged all memory chips. The problem exists either with old or new memory chips. The fan is fine, in fact, I am 99.9% sure that we don't have a hardware problem. Assuming that's all clear then my next step would be to turn on core dumps and after it dies use gdb to gether the backtrace information. If you haven't built with debugging symbols and automatic backtraces by adding --enable-stacktraces to your existing ./configure...while you're at that can you post what your existing ./configure is. Note that I know atleast int eh past AIO/aufs (i think is what it's called now) has been the cause of much grief for me so I use diskd exclusively. I'm not a huge fan of big monolithic programs anyway. I have enabled debugging symbols and will open a bug report (when I get the traces) as recommended. Thanks. ... and them it restarts automatically. I'm running squid-2.5.STABLE13 in FreeBSD 5.4-RELEASE (amd64). CPU usage is low. It's difficult to see Squid getting more than 30% of CPU usage. I have 2GB of RAM, Squid eats 1.2GB and the system always has at least 200MB free, except swap. Cache dir is about 100GB. Anyone has a similar issue? Is there any way I can debug this problem? Thank you in advance. -- Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds. -- Samuel Butler
[squid-users] Squid ramdomly dying
Hello! Squid is dying with no apparent reason from time to time... I only see in cache.log: FATAL: Received Segment Violation...dying. ... and them it restarts automatically. I'm running squid-2.5.STABLE13 in FreeBSD 5.4-RELEASE (amd64). CPU usage is low. It's difficult to see Squid getting more than 30% of CPU usage. I have 2GB of RAM, Squid eats 1.2GB and the system always has at least 200MB free, except swap. Cache dir is about 100GB. Anyone has a similar issue? Is there any way I can debug this problem? Thank you in advance.
Re: [squid-users] Squid ramdomly dying
--On May 4, 2006 1:29:00 PM -0300 [EMAIL PROTECTED] wrote: Hello! Squid is dying with no apparent reason from time to time... I only see in cache.log: FATAL: Received Segment Violation...dying. Segfaults are usually one of about three things (most common to least common) -- bad programming, bad memory, or bad CPU fan. Are you using async I/O? In the past I've had lots of issues with that. Outside of that what follows are more or less general recommendations... I don't run 2.5.13 on FreeBSD 5.4 nor AMD64 so I can't vouch for it's stability there however on Linux and FreeBSD 4.x it's been very stable. If you can take the machine down for a few hours download memtest86 from Memtest86.com burn the ISO to a disc, and boot off of it. Let it run a pass or two. If it comes up with any errors, there's your problem, bad memory most likely. If it locks up, reboots, or shuts down, you've got a cooling issue. Assuming that's all clear then my next step would be to turn on core dumps and after it dies use gdb to gether the backtrace information. If you haven't built with debugging symbols and automatic backtraces by adding --enable-stacktraces to your existing ./configure...while you're at that can you post what your existing ./configure is. Note that I know atleast int eh past AIO/aufs (i think is what it's called now) has been the cause of much grief for me so I use diskd exclusively. I'm not a huge fan of big monolithic programs anyway. ... and them it restarts automatically. I'm running squid-2.5.STABLE13 in FreeBSD 5.4-RELEASE (amd64). CPU usage is low. It's difficult to see Squid getting more than 30% of CPU usage. I have 2GB of RAM, Squid eats 1.2GB and the system always has at least 200MB free, except swap. Cache dir is about 100GB. Anyone has a similar issue? Is there any way I can debug this problem? Thank you in advance. -- Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds. -- Samuel Butler
Re: [squid-users] Squid ramdomly dying
tor 2006-05-04 klockan 13:29 -0300 skrev [EMAIL PROTECTED]: Hello! Squid is dying with no apparent reason from time to time... I only see in cache.log: FATAL: Received Segment Violation...dying. Internal error. Please file a bug report. Don't forget to include a stack trace of the segmentation violation. Squid FAQ 11.19 Sending in Squid bug reports url:http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19 Regards Henrik signature.asc Description: Detta är en digitalt signerad meddelandedel
[squid-users] Squid process dying - possibly caused by backup?
Hi, every day the squid process reports the following: [EMAIL PROTECTED] /root]# service squid status squid dead but subsys locked squid: ERROR: No running copy I simply start it back up: [EMAIL PROTECTED] /root]# service squid start Starting squid:[ OK ] Output of cache.log after starting (I think everything here looks good): 2004/09/16 10:41:03| Starting Squid Cache version 2.4.STABLE6 for i386-redhat-linux-gnu... 2004/09/16 10:41:03| Process ID 5357 2004/09/16 10:41:03| With 1024 file descriptors available 2004/09/16 10:41:03| DNS Socket created on FD 4 2004/09/16 10:41:03| Adding nameserver 127.0.0.1 from /etc/resolv.conf 2004/09/16 10:41:03| Unlinkd pipe opened on FD 9 2004/09/16 10:41:03| Swap maxSize 102400 KB, estimated 7876 objects 2004/09/16 10:41:03| Target number of buckets: 393 2004/09/16 10:41:03| Using 8192 Store buckets 2004/09/16 10:41:03| Max Mem size: 8192 KB 2004/09/16 10:41:03| Max Swap size: 102400 KB 2004/09/16 10:41:03| Rebuilding storage in /var/spool/squid (CLEAN) 2004/09/16 10:41:03| Using Least Load store dir selection 2004/09/16 10:41:03| Set Current Directory to /var/spool/squid 2004/09/16 10:41:03| Loaded Icons. 2004/09/16 10:41:03| Accepting HTTP connections at 0.0.0.0, port 8080, FD 11. 2004/09/16 10:41:03| Accepting ICP messages at 0.0.0.0, port 3130, FD 12. 2004/09/16 10:41:03| WCCP Disabled. 2004/09/16 10:41:03| Ready to serve requests. 2004/09/16 10:41:03| Done reading /var/spool/squid swaplog (1840 entries) 2004/09/16 10:41:03| Finished rebuilding storage from disk. 2004/09/16 10:41:03| 1840 Entries scanned 2004/09/16 10:41:03| 0 Invalid entries. 2004/09/16 10:41:03| 0 With invalid flags. 2004/09/16 10:41:03| 1840 Objects loaded. 2004/09/16 10:41:03| 0 Objects expired. 2004/09/16 10:41:03| 0 Objects cancelled. 2004/09/16 10:41:03| 0 Duplicate URLs purged. 2004/09/16 10:41:03| 0 Swapfile clashes avoided. 2004/09/16 10:41:03| Took 0.6 seconds (2932.0 objects/sec). 2004/09/16 10:41:03| Beginning Validation Procedure 2004/09/16 10:41:03| Completed Validation Procedure 2004/09/16 10:41:03| Validated 1840 Entries 2004/09/16 10:41:03| store_swap_size = 19456k 2004/09/16 10:41:04| storeLateRelease: released 0 objects [EMAIL PROTECTED] squid]# Here is what happens at midnight, every day when the backup starts: 2004/09/14 00:00:27| Restarting Squid Cache (version 2.4.STABLE6)... 2004/09/14 00:00:27| FD 11 Closing HTTP connection 2004/09/14 00:00:27| FD 12 Closing ICP connection 2004/09/14 00:00:27| DNS Socket created on FD 4 2004/09/14 00:00:27| Adding nameserver 127.0.0.1 from /etc/resolv.conf 2004/09/14 00:00:27| Accepting HTTP connections at 0.0.0.0, port 8080, FD 8. 2004/09/14 00:00:27| Accepting ICP messages at 0.0.0.0, port 3130, FD 10. 2004/09/14 00:00:27| WCCP Disabled. 2004/09/14 00:00:27| Loaded Icons. 2004/09/14 00:00:27| Ready to serve requests. 2004/09/14 00:00:43| Preparing for shutdown after 0 requests 2004/09/14 00:00:43| Waiting 30 seconds for active connections to finish 2004/09/14 00:00:43| FD 8 Closing HTTP connection 2004/09/14 00:00:43| Shutting down... 2004/09/14 00:00:43| FD 10 Closing ICP connection 2004/09/14 00:00:43| Closing unlinkd pipe on FD 9 2004/09/14 00:00:43| storeDirWriteCleanLogs: Starting... 2004/09/14 00:00:43| Finished. Wrote 1840 entries. 2004/09/14 00:00:43| Took 0.0 seconds (1076023.4 entries/sec). CPU Usage: 0.120 seconds = 0.060 user + 0.060 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 498 Memory usage for squid via mallinfo(): total space in arena:2353 KB Ordinary blocks: 2323 KB 3 blks Small blocks: 0 KB 0 blks Holding blocks: 176 KB 1 blks Free Small blocks: 0 KB Free Ordinary blocks: 29 KB Total in use:2499 KB 106% Total free:29 KB 1% 2004/09/14 00:00:43| Squid Cache (Version 2.4.STABLE6): Exiting normally. you can see it is dying - it says Exiting normally... I don't want this to happen :) Now, I have excluded the /var/spool/squid directory... is there anything else I should be excluding? Thanks, Dan
Re: [squid-users] Squid process dying - possibly caused by backup?
Here is what happens at midnight, every day when the backup starts: 2004/09/14 00:00:27| Restarting Squid Cache (version 2.4.STABLE6)... Ok. This is a squid -k reconfigure 2004/09/14 00:00:27| FD 11 Closing HTTP connection 2004/09/14 00:00:27| FD 12 Closing ICP connection 2004/09/14 00:00:27| DNS Socket created on FD 4 2004/09/14 00:00:27| Adding nameserver 127.0.0.1 from /etc/resolv.conf 2004/09/14 00:00:27| Accepting HTTP connections at 0.0.0.0, port 8080, FD 8. 2004/09/14 00:00:27| Accepting ICP messages at 0.0.0.0, port 3130, FD 10. 2004/09/14 00:00:27| WCCP Disabled. 2004/09/14 00:00:27| Loaded Icons. 2004/09/14 00:00:27| Ready to serve requests. 2004/09/14 00:00:43| Preparing for shutdown after 0 requests Not good. This is a squid -k shutdown. Regards Henrik
[squid-users] Squid is dying
Hello , I have a problem with my squid. Squid is dying over and over again. cache.log says: (squid)[0x80a167d] /lib/i686/libpthread.so.0[0x4015d47e] (squid)[0x42028c48] (squid)[0x420c12db] (squid)[0x420bd350] (squid)(regexec+0x65)[0x420c2df5] (squid)(vfprintf+0x2b06)[0x804d966] (squid)(vfprintf+0x3671)[0x804e4d1] (squid)(vfprintf+0x395f)[0x804e7bf] (squid)(vfprintf+0x3a4a)[0x804e8aa] (squid)[0x8080621] (squid)[0x80806bf] (squid)[0x805ef0e] (squid)[0x805f123] (squid)[0x8060045] (squid)[0x805f361] (squid)[0x809c946] (squid)[0x809d0a0] (squid)[0x80a9e20] (squid)[0x80abc9d] (squid)[0x809f4b2] (squid)[0x8066099] (squid)[0x8086673] (squid)(__libc_start_main+0xa4)[0x420158d4] (squid)(geteuid+0x51)[0x804b5a1] 2003/12/19 09:18:08| Pinger socket opened on FD 22 2003/12/19 09:18:08| Ready to serve requests. 2003/12/19 09:18:08| Store rebuilding is 2.3% complete 2003/12/19 09:18:12| Done reading /cache2 swaplog (175997 entries) 2003/12/19 09:18:12| Done reading /cache1 swaplog (176008 entries) 2003/12/19 09:18:12| Finished rebuilding storage from disk. 2003/12/19 09:18:12|352005 Entries scanned 2003/12/19 09:18:12| 0 Invalid entries. 2003/12/19 09:18:12| 0 With invalid flags. 2003/12/19 09:18:12|352005 Objects loaded. 2003/12/19 09:18:12| 0 Objects expired. 2003/12/19 09:18:12| 0 Objects cancelled. 2003/12/19 09:18:12| 0 Duplicate URLs purged. 2003/12/19 09:18:12| 0 Swapfile clashes avoided. 2003/12/19 09:18:12| Took 4.1 seconds (85106.8 objects/sec). 2003/12/19 09:18:12| Beginning Validation Procedure 2003/12/19 09:18:12|262144 Entries Validated so far. 2003/12/19 09:18:12| Completed Validation Procedure 2003/12/19 09:18:12| Validated 352005 Entries 2003/12/19 09:18:12| store_swap_size = 4216836k 2003/12/19 09:18:13| storeLateRelease: released 0 objects 2003/12/19 09:18:34| icmpRecv: recv: (111) Connection refused 2003/12/19 09:18:34| Closing Pinger socket on FD 22 2003/12/19 09:18:40| WARNING: 1 swapin MD5 mismatches 2003/12/19 09:24:24| CACHEMGR: [EMAIL PROTECTED] requesting 'info' FATAL: Received Segment Violation...dying. 2003/12/19 09:24:48| storeDirWriteCleanLogs: Starting... 2003/12/19 09:24:48| WARNING: Closing open FD 18 2003/12/19 09:24:48| WARNING: Closing open FD 19 2003/12/19 09:24:49| 65536 entries written so far. 2003/12/19 09:24:49|131072 entries written so far. 2003/12/19 09:24:49|196608 entries written so far. 2003/12/19 09:24:49|262144 entries written so far. 2003/12/19 09:24:49|327680 entries written so far. 2003/12/19 09:24:49| Finished. Wrote 352006 entries. 2003/12/19 09:24:49| Took 0.3 seconds (1171381.5 entries/sec). CPU Usage: 4.780 seconds = 2.600 user + 2.180 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 435 total space in arena: 39664 KB Total free:34 KB 0% 2003/12/19 09:24:52| Starting Squid Cache version 2.5.STABLE4 for i686-pc-linux-gnu... 2003/12/19 09:24:52| Process ID 8631 2003/12/19 09:24:52| With 1024 file descriptors available 2003/12/19 09:24:52| Performing DNS Tests... 2003/12/19 09:24:52| Successful DNS name lookup tests... 2003/12/19 09:24:52| DNS Socket created at 0.0.0.0, port 1091, FD 5 2003/12/19 09:24:52| Adding nameserver 127.0.0.1 from squid.conf 2003/12/19 09:24:52| helperOpenServers: Starting 5 'ncsa_auth' processes 2003/12/19 09:24:52| Unlinkd pipe opened on FD 15 2003/12/19 09:24:52| Swap maxSize 8192000 KB, estimated 630153 objects 2003/12/19 09:24:52| Target number of buckets: 63015 2003/12/19 09:24:52| Using 65536 Store buckets 2003/12/19 09:24:52| Max Mem size: 13312 KB 2003/12/19 09:24:52| Max Swap size: 8192000 KB 2003/12/19 09:24:52| Local cache digest enabled; rebuild/rewrite every 14400/14400 sec 2003/12/19 09:24:52| Store logging disabled 2003/12/19 09:24:52| Rebuilding storage in /cache1 (CLEAN) 2003/12/19 09:24:52| Rebuilding storage in /cache2 (CLEAN) 2003/12/19 09:24:52| Using Round Robin store dir selection 2003/12/19 09:24:52| Current Directory is /usr/local/src/squid/squid-2.5.STABLE4 2003/12/19 09:24:52| Loaded Icons. 2003/12/19 09:24:52| Accepting HTTP connections at 0.0.0.0, port 3128, FD 18. 2003/12/19 09:24:52| Accepting HTTP connections at 0.0.0.0, port 8080, FD 19. 2003/12/19 09:24:52| Accepting ICP messages at 0.0.0.0, port 3130, FD 20. squid -v : --enable-cachemgr-hostname=localhost --enable-default-err-language=Polish --enable-poll --disable-ident-lookups --enable-storeio=aufs --with-pthreads --with-aio --with-aufs-threads=48 --enable-async-io --enable-removal-policies=heap --enable-delay-pools --enable-auth=basic --enable-basic-auth-helpers=NCSA --disable-htcp --enable-ssl --enable-cache-digests --enable-truncate --enable-icmp --enable-stacktraces --disable-wccp Squid version is squid-2.5.STABLE4 with all current patches. Please help. -- Regards
Re: [squid-users] Squid is dying
Please see the Squid FAQ on reporting bugs. Regards Henrik On Fri, 19 Dec 2003, Marcin Bartnik wrote: Hello , I have a problem with my squid. Squid is dying over and over again. cache.log says: (squid)[0x80a167d] /lib/i686/libpthread.so.0[0x4015d47e] (squid)[0x42028c48] (squid)[0x420c12db] (squid)[0x420bd350] (squid)(regexec+0x65)[0x420c2df5] (squid)(vfprintf+0x2b06)[0x804d966] (squid)(vfprintf+0x3671)[0x804e4d1] (squid)(vfprintf+0x395f)[0x804e7bf] (squid)(vfprintf+0x3a4a)[0x804e8aa] (squid)[0x8080621] (squid)[0x80806bf] (squid)[0x805ef0e] (squid)[0x805f123] (squid)[0x8060045] (squid)[0x805f361] (squid)[0x809c946] (squid)[0x809d0a0] (squid)[0x80a9e20] (squid)[0x80abc9d] (squid)[0x809f4b2] (squid)[0x8066099] (squid)[0x8086673] (squid)(__libc_start_main+0xa4)[0x420158d4] (squid)(geteuid+0x51)[0x804b5a1] 2003/12/19 09:18:08| Pinger socket opened on FD 22 2003/12/19 09:18:08| Ready to serve requests. 2003/12/19 09:18:08| Store rebuilding is 2.3% complete 2003/12/19 09:18:12| Done reading /cache2 swaplog (175997 entries) 2003/12/19 09:18:12| Done reading /cache1 swaplog (176008 entries) 2003/12/19 09:18:12| Finished rebuilding storage from disk. 2003/12/19 09:18:12|352005 Entries scanned 2003/12/19 09:18:12| 0 Invalid entries. 2003/12/19 09:18:12| 0 With invalid flags. 2003/12/19 09:18:12|352005 Objects loaded. 2003/12/19 09:18:12| 0 Objects expired. 2003/12/19 09:18:12| 0 Objects cancelled. 2003/12/19 09:18:12| 0 Duplicate URLs purged. 2003/12/19 09:18:12| 0 Swapfile clashes avoided. 2003/12/19 09:18:12| Took 4.1 seconds (85106.8 objects/sec). 2003/12/19 09:18:12| Beginning Validation Procedure 2003/12/19 09:18:12|262144 Entries Validated so far. 2003/12/19 09:18:12| Completed Validation Procedure 2003/12/19 09:18:12| Validated 352005 Entries 2003/12/19 09:18:12| store_swap_size = 4216836k 2003/12/19 09:18:13| storeLateRelease: released 0 objects 2003/12/19 09:18:34| icmpRecv: recv: (111) Connection refused 2003/12/19 09:18:34| Closing Pinger socket on FD 22 2003/12/19 09:18:40| WARNING: 1 swapin MD5 mismatches 2003/12/19 09:24:24| CACHEMGR: [EMAIL PROTECTED] requesting 'info' FATAL: Received Segment Violation...dying. 2003/12/19 09:24:48| storeDirWriteCleanLogs: Starting... 2003/12/19 09:24:48| WARNING: Closing open FD 18 2003/12/19 09:24:48| WARNING: Closing open FD 19 2003/12/19 09:24:49| 65536 entries written so far. 2003/12/19 09:24:49|131072 entries written so far. 2003/12/19 09:24:49|196608 entries written so far. 2003/12/19 09:24:49|262144 entries written so far. 2003/12/19 09:24:49|327680 entries written so far. 2003/12/19 09:24:49| Finished. Wrote 352006 entries. 2003/12/19 09:24:49| Took 0.3 seconds (1171381.5 entries/sec). CPU Usage: 4.780 seconds = 2.600 user + 2.180 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 435 total space in arena: 39664 KB Total free:34 KB 0% 2003/12/19 09:24:52| Starting Squid Cache version 2.5.STABLE4 for i686-pc-linux-gnu... 2003/12/19 09:24:52| Process ID 8631 2003/12/19 09:24:52| With 1024 file descriptors available 2003/12/19 09:24:52| Performing DNS Tests... 2003/12/19 09:24:52| Successful DNS name lookup tests... 2003/12/19 09:24:52| DNS Socket created at 0.0.0.0, port 1091, FD 5 2003/12/19 09:24:52| Adding nameserver 127.0.0.1 from squid.conf 2003/12/19 09:24:52| helperOpenServers: Starting 5 'ncsa_auth' processes 2003/12/19 09:24:52| Unlinkd pipe opened on FD 15 2003/12/19 09:24:52| Swap maxSize 8192000 KB, estimated 630153 objects 2003/12/19 09:24:52| Target number of buckets: 63015 2003/12/19 09:24:52| Using 65536 Store buckets 2003/12/19 09:24:52| Max Mem size: 13312 KB 2003/12/19 09:24:52| Max Swap size: 8192000 KB 2003/12/19 09:24:52| Local cache digest enabled; rebuild/rewrite every 14400/14400 sec 2003/12/19 09:24:52| Store logging disabled 2003/12/19 09:24:52| Rebuilding storage in /cache1 (CLEAN) 2003/12/19 09:24:52| Rebuilding storage in /cache2 (CLEAN) 2003/12/19 09:24:52| Using Round Robin store dir selection 2003/12/19 09:24:52| Current Directory is /usr/local/src/squid/squid-2.5.STABLE4 2003/12/19 09:24:52| Loaded Icons. 2003/12/19 09:24:52| Accepting HTTP connections at 0.0.0.0, port 3128, FD 18. 2003/12/19 09:24:52| Accepting HTTP connections at 0.0.0.0, port 8080, FD 19. 2003/12/19 09:24:52| Accepting ICP messages at 0.0.0.0, port 3130, FD 20. squid -v : --enable-cachemgr-hostname=localhost --enable-default-err-language=Polish --enable-poll --disable-ident-lookups --enable-storeio=aufs --with-pthreads --with-aio --with-aufs-threads=48 --enable-async-io --enable-removal-policies=heap --enable-delay-pools --enable-auth=basic --enable-basic-auth-helpers=NCSA --disable-htcp --enable-ssl --enable-cache-digests --enable-truncate --enable-icmp --enable-stacktraces --disable-wccp
[squid-users] Squid 2.5S1 dying unexpectedly
Several times in the last 8 days our main proxy has died 3 times with the following logged in cache.log: FATAL: Received Segment Violation...dying. 2003/02/03 14:49:30| storeDirWriteCleanLogs: Starting... 2003/02/03 14:49:31| 65536 entries written so far. 2003/02/03 14:49:32|131072 entries written so far. 2003/02/03 14:49:32|196608 entries written so far. 2003/02/03 14:49:33|262144 entries written so far. 2003/02/03 14:49:33|327680 entries written so far. 2003/02/03 14:49:34|393216 entries written so far. 2003/02/03 14:49:34|458752 entries written so far. 2003/02/03 14:49:34| WARNING: Closing open FD 27 2003/02/03 14:49:35| Finished. Wrote 462057 entries. 2003/02/03 14:49:35| Took 4.2 seconds (109876.8 entries/sec). CPU Usage: 837.750 seconds = 529.470 user + 308.280 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 110609 Memory usage for squid via mallinfo(): total space in arena: 166322 KB Ordinary blocks: 165130 KB 12116 blks Small blocks: 0 KB 0 blks Holding blocks: 2736 KB 3 blks Free Small blocks: 0 KB Free Ordinary blocks:1191 KB Total in use: 167866 KB 101% Total free: 1191 KB 1% There is no core file being produced. The above crash happened during working hours, but as some have occurred outside busy periods, I don't think it is traffic-related. Details of the build being used are: Squid Cache: Version 2.5.STABLE1-20021118 configure options: --enable-dlmalloc --enable-gnuregex --enable-async-io=160 --enable-useragent-log --enable-referer-log --disable-wccp --enable-snmp --enable-poll --enable-err-languages=English '--enable-removal-policies=lru heap' Together with: SmartFilter Info: SmartFilter Version: 3.1.1.02 SmartFilter Info: SmartFilter API version: 3.1.3 Via the SmarFilter patches supplied by Secure Computing. It was all built using gcc 3.2 (with the Sun linker) on Solaris 7. A similar build without the SF patches and running on Solaris 2.6 hasn't had this problem (it is the parent of the above in our DMZ.) In addition, this symptom did not occur prior to 8 days ago (we have been running the current config since December 22 and the only changes to SF have been the site.txt file and weekly control list updates.) Has anyone seen this symptom? In case it is SF-related I am also asking Secure Computing. Michael Lightfoot Unix Consultant ISG Host Systems Comcare +61 2 62750680 NOTICE: This e-mail message and attachments may contain confidential information. If you are not the intended recipient you should not use or disclose any information in the message or attachments. If received in error, please notify the sender by return email immediately. Comcare does not waive any confidentiality or privilege.
