[squid-users] FATAL: Received Segment Violation...dying.
hi all , i have smp and it works fine at start of squid , but after some time , one kids of my kids must be killed and restarted agian , and so on here which showed in cache.log *FATAL: Received Segment Violation...dying. CPU Usage: 75.134 seconds = 52.767 user + 22.367 sys Maximum Resident Size: 739872 KB Page faults with physical i/o: 0 Memory usage for squid via mallinfo():* i dont know why this Dying occurs ?? as u see, it wask killed and it started agian ! after sometime, squid is hanged and i must killed it and started it agian == FATAL: Received Segment Violation...dying. CPU Usage: 75.134 seconds = 52.767 user + 22.367 sys Maximum Resident Size: 739872 KB Page faults with physical i/o: 0 Memory usage for squid via mallinfo(): total space in arena: 85848 KB Ordinary blocks:82297 KB737 blks Small blocks: 0 KB 1 blks Holding blocks: 72988 KB 8 blks Free Small blocks: 0 KB Free Ordinary blocks:3550 KB Total in use: 155285 KB 181% Total free: 3550 KB 4% 2013/12/19 10:35:52 kid2| Starting Squid Cache version 3.3.9 for i486-pc-linux-gnu... 2013/12/19 10:35:52 kid2| Process ID 20001 2013/12/19 10:35:52 kid2| Process Roles: worker 2013/12/19 10:35:52 kid2| With 131072 file descriptors available 2013/12/19 10:35:52 kid2| Initializing IP Cache... 2013/12/19 10:35:52 kid2| DNS Socket created at [::], FD 7 2013/12/19 10:35:52 kid2| DNS Socket created at 0.0.0.0, FD 8 2013/12/19 10:35:52 kid2| Adding nameserver 127.0.0.1 from /etc/resolv.conf 2013/12/19 10:35:52 kid2| Adding nameserver 127.0.0.1 from /etc/resolv.conf 2013/12/19 10:35:52 kid2| Logfile: opening log stdio:/var/log/squid/access.log 2013/12/19 10:35:52 kid2| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2013/12/19 10:35:52 kid2| Store logging disabled 2013/12/19 10:35:52 kid2| Swap maxSize 0 + 1536000 KB, estimated 118153 objects 2013/12/19 10:35:52 kid2| Target number of buckets: 5907 2013/12/19 10:35:52 kid2| Using 8192 Store buckets 2013/12/19 10:35:52 kid2| Max Mem size: 1536000 KB [shared] 2013/12/19 10:35:52 kid2| Target number of buckets: 5907 2013/12/19 10:35:52 kid2| Using 8192 Store buckets 2013/12/19 10:35:52 kid2| Max Mem size: 1536000 KB [shared] 2013/12/19 10:35:52 kid2| Max Swap size: 0 KB 2013/12/19 10:35:52 kid2| Using Least Load store dir selection 2013/12/19 10:35:52 kid2| Current Directory is /root 2013/12/19 10:35:52 kid2| Loaded Icons. 2013/12/19 10:35:52 kid2| HTCP Disabled. 2013/12/19 10:35:52 kid2| Squid plugin modules loaded: 0 2013/12/19 10:35:52 kid2| Adaptation support is off. 2013/12/19 10:35:52 kid2| Finished rebuilding storage from disk. 2013/12/19 10:35:52 kid2| 0 Entries scanned 2013/12/19 10:35:52 kid2| 0 Invalid entries. 2013/12/19 10:35:52 kid2| 0 With invalid flags. 2013/12/19 10:35:52 kid2| 0 Objects loaded. 2013/12/19 10:35:52 kid2| 0 Objects expired. 2013/12/19 10:35:52 kid2| 0 Objects cancelled. 2013/12/19 10:35:52 kid2| 0 Duplicate URLs purged. 2013/12/19 10:35:52 kid2| 0 Swapfile clashes avoided. 2013/12/19 10:35:52 kid2| Took 0.02 seconds ( 0.00 objects/sec). 2013/12/19 10:35:52 kid2| Beginning Validation Procedure 2013/12/19 10:35:52 kid2| 0 Duplicate URLs purged. 2013/12/19 10:35:52 kid2| 0 Swapfile clashes avoided. 2013/12/19 10:35:52 kid2| Took 0.02 seconds ( 0.00 objects/sec). 2013/12/19 10:35:52 kid2| Beginning Validation Procedure 2013/12/19 10:35:52 kid2| Completed Validation Procedure 2013/12/19 10:35:52 kid2| Validated 0 Entries 2013/12/19 10:35:52 kid2| store_swap_size = 0.00 KB 2013/12/19 10:35:52 kid2| Accepting HTTP Socket connections at local=xx remote=[::] FD 16 flags=1 2013/12/19 10:35:52 kid2| Accepting TPROXY spoofing HTTP Socket connections at local=x:xx remote=[::] FD 17 flags=17 2013/12/19 10:35:53 kid2| storeLateRelease: released 0 objects how troubleshoot this issue ?? wish to help regards - Dr.x -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/FATAL-Received-Segment-Violation-dying-tp4663955.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] FATAL: Received Segment Violation...dying.
On 12/20/2013 01:26 AM, Dr.x wrote: i have smp and it works fine at start of squid , but after some time , one kids of my kids must be killed and restarted agian , and so on *FATAL: Received Segment Violation...dying. i dont know why this Dying occurs ?? It most likely occurs because of a bug in Squid code. how troubleshoot this issue ?? Please file a bug report with bugzilla, posting a gdb backtrace from the core file created when a worker dies. If there is no core file or you need more information on how to collect a back trace, please visit: http://wiki.squid-cache.org/SquidFaq/BugReporting Please note that without a backtrace, your report will most likely not contain the information necessary to triage and fix the bug. Thank you, Alex.
RE: [squid-users] FATAL: Received Segment Violation...dying.
Hey there was a permission problem with director where coredump was suppose to be created, but got that fixed following is the coredump, can some one highlight what is wrong ? squid-1# gdb /usr/local/squid/sbin/squid /usr/local/squid/var/cache/core GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu... (no debugging symbols found) warning: Can't read pathname for load map: Input/output error. Reading symbols from /lib/libcrypt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.1 Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_compat.so.2 Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_nis.so.2 Reading symbols from /lib/libnss_dns.so.2... (no debugging symbols found)...done. Loaded symbols for /lib/libnss_dns.so.2 Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libresolv.so.2 (no debugging symbols found) Core was generated by `(squid)'. Program terminated with signal 6, Aborted. [New process 4412] [New process 4424] [New process 4430] [New process 4431] [New process 4437] [New process 4428] [New process 4425] [New process 4427] [New process 4470] [New process 4475] [New process 4472] [New process 4463] [New process 4464] [New process 4474] [New process 4471] [New process 4436] [New process 4426] [New process 4434] [New process 4450] [New process 4447] [New process 4465] [New process 4429] [New process 4432] [New process 4446] [New process 4433] [New process 4449] [New process 4455] [New process 4458] [New process 4462] [New process 4442] [New process 4439] [New process 4448] [New process 4435] [New process 4456] [New process 4460] [New process ] [New process 4445] [New process 4440] [New process 4452] [New process 4438] [New process 4457] [New process 4468] [New process 4466] [New process 4454] [New process 4441] [New process 4453] [New process 4461] [New process 4467] [New process 4443] [New process 4459] [New process 4451] [New process 4469] [New process 4473] #0 0x7f5f94deaed5 in raise () from /lib/libc.so.6 (gdb) bt #0 0x7f5f94deaed5 in raise () from /lib/libc.so.6 #1 0x7f5f94dec3f3 in abort () from /lib/libc.so.6 #2 0x004824ad in ?? () #3 signal handler called #4 0x7f5f94e33a72 in strcmp () from /lib/libc.so.6 #5 0x004268f2 in ?? () #6 0x0047a1b4 in ?? () #7 0x0047a4cb in ?? () #8 0x0041d832 in ?? () #9 0x0041fbe3 in ?? () #10 0x00406ec5 in ?? () #11 0x00406ec5 in ?? () #12 0x0042183b in ?? () #13 0x0042bbfe in ?? () #14 0x00456380 in ?? () #15 0x7f5f94dd71a6 in __libc_start_main () from /lib/libc.so.6 #16 0x00404069 in ?? () #17 0x7fff5f665878 in ?? () #18 0x001c in ?? () #19 0x0001 in ?? () #20 0x7fff5f666e9e in ?? () #21 0x in ?? () My settup * Squid Cache: Version 2.7.STABLE6 configure options: '--enable-async-io' '--enable-icmp' '--enable-snmp' '--enable-cache-digests' '--enable-follow-x-forwarded-for' '--enable-storeio=aufs,ufs,null,diskd,coss' '--enable-removal-policies=heap,lru' '--with-maxfd=65535' '--disable-ident-lookups' '--enable-truncate' '--enable-linux-tproxy' '--enable-linux-netfilter' '--enable-large-cache-files' * Kernel 2.6.31.13 * Debain lenny 5.04 machine is setup in bridge mode with tproxy, with ip configured on br0 interface. any help will be much appreciated. thanks in advance Date: Tue, 25 May 2010 09:29:51 -0700 From: george.herb...@gmail.com To: khanza...@hotmail.com CC: squid-users@squid-cache.org Subject: Re: [squid-users] FATAL: Received Segment Violation...dying. You will have to set up
Re: [squid-users] FATAL: Received Segment Violation...dying.
sameer khan wrote: Hey there was a permission problem with director where coredump was suppose to be created, but got that fixed following is the coredump, can some one highlight what is wrong ? squid-1# gdb /usr/local/squid/sbin/squid /usr/local/squid/var/cache/core GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu... (no debugging symbols found) warning: Can't read pathname for load map: Input/output error. Reading symbols from /lib/libcrypt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.1 Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_compat.so.2 Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_nis.so.2 Reading symbols from /lib/libnss_dns.so.2... (no debugging symbols found)...done. Loaded symbols for /lib/libnss_dns.so.2 Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libresolv.so.2 (no debugging symbols found) Core was generated by `(squid)'. Program terminated with signal 6, Aborted. [New process 4412] [New process 4424] [New process 4430] [New process 4431] [New process 4437] [New process 4428] [New process 4425] [New process 4427] [New process 4470] [New process 4475] [New process 4472] [New process 4463] [New process 4464] [New process 4474] [New process 4471] [New process 4436] [New process 4426] [New process 4434] [New process 4450] [New process 4447] [New process 4465] [New process 4429] [New process 4432] [New process 4446] [New process 4433] [New process 4449] [New process 4455] [New process 4458] [New process 4462] [New process 4442] [New process 4439] [New process 4448] [New process 4435] [New process 4456] [New process 4460] [New process ] [New process 4445] [New process 4440] [New process 4452] [New process 4438] [New process 4457] [New process 4468] [New process 4466] [New process 4454] [New process 4441] [New process 4453] [New process 4461] [New process 4467] [New process 4443] [New process 4459] [New process 4451] [New process 4469] [New process 4473] #0 0x7f5f94deaed5 in raise () from /lib/libc.so.6 (gdb) bt #0 0x7f5f94deaed5 in raise () from /lib/libc.so.6 #1 0x7f5f94dec3f3 in abort () from /lib/libc.so.6 #2 0x004824ad in ?? () #3 signal handler called #4 0x7f5f94e33a72 in strcmp () from /lib/libc.so.6 #5 0x004268f2 in ?? () Darn. The function name and other symbols have been stripped out of the squid binary. The app can;t generate any useful traces. You will need to try and replicate the problem in a squid built with debug symbols still inside. My settup * Squid Cache: Version 2.7.STABLE6 configure options: '--enable-async-io' '--enable-icmp' '--enable-snmp' '--enable-cache-digests' '--enable-follow-x-forwarded-for' '--enable-storeio=aufs,ufs,null,diskd,coss' '--enable-removal-policies=heap,lru' '--with-maxfd=65535' '--disable-ident-lookups' '--enable-truncate' '--enable-linux-tproxy' '--enable-linux-netfilter' '--enable-large-cache-files' * Kernel 2.6.31.13 FWIW: linux kernel 2.6.3* do not support TPROXY version 2 (which is the version in squid 2.7). For TPROXYv4 you will needed squid-3.1 or later. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.3
RE: [squid-users] FATAL: Received Segment Violation...dying.
hey , thanks amo for reply, but how to i build with debug symbols, do u mean by --enable-stacktrace ?. thanks and best regards Date: Wed, 26 May 2010 23:49:24 +1200 From: squ...@treenet.co.nz To: squid-users@squid-cache.org Subject: Re: [squid-users] FATAL: Received Segment Violation...dying. sameer khan wrote: Hey there was a permission problem with director where coredump was suppose to be created, but got that fixed following is the coredump, can some one highlight what is wrong ? squid-1# gdb /usr/local/squid/sbin/squid /usr/local/squid/var/cache/core GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu... (no debugging symbols found) warning: Can't read pathname for load map: Input/output error. Reading symbols from /lib/libcrypt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.1 Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_compat.so.2 Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_nis.so.2 Reading symbols from /lib/libnss_dns.so.2... (no debugging symbols found)...done. Loaded symbols for /lib/libnss_dns.so.2 Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libresolv.so.2 (no debugging symbols found) Core was generated by `(squid)'. Program terminated with signal 6, Aborted. [New process 4412] [New process 4424] [New process 4430] [New process 4431] [New process 4437] [New process 4428] [New process 4425] [New process 4427] [New process 4470] [New process 4475] [New process 4472] [New process 4463] [New process 4464] [New process 4474] [New process 4471] [New process 4436] [New process 4426] [New process 4434] [New process 4450] [New process 4447] [New process 4465] [New process 4429] [New process 4432] [New process 4446] [New process 4433] [New process 4449] [New process 4455] [New process 4458] [New process 4462] [New process 4442] [New process 4439] [New process 4448] [New process 4435] [New process 4456] [New process 4460] [New process ] [New process 4445] [New process 4440] [New process 4452] [New process 4438] [New process 4457] [New process 4468] [New process 4466] [New process 4454] [New process 4441] [New process 4453] [New process 4461] [New process 4467] [New process 4443] [New process 4459] [New process 4451] [New process 4469] [New process 4473] #0 0x7f5f94deaed5 in raise () from /lib/libc.so.6 (gdb) bt #0 0x7f5f94deaed5 in raise () from /lib/libc.so.6 #1 0x7f5f94dec3f3 in abort () from /lib/libc.so.6 #2 0x004824ad in ?? () #3 #4 0x7f5f94e33a72 in strcmp () from /lib/libc.so.6 #5 0x004268f2 in ?? () Darn. The function name and other symbols have been stripped out of the squid binary. The app can;t generate any useful traces. You will need to try and replicate the problem in a squid built with debug symbols still inside. My settup * Squid Cache: Version 2.7.STABLE6 configure options: '--enable-async-io' '--enable-icmp' '--enable-snmp' '--enable-cache-digests' '--enable-follow-x-forwarded-for' '--enable-storeio=aufs,ufs,null,diskd,coss' '--enable-removal-policies=heap,lru' '--with-maxfd=65535' '--disable-ident-lookups' '--enable-truncate' '--enable-linux-tproxy' '--enable-linux-netfilter' '--enable-large-cache-files' * Kernel 2.6.31.13 FWIW: linux kernel 2.6.3* do not support TPROXY version 2 (which is the version in squid 2.7). For TPROXYv4 you will needed squid-3.1 or later. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.3 _ http
RE: [squid-users] FATAL: Received Segment Violation...dying.
ons 2010-05-26 klockan 14:26 + skrev sameer khan: thanks amo for reply, but how to i build with debug symbols, do u mean by --enable-stacktrace ?. The default is to build with debug symbols unless you override CFLAGS or strip the binaries after install. Regards Henrik
[squid-users] FATAL: Received Segment Violation...dying.
Hey squid is just dying with fatal error: FATAL: Received Segment Violation...dying. 2010/05/25 17:52:52| storeDirWriteCleanLogs: Starting... 2010/05/25 17:52:52| WARNING: Closing open FD 29 2010/05/25 17:52:52| commSetEvents: epoll_ctl(EPOLL_CTL_DEL): failed on fd=29: (1) Operation not permitted 2010/05/25 17:52:52| WARNING: Closing open FD 30 2010/05/25 17:52:52| commSetEvents: epoll_ctl(EPOLL_CTL_DEL): failed on fd=30: (1) Operation not permitted 2010/05/25 17:52:53| 65536 entries written so far. 2010/05/25 17:52:53| 131072 entries written so far. 2010/05/25 17:52:53| 196608 entries written so far. 2010/05/25 17:52:53| 262144 entries written so far. 2010/05/25 17:52:53| 327680 entries written so far. 2010/05/25 17:52:53| 393216 entries written so far. 2010/05/25 17:52:53| 458752 entries written so far. 2010/05/25 17:52:53| 524288 entries written so far. 2010/05/25 17:52:53| 589824 entries written so far. 2010/05/25 17:52:53| 655360 entries written so far. 2010/05/25 17:52:54| 720896 entries written so far. 2010/05/25 17:52:54| 786432 entries written so far. 2010/05/25 17:52:54| 851968 entries written so far. 2010/05/25 17:52:54| 917504 entries written so far. 2010/05/25 17:52:54| 983040 entries written so far. 2010/05/25 17:52:54| 1048576 entries written so far. 2010/05/25 17:52:54| 1114112 entries written so far. 2010/05/25 17:52:54| 1179648 entries written so far. 2010/05/25 17:52:54| 1245184 entries written so far. 2010/05/25 17:52:54| 1310720 entries written so far. 2010/05/25 17:52:55| 1376256 entries written so far. 2010/05/25 17:52:55| 1441792 entries written so far. 2010/05/25 17:52:55| 1507328 entries written so far. 2010/05/25 17:52:55| 1572864 entries written so far. 2010/05/25 17:52:55| 1638400 entries written so far. 2010/05/25 17:52:55| 1703936 entries written so far. 2010/05/25 17:52:55| 1769472 entries written so far. 2010/05/25 17:52:55| 1835008 entries written so far. 2010/05/25 17:52:55| 1900544 entries written so far. 2010/05/25 17:52:55| 1966080 entries written so far. 2010/05/25 17:52:55| 2031616 entries written so far. 2010/05/25 17:52:56| 2097152 entries written so far. 2010/05/25 17:52:56| 2162688 entries written so far. 2010/05/25 17:52:56| 2228224 entries written so far. 2010/05/25 17:52:56| 2293760 entries written so far. 2010/05/25 17:53:03| Finished. Wrote 2338090 entries. 2010/05/25 17:53:03| Took 10.2 seconds (228705.3 entries/sec). CPU Usage: 12716.239 seconds = 6215.796 user + 6500.442 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 17950 Memory usage for squid via mallinfo(): total space in arena: 580484 KB Ordinary blocks: 579739 KB 287 blks Small blocks: 0 KB 4 blks Holding blocks: 57608 KB 3 blks Free Small blocks: 0 KB Free Ordinary blocks: 745 KB Total in use: 637347 KB 100% Total free: 745 KB 0% 2010/05/25 17:53:07| Starting Squid Cache version 2.7.STABLE6 for x86_64-unknown-linux-gnu... 2010/05/25 17:53:07| Process ID 4412 2010/05/25 17:53:07| With 65535 file descriptors available 2010/05/25 17:53:07| Using epoll for the IO loop 2010/05/25 17:53:07| Performing DNS Tests... 2010/05/25 17:53:07| Successful DNS name lookup tests... 2010/05/25 17:53:07| DNS Socket created at 0.0.0.0, port 26621, FD 6 2010/05/25 17:53:07| Adding nameserver 127.0.0.1 from /etc/resolv.conf 2010/05/25 17:53:07| helperOpenServers: Starting 10 'storeurl.pl' processes 2010/05/25 17:53:07| Unlinkd pipe opened on FD 20 2010/05/25 17:53:07| Swap maxSize 565248000 + 3145728 KB, estimated 43722594 objects 2010/05/25 17:53:07| Target number of buckets: 2186129 2010/05/25 17:53:07| Using 4194304 Store buckets 2010/05/25 17:53:07| Max Mem size: 3145728 KB 2010/05/25 17:53:07| Max Swap size: 565248000 KB 2010/05/25 17:53:07| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2010/05/25 17:53:07| Store logging disabled 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sda1 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sda2 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sda3 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sda4 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sdb1 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sdb2 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sdb3 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sdb4 (CLEAN) 2010/05/25 17:53:07| Using Least Load store dir selection 2010/05/25 17:53:07| Set Current Directory to /usr/local/squid/var/cache 2010/05/25 17:53:07| Loaded Icons. 2010/05/25 17:53:07| Accepting transparently proxied HTTP connections at 0.0.0.0, port
Re: [squid-users] FATAL: Received Segment Violation...dying.
You will have to set up the system to collect a core dump, you need that to tell where in the code it seg faulted. On Tue, May 25, 2010 at 5:56 AM, sameer khan khanza...@hotmail.com wrote: Hey squid is just dying with fatal error: FATAL: Received Segment Violation...dying. 2010/05/25 17:52:52| storeDirWriteCleanLogs: Starting... 2010/05/25 17:52:52| WARNING: Closing open FD 29 2010/05/25 17:52:52| commSetEvents: epoll_ctl(EPOLL_CTL_DEL): failed on fd=29: (1) Operation not permitted 2010/05/25 17:52:52| WARNING: Closing open FD 30 2010/05/25 17:52:52| commSetEvents: epoll_ctl(EPOLL_CTL_DEL): failed on fd=30: (1) Operation not permitted 2010/05/25 17:52:53| 65536 entries written so far. 2010/05/25 17:52:53| 131072 entries written so far. 2010/05/25 17:52:53| 196608 entries written so far. 2010/05/25 17:52:53| 262144 entries written so far. 2010/05/25 17:52:53| 327680 entries written so far. 2010/05/25 17:52:53| 393216 entries written so far. 2010/05/25 17:52:53| 458752 entries written so far. 2010/05/25 17:52:53| 524288 entries written so far. 2010/05/25 17:52:53| 589824 entries written so far. 2010/05/25 17:52:53| 655360 entries written so far. 2010/05/25 17:52:54| 720896 entries written so far. 2010/05/25 17:52:54| 786432 entries written so far. 2010/05/25 17:52:54| 851968 entries written so far. 2010/05/25 17:52:54| 917504 entries written so far. 2010/05/25 17:52:54| 983040 entries written so far. 2010/05/25 17:52:54| 1048576 entries written so far. 2010/05/25 17:52:54| 1114112 entries written so far. 2010/05/25 17:52:54| 1179648 entries written so far. 2010/05/25 17:52:54| 1245184 entries written so far. 2010/05/25 17:52:54| 1310720 entries written so far. 2010/05/25 17:52:55| 1376256 entries written so far. 2010/05/25 17:52:55| 1441792 entries written so far. 2010/05/25 17:52:55| 1507328 entries written so far. 2010/05/25 17:52:55| 1572864 entries written so far. 2010/05/25 17:52:55| 1638400 entries written so far. 2010/05/25 17:52:55| 1703936 entries written so far. 2010/05/25 17:52:55| 1769472 entries written so far. 2010/05/25 17:52:55| 1835008 entries written so far. 2010/05/25 17:52:55| 1900544 entries written so far. 2010/05/25 17:52:55| 1966080 entries written so far. 2010/05/25 17:52:55| 2031616 entries written so far. 2010/05/25 17:52:56| 2097152 entries written so far. 2010/05/25 17:52:56| 2162688 entries written so far. 2010/05/25 17:52:56| 2228224 entries written so far. 2010/05/25 17:52:56| 2293760 entries written so far. 2010/05/25 17:53:03| Finished. Wrote 2338090 entries. 2010/05/25 17:53:03| Took 10.2 seconds (228705.3 entries/sec). CPU Usage: 12716.239 seconds = 6215.796 user + 6500.442 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 17950 Memory usage for squid via mallinfo(): total space in arena: 580484 KB Ordinary blocks: 579739 KB 287 blks Small blocks: 0 KB 4 blks Holding blocks: 57608 KB 3 blks Free Small blocks: 0 KB Free Ordinary blocks: 745 KB Total in use: 637347 KB 100% Total free: 745 KB 0% 2010/05/25 17:53:07| Starting Squid Cache version 2.7.STABLE6 for x86_64-unknown-linux-gnu... 2010/05/25 17:53:07| Process ID 4412 2010/05/25 17:53:07| With 65535 file descriptors available 2010/05/25 17:53:07| Using epoll for the IO loop 2010/05/25 17:53:07| Performing DNS Tests... 2010/05/25 17:53:07| Successful DNS name lookup tests... 2010/05/25 17:53:07| DNS Socket created at 0.0.0.0, port 26621, FD 6 2010/05/25 17:53:07| Adding nameserver 127.0.0.1 from /etc/resolv.conf 2010/05/25 17:53:07| helperOpenServers: Starting 10 'storeurl.pl' processes 2010/05/25 17:53:07| Unlinkd pipe opened on FD 20 2010/05/25 17:53:07| Swap maxSize 565248000 + 3145728 KB, estimated 43722594 objects 2010/05/25 17:53:07| Target number of buckets: 2186129 2010/05/25 17:53:07| Using 4194304 Store buckets 2010/05/25 17:53:07| Max Mem size: 3145728 KB 2010/05/25 17:53:07| Max Swap size: 565248000 KB 2010/05/25 17:53:07| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2010/05/25 17:53:07| Store logging disabled 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sda1 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sda2 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sda3 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sda4 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sdb1 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sdb2 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in /usr/local/squid/var/cache/sdb3 (CLEAN) 2010/05/25 17:53:07| Rebuilding storage in
[squid-users] FATAL: Received Segment Violation...dying
Hi all, I get FATAL: Received Segment Violation...dying. every hour or so. It is always prefaced by : 2006/11/06 10:37:23| 84490d8 lookup for 50 2006/11/06 10:37:23| 84490d8: joining for id 50 2006/11/06 10:37:23| 84490d8: joined for id 50: * FATAL: Received Segment Violation...dying. The 84490d8 number is different each time, but it is still prefaced by this lookup for 50 thing. It is Squid 2.6 STABLE4. I have been trying to trace down this problem for days and just seem to be spinning my wheels. I tried re-compiling without using the Gcc optimizations as per another article, no luck. The server still drops dead every hour-hour and 10 minutes and then reboots. I have checked my cron extensively looking for anything that might be running every hour, the only thing in there that happens on less than a weekly basis is the nightly log file rotate for squid (11:50pm). Let me know if there is any other data i can provide to help you help me :) -Jake
Re: [squid-users] FATAL: Received Segment Violation...dying
mån 2006-11-06 klockan 15:12 -0500 skrev Jacob Dana: Hi all, I get FATAL: Received Segment Violation...dying. every hour or so. It is always prefaced by : 2006/11/06 10:37:23| 84490d8 lookup for 50 2006/11/06 10:37:23| 84490d8: joining for id 50 2006/11/06 10:37:23| 84490d8: joined for id 50: * Looks like debug level 6 messages from HttpHeader.c. Have you set debug_options? FATAL: Received Segment Violation...dying. http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19 need to include a stack trace. Without it nothing can be done. The 84490d8 number is different each time, but it is still prefaced by this lookup for 50 thing. It is Squid 2.6 STABLE4. I have been trying to trace down this problem for days and just seem to be spinning my wheels. I tried re-compiling without using the Gcc optimizations as per another article, no luck. The server still drops dead every hour-hour and 10 minutes and then reboots. Server reboots? Then it's worse than a Squid issue.. Squid issues only cause Squid to restart.. Anything in the system logs? (messages/syslog etc). Regards Henrik signature.asc Description: Detta är en digitalt signerad meddelandedel
[squid-users] Fatal: Received Segment Violation ....dying
All I am experiencing squid restarts very frequently and notices in cache.log that this site is accessed which is possible causing the crashe: Fatal: Received Segment Violation dying Ctx: enter level 0: 'http://newsimg.bbc.co.uk/nol/ukfs_news/js/av.js' I have tried to access this site but nothing happens, but every time it dies it due to a bbc website. How can I resolve this Thanks Levent Mehmet Network Analyst Server and Network Team [EMAIL PROTECTED] Operate Unit Market Towers, 20th Floor 1 Nine Elms Lane London SW8 5NQ E-mail: [EMAIL PROTECTED] Phone: +44 20 7084 3517 Fax: +44 20 7084 2536 This email and any files transmitted with it are confidential. If you are not the intended recipient, any reading, printing, storage, disclosure, copying or any other action taken in respect of this email is prohibited and may be unlawful. If you are not the intended recipient, please notify the sender immediately by using the reply function and then permanently delete what you have received.Incoming and outgoing email messages are routinely monitored for compliance with the Department of Healths policy on the use of electronic communications. For more information on the Department of Healths email policy, click http;//www.doh.gov.uk/emaildisclaimer.htm The original of this email was scanned for viruses by Government Secure Intranet (GSi) virus scanning service supplied exclusively by Cable Wireless in partnership with MessageLabs. On leaving the GSI this email was certified virus free. The MessageLabs Anti Virus Service is the first managed service to achieve the CSIA Claims Tested Mark (CCTM Certificate Number 2006/04/0007), the UK Government quality mark initiative for information security products and services. For more information about this please visit www.cctmark.gov.uk
Re: [squid-users] Fatal: Received Segment Violation ....dying
On Mon, Aug 07, 2006, Mehmet, Levent (Accenture) wrote: All I am experiencing squid restarts very frequently and notices in cache.log that this site is accessed which is possible causing the crashe: Fatal: Received Segment Violation dying Ctx: enter level 0: 'http://newsimg.bbc.co.uk/nol/ukfs_news/js/av.js' I have tried to access this site but nothing happens, but every time it dies it due to a bbc website. How can I resolve this You need to tell us which version of Squid you're running. Adrian
RE: [squid-users] Fatal: Received Segment Violation ....dying
Version 2.6.stable1 -Original Message- From: Adrian Chadd [mailto:[EMAIL PROTECTED] Sent: 07 August 2006 09:40 To: Mehmet, Levent (Accenture) Cc: squid-users@squid-cache.org Subject: Re: [squid-users] Fatal: Received Segment Violation dying On Mon, Aug 07, 2006, Mehmet, Levent (Accenture) wrote: All I am experiencing squid restarts very frequently and notices in cache.log that this site is accessed which is possible causing the crashe: Fatal: Received Segment Violation dying Ctx: enter level 0: 'http://newsimg.bbc.co.uk/nol/ukfs_news/js/av.js' I have tried to access this site but nothing happens, but every time it dies it due to a bbc website. How can I resolve this You need to tell us which version of Squid you're running. Adrian PLEASE NOTE: THE ABOVE MESSAGE WAS RECEIVED FROM THE INTERNET. On entering the GSI, this email was scanned for viruses by the Government Secure Intranet (GSi) virus scanning service supplied exclusively by Cable Wireless in partnership with MessageLabs. In case of problems, please call your organisational IT Helpdesk. The MessageLabs Anti Virus Service is the first managed service to achieve the CSIA Claims Tested Mark (CCTM Certificate Number 2006/04/0007), the UK Government quality mark initiative for information security products and services. For more information about this please visit www.cctmark.gov.uk This email and any files transmitted with it are confidential. If you are not the intended recipient, any reading, printing, storage, disclosure, copying or any other action taken in respect of this email is prohibited and may be unlawful. If you are not the intended recipient, please notify the sender immediately by using the reply function and then permanently delete what you have received.Incoming and outgoing email messages are routinely monitored for compliance with the Department of Healths policy on the use of electronic communications. For more information on the Department of Healths email policy, click http;//www.doh.gov.uk/emaildisclaimer.htm The original of this email was scanned for viruses by Government Secure Intranet (GSi) virus scanning service supplied exclusively by Cable Wireless in partnership with MessageLabs. On leaving the GSI this email was certified virus free. The MessageLabs Anti Virus Service is the first managed service to achieve the CSIA Claims Tested Mark (CCTM Certificate Number 2006/04/0007), the UK Government quality mark initiative for information security products and services. For more information about this please visit www.cctmark.gov.uk
Re: [squid-users] Fatal: Received Segment Violation ....dying
On Mon, Aug 07, 2006, Mehmet, Levent (Accenture) wrote: Version 2.6.stable1 Upgrade to the latest squid-2.6 daily snapshot. Its fixed a number of these crashes. Adrian
Re: [squid-users] Fatal: Received Segment Violation ....dying
mån 2006-08-07 klockan 17:00 +0800 skrev Adrian Chadd: On Mon, Aug 07, 2006, Mehmet, Levent (Accenture) wrote: Version 2.6.stable1 Upgrade to the latest squid-2.6 daily snapshot. Its fixed a number of these crashes. 2.6.STABLE2 should be sufficient. The use of daily snapshot is in principle currently only needed if you use delay pools (quite broken in STABLE1 2). Regards Henrik signature.asc Description: Detta är en digitalt signerad meddelandedel
[squid-users] FATAL: Received Segment Violation...dying.
My squid box works fine for the last 2 months. But this morning, it's down. I got this piece in the cache.log: cache.log 2005/02/03 10:17:15| WARNING: Forwarding loop detected for: GET /images/web3_pic1.gif HTTP/1.0^M Accept: */*^M Referer: http://y.sina.com.cn/^M Accept-Language: zh-cn^M Accept-Encoding: gzip, deflate^M User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)^M Host: y.sina.com.cn^M Cookie: UNIPROINFO=sz:1024x768||dp:32||ac:Mozilla||an:Microsoft Internet Explorer||av:4.0 (compatible, MSIE 6.0, Windows NT 5.0)||cpu:x86||pf:Win32||jv:1.3||ct:lan||lg:zh-cn||tz:-8; UNIPROPATH=|*||pid:1-5-1-0-5753773|news.sina.com.cn/w/2005-02-03/05105027373s.shtml|st:0|et:1107396589437||hp:N|*|; UNIPROCT=71-0-0:5|1-4-5:1|62-1-1:1|42-4-3:1|42-0-0:1|31-5-9:2|31-7-8:1|1-6-4:1|1-6-3:1|1-4-2:1|59-68-4036:5|1-6-0:1|1-5-1:2; FINA_VISITED_S=sh01|é??¤??êy; VISITED_STOCK=sh igamex_cookie=1; sina_cookie_enable=yes; bbsviewtype=1^M Via: 1.1 GreenCache-2100.gforce.cn/6: (squid/2.5.STABLE7), 1.0 GreenCache-2100.gforce.cn/5: (squid/2.5.STABLE7)^M X-Forwarded-For: unknown, unknown^M Cache-Control: max-age=7776000, only-if-cached^M ^M 2005/02/03 10:19:15| storeAufsOpenDone: (2) No such file or directory 2005/02/03 10:19:15|/cache/0D/CC/000DCC1B 2005/02/03 10:19:37| storeAufsOpenDone: (2) No such file or directory 2005/02/03 10:19:37|/cache/05/7F/00057FB3 2005/02/03 10:19:37| storeAufsOpenDone: (2) No such file or directory 2005/02/03 10:19:37|/cache/05/7F/00057F4B 2005/02/03 10:19:37| storeAufsOpenDone: (2) No such file or directory 2005/02/03 10:19:37|/cache/05/83/000583B6 2005/02/03 10:19:37| storeAufsOpenDone: (2) No such file or directory 2005/02/03 10:19:37|/cache/05/7F/00057FA0 2005/02/03 10:20:22| storeAufsOpenDone: (2) No such file or directory 2005/02/03 10:20:22|/cache/01/BB/0001BBA1 2005/02/03 10:21:30| storeAufsOpenDone: (2) No such file or directory 2005/02/03 10:21:30|/cache/06/71/000671AF 2005/02/03 10:22:11| sslReadServer: FD 68: read failure: (104) Connection reset by peer 2005/02/03 10:23:01| storeAufsOpenDone: (2) No such file or directory 2005/02/03 10:23:01|/cache/08/DE/0008DE32 2005/02/03 10:25:33| storeAufsOpenDone: (2) No such file or directory 2005/02/03 10:25:33|/cache2/00/00/0020 (squid)[0x475781] /lib64/tls/libpthread.so.0[0x2a958d2fa0] (squid)[0x44f942] (squid)(__strtod_internal+0x7b8)[0x4041c0] (squid)[0x426e1a] (squid)[0x425582] (squid)[0x428c41] (squid)[0x4254eb] (squid)[0x429467] (squid)[0x42af06] (squid)[0x44ff4a] /lib64/tls/libc.so.6(__libc_start_main+0xee)[0x2a95eaf1ae] (squid)(regcomp+0x72)[0x403cea] FATAL: Received Segment Violation...dying. -- End -- When I type 'ps -A | grep squid', I can see the process is still there, and I can telnet the port squid serves, but I can't browse any web pages. Can somebody tell me what's the matter with it? -- System informatio - - AMD Opteron 248 * 2 - S2882 Thunder K8s Pro - RAM 1GB - 2 SCSI Seagate 10k for RAID-0 # uname -a Linux NGate 2.4.21-20.EL.NGate #2 SMP Mon Nov 8 13:26:37 CST 2004 i686 athlon i386 GNU/Linux # /usr/local/squid/sbin/squid -v Squid Cache: Version 2.5.STABLE7 configure options: --prefix=/usr/local/squid --with-aufs-threads=32 --with-pthreads --with-aio --with-dl --enable-storeio=ufs,aufs,diskd --enable-removal-policies=lru,heap --enable-kill-parent-hack --enable-snmp --enable-poll --disable-ident-lookups --disable-hostname-checks --enable-underscores --enable-stacktraces --enable-dl-malloc --enable-wccpv2 # cat /usr/local/squid/etc/squid.conf visible_hostname NGate.com hierarchy_stoplist cgi-bin ? acl QUERY urlpath_regex cgi-bin \? .cgi .pl .php .asp .cfm no_cache deny QUERY refresh_pattern ^ftp: 144020% 10080 refresh_pattern ^gopher:14400% 1440 refresh_pattern -i .gif 144090% 129600 reload-into-ims refresh_pattern -i .swf 144090% 129600 reload-into-ims refresh_pattern -i .jpg 144090% 129600 reload-into-ims refresh_pattern -i .bmp 144090% 129600 reload-into-ims refresh_pattern -i .pdf090% 129600 reload-into-ims refresh_pattern -i .zip090% 129600 reload-into-ims refresh_pattern -i .rar090% 129600 reload-into-ims refresh_pattern -i .exe090% 129600 reload-into-ims refresh_pattern . 120% 4320 acl all src 0.0.0.0/0.0.0.0 acl manager proto cache_object acl localhost src 127.0.0.1/255.255.255.255 acl to_localhost dst 127.0.0.0/8 acl SSL_ports port 443 acl Safe_ports port 80 acl CONNECT method CONNECT http_access allow manager localhost http_access allow CONNECT SSL_ports http_access deny !Safe_ports http_access deny to_localhost http_access allow all acl snmppublic snmp_community public snmp_access allow
RE: [squid-users] FATAL: Received Segment Violation...dying.
My squid box works fine for the last 2 months. But this morning, it's down. I got this piece in the cache.log: ... http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19 M.
Re: [squid-users] FATAL: Received Segment Violation...dying.
* Dave Inabinet ([EMAIL PROTECTED]): FreeBSD 4.10 Squid 2.5 Stable ports build Which portversion do you use? I could not reproduce this locally, using the port's current version 2.5.7_3 (-STABLE7 plus all applicable patches) on FreeBSD 4.10. I have blocked this site that is causing the proxy abuse message. When I try to browse this site - www.verschk.com - nothing comes up. Arin shows it somewhere in Canada. Fellow colleague thinks it is a spyware site. What kind of a URL could cause Squid to die like this? My cache_log: 2004/11/24 08:48:30| ipcacheParse: No Address records in response to 'entimg.msn.com' This is interesting, entimg.msn.com does resolve here: [EMAIL PROTECTED] [~] % dnsip entimg.msn.com 213.203.217.113 213.203.217.107 [EMAIL PROTECTED] [~] % dnsname `dnsip entimg.msn.com` akamai-deploy-05b.dus1.de.inetbone.net akamai-deploy-03b.dus1.de.inetbone.net 2004/11/24 08:48:55| httpSendRequestEntryDone: Likely proxy abuse detected '172.20.241.217' - 'http://www.verschk.com/list. asp' FATAL: Received Segment Violation...dying. A patch that I think was supposed to adressed this very problem was issued on June 8 against 2.5-STABLE5; it was integrated into the FreeBSD port in version 2.5.5_9. If you run an older version of the port, this might be the problem.
[squid-users] FATAL: Received Segment Violation...dying.
FreeBSD 4.10 Squid 2.5 Stable ports build I have blocked this site that is causing the proxy abuse message. When I try to browse this site - www.verschk.com - nothing comes up. Arin shows it somewhere in Canada. Fellow colleague thinks it is a spyware site. What kind of a URL could cause Squid to die like this? My cache_log: 2004/11/24 08:48:30| ipcacheParse: No Address records in response to 'entimg.msn.com' 2004/11/24 08:48:55| httpSendRequestEntryDone: Likely proxy abuse detected '172.20.241.217' - 'http://www.verschk.com/list. asp' FATAL: Received Segment Violation...dying. 2004/11/24 08:48:55| storeDirWriteCleanLogs: Starting... 2004/11/24 08:48:55| WARNING: Closing open FD 11 2004/11/24 08:48:55| 65536 entries written so far. 2004/11/24 08:48:56|131072 entries written so far. 2004/11/24 08:48:56|196608 entries written so far. 2004/11/24 08:48:56|262144 entries written so far. 2004/11/24 08:48:56|327680 entries written so far. 2004/11/24 08:48:56| Finished. Wrote 353141 entries. 2004/11/24 08:48:56| Took 0.6 seconds (570542.1 entries/sec). CPU Usage: 145.858 seconds = 62.189 user + 83.669 sys Maximum Resident Size: 242940 KB Page faults with physical i/o: 0 2004/11/24 08:49:23| Starting Squid Cache version 2.5.STABLE5 for i386-portbld-freebsd4.10... 2004/11/24 08:49:23| Process ID 1637 2004/11/24 08:49:23| With 11072 file descriptors available 2004/11/24 08:49:23| DNS Socket created at 0.0.0.0, port 3014, FD 4 2004/11/24 08:49:23| Adding nameserver 172.20.241.6 from /etc/resolv.conf 2004/11/24 08:49:23| Unlinkd pipe opened on FD 9 2004/11/24 08:49:23| Swap maxSize 8192000 KB, estimated 630153 objects 2004/11/24 08:49:23| Target number of buckets: 31507 2004/11/24 08:49:23| Using 32768 Store buckets 2004/11/24 08:49:23| Max Mem size: 262144 KB 2004/11/24 08:49:23| Max Swap size: 8192000 KB 2004/11/24 08:49:23| Rebuilding storage in /usr/local/squid/cache (CLEAN) 2004/11/24 08:49:23| Using Least Load store dir selection 2004/11/24 08:49:23| Current Directory is /usr/local/squid/logs 2004/11/24 08:49:23| Loaded Icons. 2004/11/24 08:49:23| Accepting HTTP connections at 0.0.0.0, port 3128, FD 11. 2004/11/24 08:49:23| Accepting ICP messages at 0.0.0.0, port 3130, FD 13. 2004/11/24 08:49:23| Accepting SNMP messages on port 3401, FD 14. 2004/11/24 08:49:23| WCCP Disabled. 2004/11/24 08:49:23| /var/log/squid.pid: (13) Permission denied 2004/11/24 08:49:23| WARNING: Could not write pid file 2004/11/24 08:49:23| Ready to serve requests. 2004/11/24 08:49:23| Store rebuilding is 1.2% complete 2004/11/24 08:49:27| Done reading /usr/local/squid/cache swaplog (353141 entries) 2004/11/24 08:49:27| Finished rebuilding storage from disk. 2004/11/24 08:49:27|353141 Entries scanned 2004/11/24 08:49:27| 0 Invalid entries. 2004/11/24 08:49:27| 0 With invalid flags. 2004/11/24 08:49:27|353106 Objects loaded. 2004/11/24 08:49:27| 0 Objects expired. 2004/11/24 08:49:27| 0 Objects cancelled. 2004/11/24 08:49:27|14 Duplicate URLs purged. 2004/11/24 08:49:27|21 Swapfile clashes avoided. 2004/11/24 08:49:27| Took 4.8 seconds (74002.4 objects/sec). 2004/11/24 08:49:27| Beginning Validation Procedure 2004/11/24 08:49:27|262144 Entries Validated so far. 2004/11/24 08:49:28| Completed Validation Procedure 2004/11/24 08:49:28| Validated 353106 Entries 2004/11/24 08:49:28| store_swap_size = 4635508k 2004/11/24 08:49:28| storeLateRelease: released 2 objects 2004/11/24 08:59:27| WARNING: 1 swapin MD5 mismatches 2004/11/24 09:01:42| sslReadServer: FD 38: read failure: (54) Connection reset by peer
RE: [squid-users] FATAL: Received Segment Violation...dying.
Squid 2.5 Stable ports build I have blocked this site that is causing the proxy abuse message. When I try to browse this site - www.verschk.com - nothing comes up. Arin shows it somewhere in Canada. Fellow colleague thinks it is a spyware site. What kind of a URL could cause Squid to die like this? ... No kind of url should be able to crash squid : upgrade to the latest stable release. Check again, then. M. _ Free mail? MSN Hotmail ! http://www.msn.be/hotmail
[squid-users] FATAL: Received Segment Violation...dying. 2.5.stable7
Hi Two days and two crash. First: 2004/10/20 13:31:14| NETDB state saved; 797 entries, 102 msec squid[0x80a6c19] /lib/libpthread.so.0[0x4013af54] /lib/libc.so.6[0x401b76b8] /lib/libc.so.6(__libc_free+0xa7)[0x401fcaa3] squid[0x80bc3fe] squid[0x8089b62] squid[0x8088bd9] squid[0x806182a] squid[0x8064fdc] squid[0x8066bab] squid[0x80677ef] squid[0x80882c5] /lib/libc.so.6(__libc_start_main+0xbb)[0x401a714f] squid(shmat+0x59)[0x804b631] FATAL: Received Segment Violation...dying. Second (debug_options ALL,2): 2004/10/21 19:01:24| The reply for HEAD http://v5.windowsupdate.microsoft.com/SelfUpdate/wuident.cab?0410211649 is ALLOWED, because it matched 'all' squid[0x80a6c19] /lib/libpthread.so.0[0x4013af54] /lib/libc.so.6[0x401b76b8] /lib/libc.so.6(__libc_free+0xa7)[0x401fcaa3] squid[0x80bc3fe] squid[0x8089b62] squid[0x8088bd9] squid[0x80617f3] squid[0x80a1f5c] squid[0x80a234c] squid[0x80a21e2] squid[0x80a2c6e] squid[0x80a0068] squid[0x807c015] squid[0x806772d] squid[0x80882c5] /lib/libc.so.6(__libc_start_main+0xbb)[0x401a714f] squid(shmat+0x59)[0x804b631] FATAL: Received Segment Violation...dying. # After dying process is still runing but not work (not proxing). # # ./squid -v Squid Cache: Version 2.5.STABLE7 configure options: --prefix=/usr/local/squid-2.5.STABLE7 --with-dl --enable-icmp --enable-storeio=aufs,diskd --enable-async-io --enable-snmp --enable-cachemgr-hostname=xxx.xx.xx --enable-htcp --enable-ssl --enable-forw-via-db --enable-cache-digests --enable-default-err-language=Polish --enable-linux-netfilter --disable-ident-lookups --enable-underscores --enable-stacktraces Can somebody help?
RE: [squid-users] FATAL: Received Segment Violation...dying. 2.5.stable7
Hi Two days and two crash. First: 2004/10/20 13:31:14| NETDB state saved; 797 entries, 102 msec squid[0x80a6c19] /lib/libpthread.so.0[0x4013af54] /lib/libc.so.6[0x401b76b8] /lib/libc.so.6(__libc_free+0xa7)[0x401fcaa3] squid[0x80bc3fe] squid[0x8089b62] squid[0x8088bd9] squid[0x806182a] squid[0x8064fdc] squid[0x8066bab] squid[0x80677ef] squid[0x80882c5] /lib/libc.so.6(__libc_start_main+0xbb)[0x401a714f] squid(shmat+0x59)[0x804b631] FATAL: Received Segment Violation...dying. Second (debug_options ALL,2): 2004/10/21 19:01:24| The reply for HEAD http://v5.windowsupdate.microsoft.com/SelfUpdate/wuident.cab?0410211649 is ALLOWED, because it matched 'all' squid[0x80a6c19] /lib/libpthread.so.0[0x4013af54] /lib/libc.so.6[0x401b76b8] /lib/libc.so.6(__libc_free+0xa7)[0x401fcaa3] squid[0x80bc3fe] squid[0x8089b62] squid[0x8088bd9] squid[0x80617f3] squid[0x80a1f5c] squid[0x80a234c] squid[0x80a21e2] squid[0x80a2c6e] squid[0x80a0068] squid[0x807c015] squid[0x806772d] squid[0x80882c5] /lib/libc.so.6(__libc_start_main+0xbb)[0x401a714f] squid(shmat+0x59)[0x804b631] FATAL: Received Segment Violation...dying. # After dying process is still runing but not work (not proxing). # # ./squid -v Squid Cache: Version 2.5.STABLE7 configure options: --prefix=/usr/local/squid-2.5.STABLE7 --with-dl --enable-icmp --enable-storeio=aufs,diskd --enable-async-io --enable-snmp --enable-cachemgr-hostname=xxx.xx.xx --enable-htcp --enable-ssl --enable-forw-via-db --enable-cache-digests --enable-default-err-language=Polish --enable-linux-netfilter --disable-ident-lookups --enable-underscores --enable-stacktraces Can somebody help? File a bug report. See FAQ guidelines for colitting bug reports. M. _ Do you know all the advantages of a credit card? http://money.msn.be/bcc
Re: [squid-users] FATAL: Received Segment Violation...dying. (SOLVED)
I get same error. Squid is 2.5.STABLE5 Compile options: --enable-gnuregex --enable-snmp --enable-linux-netfilter --enable-internal-dns --with-pthreads --enable-wccpv2 --disable-icmp --disable-wccp --disable-arp-acl --disable-ssl --disable-ident-lookups --disable-unlinkd (transparent proxy using wccpv2, linux-netfilter, etc.). Here is what I get: 2004/05/19 15:22:16| httpSendRequestEntryDone: Likely proxy abuse detected 'x.x.x.x' - 'http://activex.microsoft.com/objects/ocget.dll' FATAL: Received Segment Violation...dying. After this squid restarts. What can it be? Raymond A. Meijer wrote: On Fri 23 April 2004 22:31, Henrik Nordstrom wrote: I saw earlier in this thread that -O6 was used. Using any -O level above -O2 is generally not advisable as there very often lurks compiler bugs at those higher levels, and it is in addition not expected higher -O levels will give any better performance of Squid. Over the years there has been quite many reports about segmentation faults from people using too aggressive compiler optimizations, and it has most often been fixed by using a normal optimization level. I think that my problems were caused by the --enable-dlmalloc configure option (I had tried -O2 before). Last Friday I recompiled Squid this way: export CFLAGS=-s -DNUMTHREADS=24 ulimit -n 4096 ./configure --prefix=/opt/squid-2.5.STABLE5 --enable-linux-netfilter --enable-async-io=24 --enable-underscores '--enable-removal-policies=lru heap' make -j3 all make install and it's been working perfectly ever since. Thanks everybody for your suggestions! Ray
[squid-users] RE: [SPAM] - Re: [squid-users] FATAL: Received Segment Violation...dying. (SOLVED) - Bayesian Filter detected spam
There is a bug open for this in bugzilla http://www.squid-cache.org/bugs/show_bug.cgi?id=972 and a test patch against 2.5 stable5 that appears to fix the problem. I was experiencing the same problem several times a day across lots of servers. I have applied the patch and so far so good no crashes. Steve -Original Message- From: alex [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 19, 2004 7:05 AM To: squid-users Subject: [SPAM] - Re: [squid-users] FATAL: Received Segment Violation...dying. (SOLVED) - Bayesian Filter detected spam I get same error. Squid is 2.5.STABLE5 Compile options: --enable-gnuregex --enable-snmp --enable-linux-netfilter --enable-internal-dns --with-pthreads --enable-wccpv2 --disable-icmp --disable-wccp --disable-arp-acl --disable-ssl --disable-ident-lookups --disable-unlinkd (transparent proxy using wccpv2, linux-netfilter, etc.). Here is what I get: 2004/05/19 15:22:16| httpSendRequestEntryDone: Likely proxy abuse detected 'x.x.x.x' - 'http://activex.microsoft.com/objects/ocget.dll' FATAL: Received Segment Violation...dying. After this squid restarts. What can it be? Raymond A. Meijer wrote: On Fri 23 April 2004 22:31, Henrik Nordstrom wrote: I saw earlier in this thread that -O6 was used. Using any -O level above -O2 is generally not advisable as there very often lurks compiler bugs at those higher levels, and it is in addition not expected higher -O levels will give any better performance of Squid. Over the years there has been quite many reports about segmentation faults from people using too aggressive compiler optimizations, and it has most often been fixed by using a normal optimization level. I think that my problems were caused by the --enable-dlmalloc configure option (I had tried -O2 before). Last Friday I recompiled Squid this way: export CFLAGS=-s -DNUMTHREADS=24 ulimit -n 4096 ./configure --prefix=/opt/squid-2.5.STABLE5 --enable-linux-netfilter --enable-async-io=24 --enable-underscores '--enable-removal-policies=lru heap' make -j3 all make install and it's been working perfectly ever since. Thanks everybody for your suggestions! Ray
Re: [squid-users] FATAL: Received Segment Violation...dying. (SOLVED)
On Fri 23 April 2004 22:31, Henrik Nordstrom wrote: I saw earlier in this thread that -O6 was used. Using any -O level above -O2 is generally not advisable as there very often lurks compiler bugs at those higher levels, and it is in addition not expected higher -O levels will give any better performance of Squid. Over the years there has been quite many reports about segmentation faults from people using too aggressive compiler optimizations, and it has most often been fixed by using a normal optimization level. I think that my problems were caused by the --enable-dlmalloc configure option (I had tried -O2 before). Last Friday I recompiled Squid this way: export CFLAGS=-s -DNUMTHREADS=24 ulimit -n 4096 ./configure --prefix=/opt/squid-2.5.STABLE5 --enable-linux-netfilter --enable-async-io=24 --enable-underscores '--enable-removal-policies=lru heap' make -j3 all make install and it's been working perfectly ever since. Thanks everybody for your suggestions! Ray
[squid-users] FATAL: Received Segment Violation...dying.
Hello, I have a Dual PIII/866MHz Fedora Core 1 box with 1x9GB and 1x18GB SCSI disks for squid and 2.5GB memory. Only 50% of the disks is being used for the spool (formatted in ReiserFS 3.6). The other 50% of the disks is formatted in Ext3 (for performance testing), but not mounted at the moment. I've downloaded the sources for SQUID2.5.STABLE5 and compiled them with gcc-3.3.2-6 and glibc-2.3.2-101.4 and the following configure options: --prefix=/opt/squid-2.5.STABLE5 --enable-linux-netfilter --enable-async-io=24 --enable-dlmalloc --enable-underscores '--enable-removal-policies=lru heap' CFLAGS was -O6 -s -DNUMTHREADS=24 at compile time. The ip_wccp version being used is: ip_wccp.c,v 1.5 2004/02/17 01:55:05 Squid worked fine for about 1.5 hours, but suddenly it died with a Segment Violation. See the cache.log: 2004/04/23 11:51:29| Starting Squid Cache version 2.5.STABLE5 for i686-pc-linux-gnu... 2004/04/23 11:51:29| Process ID 4115 2004/04/23 11:51:29| With 4096 file descriptors available 2004/04/23 11:51:29| Performing DNS Tests... 2004/04/23 11:51:29| Successful DNS name lookup tests... 2004/04/23 11:51:29| DNS Socket created at 0.0.0.0, port 32776, FD 4 2004/04/23 11:51:29| Adding nameserver 62.1.1.92 from /etc/resolv.conf 2004/04/23 11:51:29| Adding nameserver 62.1.1.62 from /etc/resolv.conf 2004/04/23 11:51:29| Unlinkd pipe opened on FD 9 2004/04/23 11:51:29| Swap maxSize 2048 KB, estimated 1575384 objects 2004/04/23 11:51:29| Target number of buckets: 78769 2004/04/23 11:51:29| Using 131072 Store buckets 2004/04/23 11:51:29| Max Mem size: 8192 KB 2004/04/23 11:51:29| Max Swap size: 2048 KB 2004/04/23 11:51:29| Rebuilding storage in /opt/squid/var/cache/disk1 (CLEAN) 2004/04/23 11:51:29| Rebuilding storage in /opt/squid/var/cache/disk2 (CLEAN) 2004/04/23 11:51:29| Using Least Load store dir selection 2004/04/23 11:51:29| Set Current Directory to /opt/squid/var/cache 2004/04/23 11:51:29| Loaded Icons. 2004/04/23 11:51:29| Accepting HTTP connections at 0.0.0.0, port 3128, FD 12. 2004/04/23 11:51:29| Accepting WCCP messages on port 2048, FD 13. 2004/04/23 11:51:29| Ready to serve requests. 2004/04/23 11:51:30| Store rebuilding is 19.9% complete 2004/04/23 11:51:30| Done scanning /opt/squid/var/cache/disk2 swaplog (0 entries) 2004/04/23 11:51:30| Done reading /opt/squid/var/cache/disk1 swaplog (20571 entries) 2004/04/23 11:51:30| Finished rebuilding storage from disk. 2004/04/23 11:51:30| 20571 Entries scanned 2004/04/23 11:51:30| 0 Invalid entries. 2004/04/23 11:51:30| 0 With invalid flags. 2004/04/23 11:51:30| 20571 Objects loaded. 2004/04/23 11:51:30| 0 Objects expired. 2004/04/23 11:51:30| 0 Objects cancelled. 2004/04/23 11:51:30| 0 Duplicate URLs purged. 2004/04/23 11:51:30| 0 Swapfile clashes avoided. 2004/04/23 11:51:30| Took 1.0 seconds (20430.0 objects/sec). 2004/04/23 11:51:30| Beginning Validation Procedure 2004/04/23 11:51:30| Completed Validation Procedure 2004/04/23 11:51:30| Validated 20571 Entries 2004/04/23 11:51:30| store_swap_size = 279824k 2004/04/23 11:51:31| storeLateRelease: released 0 objects 2004/04/23 12:02:30| squidaio_queue_request: WARNING - Queue congestion 2004/04/23 12:54:13| squidaio_queue_request: WARNING - Queue congestion 2004/04/23 13:23:16| squidaio_queue_request: WARNING - Queue congestion 2004/04/23 13:27:55| CACHEMGR: [EMAIL PROTECTED] requesting 'info' FATAL: Received Segment Violation...dying. 2004/04/23 13:29:55| storeDirWriteCleanLogs: Starting... 2004/04/23 13:29:55| WARNING: Closing open FD 12 2004/04/23 13:29:56| 65536 entries written so far. 2004/04/23 13:29:56| Finished. Wrote 69628 entries. 2004/04/23 13:29:56| Took 0.1 seconds (649696.7 entries/sec). CPU Usage: 4228.510 seconds = 1153.910 user + 3074.600 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 418 Memory usage for squid via mallinfo(): total space in arena: 27308 KB Ordinary blocks:23302 KB 7935 blks Small blocks: 0 KB 0 blks Holding blocks: 1592 KB 3 blks Free Small blocks: 0 KB Free Ordinary blocks:4005 KB Total in use: 24894 KB 91% Total free: 4005 KB 15% 2004/04/23 13:29:59| Starting Squid Cache version 2.5.STABLE5 for i686-pc-linux-gnu... 2004/04/23 13:29:59| Process ID 6560 2004/04/23 13:29:59| With 4096 file descriptors available 2004/04/23 13:29:59| Performing DNS Tests... 2004/04/23 13:29:59| Successful DNS name lookup tests... 2004/04/23 13:29:59| DNS Socket created at 0.0.0.0, port 32777, FD 4 2004/04/23 13:29:59| Adding nameserver 62.1.1.92 from /etc/resolv.conf 2004/04/23 13:29:59| Adding nameserver 62.1.1.62 from /etc/resolv.conf 2004/04/23 13:29:59| Unlinkd pipe opened on FD 9 2004/04/23 13:29:59| Swap maxSize 2048 KB, estimated 1575384 objects 2004/04/23 13:29:59| Target number of buckets: 78769 2004/04/23 13:29:59| Using
RE: [squid-users] FATAL: Received Segment Violation...dying.
Hello, I have a Dual PIII/866MHz Fedora Core 1 box with 1x9GB and 1x18GB SCSI disks for squid and 2.5GB memory. Only 50% of the disks is being used for the spool (formatted in ReiserFS 3.6). The other 50% of the disks is formatted in Ext3 (for performance testing), but not mounted at the moment. I've downloaded the sources for SQUID2.5.STABLE5 and compiled them with gcc-3.3.2-6 and glibc-2.3.2-101.4 and the following configure options: --prefix=/opt/squid-2.5.STABLE5 --enable-linux-netfilter --enable-async-io=24 --enable-dlmalloc --enable-underscores '--enable-removal-policies=lru heap' CFLAGS was -O6 -s -DNUMTHREADS=24 at compile time. ... Any reasons for '--enable-dlmalloc' ? Suggesting to leave that away. Some for '-O6' in CFLAGS. Afterwards check whether your problem persists. M.
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Fri 23 April 2004 14:26, Elsen Marc wrote: I've downloaded the sources for SQUID2.5.STABLE5 and compiled them with gcc-3.3.2-6 and glibc-2.3.2-101.4 and the following configure options: --prefix=/opt/squid-2.5.STABLE5 --enable-linux-netfilter --enable-async-io=24 --enable-dlmalloc --enable-underscores '--enable-removal-policies=lru heap' CFLAGS was -O6 -s -DNUMTHREADS=24 at compile time. Any reasons for '--enable-dlmalloc' ? The only reason is that the previous version, squid-2.5.STABLE2, was configured that way (by someone else)... Suggesting to leave that away. Some for '-O6' in CFLAGS. Okay, it's recompiling now, without '--enable-dlmalloc' and '-O6'. Thanks so far, Ray
Re: [squid-users] FATAL: Received Segment Violation...dying.
Dear Raymond unfortunately as i was reading your mail my squid as died with same error :( . i was also running Squid-2.5-StABLE5 i downgrade to old tar source on system which was squid-2.5-Stable2 it is running ok after that . what was your cpu usage for squid ? Regards I have a Dual PIII/866MHz Fedora Core 1 box with 1x9GB and 1x18GB SCSI disks for squid and 2.5GB memory. Only 50% of the disks is being used for the spool (formatted in ReiserFS 3.6). The other 50% of the disks is formatted in Ext3 (for performance testing), but not mounted at the moment. I've downloaded the sources for SQUID2.5.STABLE5 and compiled them with gcc-3.3.2-6 and glibc-2.3.2-101.4 and the following configure options: --prefix=/opt/squid-2.5.STABLE5 --enable-linux-netfilter --enable-async-io=24 --enable-dlmalloc --enable-underscores '--enable-removal-policies=lru heap' CFLAGS was -O6 -s -DNUMTHREADS=24 at compile time. The ip_wccp version being used is: ip_wccp.c,v 1.5 2004/02/17 01:55:05 Squid worked fine for about 1.5 hours, but suddenly it died with a Segment Violation. See the cache.log: 2004/04/23 11:51:29| Starting Squid Cache version 2.5.STABLE5 for i686-pc-linux-gnu... 2004/04/23 11:51:29| Process ID 4115 2004/04/23 11:51:29| With 4096 file descriptors available 2004/04/23 11:51:29| Performing DNS Tests... 2004/04/23 11:51:29| Successful DNS name lookup tests... 2004/04/23 11:51:29| DNS Socket created at 0.0.0.0, port 32776, FD 4 2004/04/23 11:51:29| Adding nameserver 62.1.1.92 from /etc/resolv.conf 2004/04/23 11:51:29| Adding nameserver 62.1.1.62 from /etc/resolv.conf 2004/04/23 11:51:29| Unlinkd pipe opened on FD 9 2004/04/23 11:51:29| Swap maxSize 2048 KB, estimated 1575384 objects 2004/04/23 11:51:29| Target number of buckets: 78769 2004/04/23 11:51:29| Using 131072 Store buckets 2004/04/23 11:51:29| Max Mem size: 8192 KB 2004/04/23 11:51:29| Max Swap size: 2048 KB 2004/04/23 11:51:29| Rebuilding storage in /opt/squid/var/cache/disk1 (CLEAN) 2004/04/23 11:51:29| Rebuilding storage in /opt/squid/var/cache/disk2 (CLEAN) 2004/04/23 11:51:29| Using Least Load store dir selection 2004/04/23 11:51:29| Set Current Directory to /opt/squid/var/cache 2004/04/23 11:51:29| Loaded Icons. 2004/04/23 11:51:29| Accepting HTTP connections at 0.0.0.0, port 3128, FD 12. 2004/04/23 11:51:29| Accepting WCCP messages on port 2048, FD 13. 2004/04/23 11:51:29| Ready to serve requests. 2004/04/23 11:51:30| Store rebuilding is 19.9% complete 2004/04/23 11:51:30| Done scanning /opt/squid/var/cache/disk2 swaplog (0 entries) 2004/04/23 11:51:30| Done reading /opt/squid/var/cache/disk1 swaplog (20571 entries) 2004/04/23 11:51:30| Finished rebuilding storage from disk. 2004/04/23 11:51:30| 20571 Entries scanned 2004/04/23 11:51:30| 0 Invalid entries. 2004/04/23 11:51:30| 0 With invalid flags. 2004/04/23 11:51:30| 20571 Objects loaded. 2004/04/23 11:51:30| 0 Objects expired. 2004/04/23 11:51:30| 0 Objects cancelled. 2004/04/23 11:51:30| 0 Duplicate URLs purged. 2004/04/23 11:51:30| 0 Swapfile clashes avoided. 2004/04/23 11:51:30| Took 1.0 seconds (20430.0 objects/sec). 2004/04/23 11:51:30| Beginning Validation Procedure 2004/04/23 11:51:30| Completed Validation Procedure 2004/04/23 11:51:30| Validated 20571 Entries 2004/04/23 11:51:30| store_swap_size = 279824k 2004/04/23 11:51:31| storeLateRelease: released 0 objects 2004/04/23 12:02:30| squidaio_queue_request: WARNING - Queue congestion 2004/04/23 12:54:13| squidaio_queue_request: WARNING - Queue congestion 2004/04/23 13:23:16| squidaio_queue_request: WARNING - Queue congestion 2004/04/23 13:27:55| CACHEMGR: [EMAIL PROTECTED] requesting 'info' FATAL: Received Segment Violation...dying. 2004/04/23 13:29:55| storeDirWriteCleanLogs: Starting... 2004/04/23 13:29:55| WARNING: Closing open FD 12 2004/04/23 13:29:56| 65536 entries written so far. 2004/04/23 13:29:56| Finished. Wrote 69628 entries. 2004/04/23 13:29:56| Took 0.1 seconds (649696.7 entries/sec). CPU Usage: 4228.510 seconds = 1153.910 user + 3074.600 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 418 Memory usage for squid via mallinfo(): total space in arena: 27308 KB Ordinary blocks:23302 KB 7935 blks Small blocks: 0 KB 0 blks Holding blocks: 1592 KB 3 blks Free Small blocks: 0 KB Free Ordinary blocks:4005 KB Total in use: 24894 KB 91% Total free: 4005 KB 15% 2004/04/23 13:29:59| Starting Squid Cache version 2.5.STABLE5 for i686-pc-linux-gnu... 2004/04/23 13:29:59| Process ID 6560 2004/04/23 13:29:59| With 4096 file descriptors available 2004/04/23 13:29:59| Performing DNS Tests... 2004/04/23 13:29:59| Successful DNS name lookup tests... 2004/04/23
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Fri 23 April 2004 14:42, unixware wrote: Hi, unfortunately as i was reading your mail my squid as died with same error :( . i was also running Squid-2.5-StABLE5 Ouch.. i downgrade to old tar source on system which was squid-2.5-Stable2 it is running ok after that . Hmmm...interesting... what was your cpu usage for squid ? Not too much: CPU %user %nice %system %idle 12:00:00 PM all 7.49 0.00 21.39 71.12 12:10:00 PM all 11.25 0.00 30.75 58.00 12:20:00 PM all 10.98 0.00 29.57 59.45 12:30:00 PM all 9.83 0.00 27.07 63.10 12:40:00 PM all 10.11 0.00 27.42 62.48 12:50:00 PM all 10.91 0.00 29.66 59.43 01:00:00 PM all 9.53 0.00 26.63 63.84 01:10:00 PM all 9.80 0.00 28.16 62.05 01:20:00 PM all 8.40 0.00 23.73 67.86 01:30:00 PM all 9.39 0.00 26.61 64.00 01:40:00 PM all 8.81 0.00 26.11 65.08 01:50:00 PM all 10.22 0.00 28.84 60.94 02:00:00 PM all 9.47 0.00 26.74 63.79 02:10:00 PM all 9.13 0.00 26.84 64.03 02:20:00 PM all 9.15 0.00 26.18 64.68 02:30:00 PM all 10.20 0.00 26.81 62.99 02:40:00 PM all 13.90 0.00 27.14 58.97 What are your configure and compile options? What kind of machine is it running on? Ray
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Fri 23 April 2004 14:31, Raymond A. Meijer wrote: Okay, it's recompiling now, without '--enable-dlmalloc' and '-O6'. ...and running fine, so far: 2004/04/23 14:43:23| Starting Squid Cache version 2.5.STABLE5 for i686-pc-linux-gnu... 2004/04/23 14:43:23| Process ID 18192 2004/04/23 14:43:23| With 4096 file descriptors available 2004/04/23 14:43:23| Performing DNS Tests... 2004/04/23 14:43:23| Successful DNS name lookup tests... 2004/04/23 14:43:23| DNS Socket created at 0.0.0.0, port 32777, FD 4 2004/04/23 14:43:23| Adding nameserver 62.1.1.92 from /etc/resolv.conf 2004/04/23 14:43:23| Adding nameserver 62.1.1.62 from /etc/resolv.conf 2004/04/23 14:43:23| Unlinkd pipe opened on FD 9 2004/04/23 14:43:23| Swap maxSize 2048 KB, estimated 1575384 objects 2004/04/23 14:43:23| Target number of buckets: 78769 2004/04/23 14:43:23| Using 131072 Store buckets 2004/04/23 14:43:23| Max Mem size: 8192 KB 2004/04/23 14:43:23| Max Swap size: 2048 KB 2004/04/23 14:43:23| Rebuilding storage in /opt/squid/var/cache/disk1 (CLEAN) 2004/04/23 14:43:23| Rebuilding storage in /opt/squid/var/cache/disk2 (CLEAN) 2004/04/23 14:43:23| Using Least Load store dir selection 2004/04/23 14:43:23| Set Current Directory to /opt/squid/var/cache 2004/04/23 14:43:23| Loaded Icons. 2004/04/23 14:43:23| Accepting HTTP connections at 0.0.0.0, port 3128, FD 12. 2004/04/23 14:43:23| Accepting WCCP messages on port 2048, FD 13. 2004/04/23 14:43:23| Ready to serve requests. 2004/04/23 14:43:23| Store rebuilding is 3.8% complete 2004/04/23 14:43:23| Done scanning /opt/squid/var/cache/disk2 swaplog (0 entries) 2004/04/23 14:43:26| Done reading /opt/squid/var/cache/disk1 swaplog (108127 entries) 2004/04/23 14:43:26| Finished rebuilding storage from disk. 2004/04/23 14:43:26|108127 Entries scanned 2004/04/23 14:43:26| 0 Invalid entries. 2004/04/23 14:43:26| 0 With invalid flags. 2004/04/23 14:43:26|108127 Objects loaded. 2004/04/23 14:43:26| 0 Objects expired. 2004/04/23 14:43:26| 0 Objects cancelled. 2004/04/23 14:43:26| 0 Duplicate URLs purged. 2004/04/23 14:43:26| 0 Swapfile clashes avoided. 2004/04/23 14:43:26| Took 3.0 seconds (36442.6 objects/sec). 2004/04/23 14:43:26| Beginning Validation Procedure 2004/04/23 14:43:26| Completed Validation Procedure 2004/04/23 14:43:26| Validated 108127 Entries 2004/04/23 14:43:26| store_swap_size = 1507264k 2004/04/23 14:43:27| storeLateRelease: released 0 objects 14:48:20 up 4:49, 4 users, load average: 0.53, 0.56, 0.68 total used free sharedbuffers cached Mem: 25865721769192 817380 0 1081921455672 FilesystemType 1M-blocks Used Available Use% Mounted on /dev/sdc2 reiserfs 17366 1549 15817 9% /opt/squid/var/cache/disk1 /dev/sdb2 reiserfs868333 8651 1% /opt/squid/var/cache/disk2 procs memory swap io system cpu r b swpd free buff cache si sobibo incs us sy wa id 0 0 0 829916 107892 144526400 4 177 741 234 6 14 0 80 0 0 0 829280 107900 144588000 0 230 728 202 5 13 0 81 0 0 0 828604 107908 144647600 1 222 760 226 6 14 0 80 1 0 0 828608 107924 144644000 0 184 686 194 5 12 0 83 0 0 0 827956 107948 144703200 0 130 720 263 6 16 0 78 0 0 0 826884 107964 144785600 0 219 877 256 8 16 0 76 0 0 0 825940 107980 144846400 0 278 927 291 9 19 0 72 1 0 0 825184 108000 144914400 8 223 943 277 7 21 0 72 2 0 0 824464 108020 144981200 9 234 815 243 5 19 0 76 0 0 0 823776 108040 14504400010 237 750 271 6 14 0 80 0 0 0 823292 108048 145090000 2 163 845 303 7 18 0 76 1 0 0 822984 108064 145112800 2 310 1006 321 9 21 0 70 0 0 0 822396 108076 145170400 1 198 992 249 9 20 0 71 1 0 0 821812 108092 145220000 2 251 1148 260 10 23 0 68 0 0 0 821736 108100 145205200 7 247 1046 307 9 23 0 68 1 0 0 821192 108108 145233600 2 160 933 268 9 21 0 70 1 0 0 820412 108116 145300800 5 245 1081 286 11 24 0 65 2 0 0 820276 108124 145312000 3 180 786 234 6 18 0 75 0 0 0 819688 108144 145366000 4 194 934 280 7 24 0 69 0 0 0 819280 108148 145404400 3 186 811 248 6 18 0 76 0 0 0 818800 108160 145451200 8 216 756 226 6 17 0 77 1 0 0 818028 108180 145521200 0 142 757 211 6 15 0 79 0 0 0 817588 108192 145562000 0 213 821 214 6 19 0 75 1 0 0 816820 108212 145631200 2 146 809 215 7
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Fri, 23 Apr 2004, Raymond A. Meijer wrote: Squid worked fine for about 1.5 hours, but suddenly it died with a Segment Violation. Please file a bug report for this issue per the instructions in Squid FAQ 11.19 Sending in Squid bug reports url:http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19 A stack trace as described under crashes and core dumps is required for us to be able to process your report in an meaningful manner. Regards Henrik
Re: [squid-users] FATAL: Received Segment Violation...dying.
What are your configure and compile options? What kind of machine is it running on? Pentitum III 1200 Mhz Intel Entry Level Server Board 2 GB RAM 3 SCSI drive ( ReiserFS ) Redhat 7.3 linux kernel 2.4.25 gcc 2.96 CFLAGS -O3 -march=i686 -funroll-loops -fomit-frame-pointer squid compiled with async-io i also get this error when i was using Redhat 9 with default setting 2 weeks ago . Regards ./UW __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Fri 23 April 2004 15:07, Henrik Nordstrom wrote: Hi, Please file a bug report for this issue per the instructions in Squid FAQ 11.19 Sending in Squid bug reports url:http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19 A stack trace as described under crashes and core dumps is required for us to be able to process your report in an meaningful manner. If it happens again I will file a bug report. Thanks, Ray
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Fri, 23 Apr 2004, Raymond A. Meijer wrote: On Fri 23 April 2004 14:42, unixware wrote: Hi, unfortunately as i was reading your mail my squid as died with same error :( . i was also running Squid-2.5-StABLE5 Ouch.. i downgrade to old tar source on system which was squid-2.5-Stable2 it is running ok after that . Hmmm...interesting... What I know for sure is that there has been very many segmentation fault errors fixed since 2.5.STABLE2. See http://www.squid-cache.org/Versions/v2/2.5/bugs/ for a list of known bugs fixed after the 2.5.STABLE2 release. I would suspect you will find three or four important ones making it questionable if downgrading to 2.5.STABLE2 is a viable solution. I saw earlier in this thread that -O6 was used. Using any -O level above -O2 is generally not advisable as there very often lurks compiler bugs at those higher levels, and it is in addition not expected higher -O levels will give any better performance of Squid. Over the years there has been quite many reports about segmentation faults from people using too aggressive compiler optimizations, and it has most often been fixed by using a normal optimization level. Regards Henrik
Re: [squid-users] FATAL: Received Segment Violation...dying.
I saw earlier in this thread that -O6 was used. Using any -O level above -O2 is generally not advisable as there very often lurks compiler bugs at those higher levels, and it is in addition not expected higher -O levels will give any better performance of Squid. Over the years there has been quite many reports about segmentation faults from people using too aggressive compiler optimizations, and it has most often been fixed by using a normal optimization level. Thanks for your reply and suggestions i am using these CFLAGS -O3 -march=i686 -funroll-loops -fomit-frame-pointer these really help me to come out of high cpu usage by squid. squid performance also more better now. Regards UW __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Fri, 2 Apr 2004, unixware wrote: a) How many requests/s? (5 min average) 65-90 req/sec Ok. A bit but fully in range for what your CPU should be capable of. b) How many open connections? (number of filedescriptors in use) 2500-3500 open connections Current File descriptor in use 2800 A little high, but only a little. We Provide and Interent Over Cable and Dialup Services at peak hours around 3800 cable modems and 600 dialup modem are on line . How man Mbit/s is your Squid server proxying? Pentitum III 1200 MHz Entry Level Server Ok. RAM 2 GB Ok. 3 SCSI Disk ( one for OS ) ( other for Cache ) Would probably do good with a third drive for cache. I would also make sure all log files including swap.state is on the OS drive, and no swap partition. i am not using more 8 GB for cache for each drive Ok. OS Redhat 9 ( Mode Transparent using WCCP ) Try downgrading to a standard Linux-2.4 kernel. File system Reierfs Ok. squid compiled with 16384 file descriptor Quite high.. Squid will perform better if your recompile with fewer filedescriptors, I would suggest 4096 or 6192. Note: Due to a glibc issue the number of filedescriptors must be eventy divideable by 32 or odd things may happen.. using AUFS Ok. Is switching other OS like FreeBSd helps ?? Maybe, maybe not. Both Linux and FreeBSD usually performs about the same, but your milage may vary depending on network driver quality etc.. Regards Henrik
Re: [squid-users] FATAL: Received Segment Violation...dying.
How man Mbit/s is your Squid server proxying? 20 Mbit/s ( 2 x 10 links . 2 squid boxes on each link ) I would also make sure all log files including swap.state is on the OS drive, and no swap partition. log files are on OS drive but swap.state is on cache drive . how i can shift it to OS drive )OS Redhat 9 ( Mode Transparent using WCCP ) Try downgrading to a standard Linux-2.4 kernel. Using Default Redhat 9 Kernel ( 2.4.20 ) with using wccp v.1 patch Quite high.. Squid will perform better if your recompile with fewer filedescriptors, I would suggest 4096 or 6192. Note: Due to a glibc issue the number of filedescriptors must be eventy divideable by 32 or odd things may happen.. OK i will lower FD to 4096 or 6192 Maybe, maybe not. Both Linux and FreeBSD usually performs about the same, but your milage may vary depending on network driver quality etc.. sometime i get very low throughput when testing squid at peak hour . and downloading speed keep on decreasing :( i hope squid-3 will stable soon so i can use epoll for efficient network i/o Thanks for your help Regards UW __ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Sat, 3 Apr 2004, unixware wrote: How man Mbit/s is your Squid server proxying? 20 Mbit/s ( 2 x 10 links . 2 squid boxes on each link ) So approx 10Mbit/s per Squid then? No other traffic on these links? I would also make sure all log files including swap.state is on the OS drive, and no swap partition. log files are on OS drive but swap.state is on cache drive . how i can shift it to OS drive See cache_swap_log. )OS Redhat 9 ( Mode Transparent using WCCP ) Try downgrading to a standard Linux-2.4 kernel. Using Default Redhat 9 Kernel ( 2.4.20 ) with using wccp v.1 patch Try downgrading to a standard Linux-2.4 kernel. sometime i get very low throughput when testing squid at peak hour . and downloading speed keep on decreasing :( Then look into the service times using cachemgr, and also monitor the results of vmstat 5. i hope squid-3 will stable soon so i can use epoll for efficient network i/o Don't hold your breath while waiting. Regards Henrik
Re: [squid-users] FATAL: Received Segment Violation...dying.
How man Mbit/s is your Squid server proxying? 20 Mbit/s ( 2 x 10 links . 2 squid boxes on each link ) So approx 10Mbit/s per Squid then? No other traffic on these links? These are Recieve only Satelite links used for web traffic only Try downgrading to a standard Linux-2.4 kernel. i will build standard kernel .RH 9 default kernel load many unnessary modules like usb-ohci usbcore . and device drivers are load as modules . i will try to build them statically in to kernel i think this aslo speed up access to device . improve overall performance. sometime i get very low throughput when testing squid at peak hour . and downloading speed keep on decreasing :( Then look into the service times using cachemgr, and also monitor the results of vmstat 5. i usually use free -m to see my machine not swaping too much Thanks too much for your valuable advice .no wards to thank you. Regards UW __ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Sat, 3 Apr 2004, unixware wrote: These are Recieve only Satelite links used for web traffic only Ok. Relatively high latency then I suppose.. has some impact on performance as more connections is needed for the same request rate. Try downgrading to a standard Linux-2.4 kernel. i will build standard kernel .RH 9 default kernel load many unnessary modules like usb-ohci usbcore . and device drivers are load as modules . i will try to build them statically in to kernel i think this aslo speed up access to device . improve overall performance. The problem is not so much the extra modules but the RH 9 kernel has had major brain surgery applied. What RH 9 calls 2.4 is closer to 2.6 than 2.4 but then again very different.. I have had very conflicting reports wrt Squid performance on the RH 9 kernels.. (some say it is OK, some say performace is much worse for Squid than standard kernels). Note: If/when you use a standard kernel it is higly recommended to run without swap. The standard kernel VM has some bad habits of pushing large applications like Squid out in swap only because there is disk I/O... i usually use free -m to see my machine not swaping too much This does not tell you how the machine behaves now, only what it has done.. vmstat gives much better output for determining what is going on right now. Regards Henrik
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Thu, 1 Apr 2004, unixware wrote: Dear all Squid stops suddenly with FATAL: Received Segment Violation...dying. i have 4 squid boxes running squid-2.5Stable4 most them of dying with same problem since yesterday . i aslo upgraded to squid-2.5-Stable5 but same problem Please file a bug report on this issue, with the information described in Squid FAQ 11.19 Sending in Squid bug reports url:http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19 Regards Henrik
Re: [squid-users] FATAL: Received Segment Violation...dying.
On 02.04 02:46, unixware wrote: i will definatly report Bug report Please Suggest How to lower my CPU usage CPU Usage, 5 minute avg: 97.75% CPU Usage, 60 minute avg: 98.27% half_opened_clients already off isnt't it just your machine overloaded? how many requests per second do you have? What's your CPU/memory/disk usage? -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. I intend to live forever - so far so good.
Re: [squid-users] FATAL: Received Segment Violation...dying.
On Fri, 2 Apr 2004, unixware wrote: i will definatly report Bug report Please Suggest How to lower my CPU usage CPU Usage, 5 minute avg: 97.75% CPU Usage, 60 minute avg: 98.27% half_opened_clients already off Some data a) How many requests/s? (5 min average) b) How many open connections? (number of filedescriptors in use) REgards Henrik
Re: [squid-users] FATAL: Received Segment Violation...dying.
a) How many requests/s? (5 min average) 65-90 req/sec b) How many open connections? (number of filedescriptors in use) 2500-3500 open connections Current File descriptor in use 2800 We Provide and Interent Over Cable and Dialup Services at peak hours around 3800 cable modems and 600 dialup modem are on line . we have 4 Squid boxes with following Specs Pentitum III 1200 MHz Entry Level Server RAM 2 GB 3 SCSI Disk ( one for OS ) ( other for Cache ) i am not using more 8 GB for cache for each drive OS Redhat 9 ( Mode Transparent using WCCP ) File system Reierfs squid compiled with 16384 file descriptor using AUFS Is switching other OS like FreeBSd helps ?? or Compiling linux kernel with specfic option aslo thinking adding other Scsi drive for cache i want to get maxium performance from my Hardware Your input will be very helpful .. Thanks and Regards UW __ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/
[squid-users] FATAL: Received Segment Violation...dying.
Dear all Squid stops suddenly with FATAL: Received Segment Violation...dying. i have 4 squid boxes running squid-2.5Stable4 most them of dying with same problem since yesterday . i aslo upgraded to squid-2.5-Stable5 but same problem Other thing i have notice squid is taking too much CPU like 99.2 % My Machines has following Spec Intel Entry Level Server motherboard Processor Pentitum III 1200 MHz RAM 2 GB 2 SCSI ( cache 8 GB each ) 1 SCSI ( OS Red HAT 9 ) Squid Compilation Option async-io Urgent help needed Thanks and Regards Here is some of output from cachemgr. Connection information for squid: Number of clients accessing cache: 3388 Number of HTTP requests received: 1135718 Number of ICP messages received:528268 Number of ICP messages sent:570112 Number of queued ICP replies: 0 Request failure ratio: 0.00 Average HTTP requests per minute since start: 4932.6 Average ICP messages per minute since start:4770.4 Select loop called: 2698115 times, 5.120 ms avg Resource usage for squid: UP Time:13814.818 seconds CPU Time: 13463.360 seconds CPU Usage: 97.46% CPU Usage, 5 minute avg:97.75% CPU Usage, 60 minute avg: 98.27% __ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/
Re: [squid-users] FATAL: Received Segment Violation...dying.
Squid stops suddenly with FATAL: Received Segment Violation...dying. i have 4 squid boxes running squid-2.5Stable4 most them of dying with same problem since yesterday . i aslo upgraded to squid-2.5-Stable5 but same problem Anyother messages on the cache.log. what is the configuration? Regards, Muthukumar.
[squid-users] FATAL: Received Segment Violation...dying.
Hi, Running Squid 2.5Stable2 on Redhat Linux 9.0. I got FATAL: Received Segment Violation...dying. squid does not accept any more connection. Check out FAQ; no info found. Iptables is running on the server. No idea if this is causing it. Thanks in advance! nooshin
Re: [squid-users] FATAL: Received Segment Violation...dying.
Nooshin, Try upgrade to STABLE4 it may solve your problem. I had similar problem with Squid-2.5-STABLE1 few weeks ago but an upgrade to STABLE4 solved the probelm, my Squid is running on Redhat 7.2. Good luck, Daniel Zand, Nooshin [EMAIL PROTECTED] 1/10/2003 5:32:52 Hi, Running Squid 2.5Stable2 on Redhat Linux 9.0. I got FATAL: Received Segment Violation...dying. squid does not accept any more connection. Check out FAQ; no info found. Iptables is running on the server. No idea if this is causing it. Thanks in advance! nooshin * This email message, including any attached files, is confidential and intended solely for the use of the individual or entity to whom it is addressed. The NSW Department of Commerce prohibits the right to publish, copy, distribute or disclose any information contained in this email, or its attachments, by any party other than the intended recipient. If you have received this email in error please notify the sender and delete it from your system. No employee or agent is authorised to conclude any binding agreement on behalf of the NSW Department of Commerce by email. The views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Department, except where the sender expressly, and with authority, states them to be the views of NSW Department of Commerce. The NSW Department of Commerce accepts no liability for any loss or damage arising from the use of this email and recommends that the recipient check this email and any attached files for the presence of viruses. *
RE: [squid-users] FATAL: Received Segment Violation...dying.
Are you using diskd? I start to see failure on open and unlink. No idea what is the cause of open and unlink failure. I assume might be related to ipcs parameters. Here is my diskd status 32247 1.2 0.0 2112 400 ?RSep30 3:19 diskd 33019904 33019905 33019906 Here is the data from cache manager sent_count: 2988824 recv_count: 2988820 max_away: 73 max_shmuse: 73 open_fail_queue_len: 3267 block_queue_len: 24206046 OPS SUCCESSFAIL open 480045 414203 65842 create 102643 102642 0 close 516928 516842 0 unlink 807573 409047 398526 read 700244 634402 0 write 381391 381389 0 Regards, nooshin -Original Message- From: Daniel Lim [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 5:13 PM To: Zand, Nooshin; [EMAIL PROTECTED] Subject: Re: [squid-users] FATAL: Received Segment Violation...dying. Nooshin, Try upgrade to STABLE4 it may solve your problem. I had similar problem with Squid-2.5-STABLE1 few weeks ago but an upgrade to STABLE4 solved the probelm, my Squid is running on Redhat 7.2. Good luck, Daniel Zand, Nooshin [EMAIL PROTECTED] 1/10/2003 5:32:52 Hi, Running Squid 2.5Stable2 on Redhat Linux 9.0. I got FATAL: Received Segment Violation...dying. squid does not accept any more connection. Check out FAQ; no info found. Iptables is running on the server. No idea if this is causing it. Thanks in advance! nooshin * This email message, including any attached files, is confidential and intended solely for the use of the individual or entity to whom it is addressed. The NSW Department of Commerce prohibits the right to publish, copy, distribute or disclose any information contained in this email, or its attachments, by any party other than the intended recipient. If you have received this email in error please notify the sender and delete it from your system. No employee or agent is authorised to conclude any binding agreement on behalf of the NSW Department of Commerce by email. The views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Department, except where the sender expressly, and with authority, states them to be the views of NSW Department of Commerce. The NSW Department of Commerce accepts no liability for any loss or damage arising from the use of this email and recommends that the recipient check this email and any attached files for the presence of viruses. *
RE: [squid-users] FATAL: Received Segment Violation...dying.
It has been stable and achieving satisfactory performance since we upgraded a week ago. I am not aware of any leak, it is in fact consuming less resources than before. On ave it is servicing about 20 HTTP reqs/sec. The Segment Violation I got prior to upgrade was discernible in processing an invalid clientReadRequest happening many times a day but the Squid was able to restart after dying. I don't know what that was but the upgrade solved the problem. Regards, Daniel Zand, Nooshin [EMAIL PROTECTED] 1/10/2003 10:19:39 Daniel, Thanks for suggestion. How stable is your squid on Linux. Have you notice any memory leak? How many requests per second does squid process. Thanks, nooshin -Original Message- From: Daniel Lim [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 5:13 PM To: Zand, Nooshin; [EMAIL PROTECTED] Subject: Re: [squid-users] FATAL: Received Segment Violation...dying. Nooshin, Try upgrade to STABLE4 it may solve your problem. I had similar problem with Squid-2.5-STABLE1 few weeks ago but an upgrade to STABLE4 solved the probelm, my Squid is running on Redhat 7.2. Good luck, Daniel Zand, Nooshin [EMAIL PROTECTED] 1/10/2003 5:32:52 Hi, Running Squid 2.5Stable2 on Redhat Linux 9.0. I got FATAL: Received Segment Violation...dying. squid does not accept any more connection. Check out FAQ; no info found. Iptables is running on the server. No idea if this is causing it. Thanks in advance! nooshin * This email message, including any attached files, is confidential and intended solely for the use of the individual or entity to whom it is addressed. The NSW Department of Commerce prohibits the right to publish, copy, distribute or disclose any information contained in this email, or its attachments, by any party other than the intended recipient. If you have received this email in error please notify the sender and delete it from your system. No employee or agent is authorised to conclude any binding agreement on behalf of the NSW Department of Commerce by email. The views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Department, except where the sender expressly, and with authority, states them to be the views of NSW Department of Commerce. The NSW Department of Commerce accepts no liability for any loss or damage arising from the use of this email and recommends that the recipient check this email and any attached files for the presence of viruses. * * This email message, including any attached files, is confidential and intended solely for the use of the individual or entity to whom it is addressed. The NSW Department of Commerce prohibits the right to publish, copy, distribute or disclose any information contained in this email, or its attachments, by any party other than the intended recipient. If you have received this email in error please notify the sender and delete it from your system. No employee or agent is authorised to conclude any binding agreement on behalf of the NSW Department of Commerce by email. The views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Department, except where the sender expressly, and with authority, states them to be the views of NSW Department of Commerce. The NSW Department of Commerce accepts no liability for any loss or damage arising from the use of this email and recommends that the recipient check this email and any attached files for the presence of viruses. *
RE: [squid-users] FATAL: Received Segment Violation...dying.
No diskd. Zand, Nooshin [EMAIL PROTECTED] 1/10/2003 11:08:02 Are you using diskd? I start to see failure on open and unlink. No idea what is the cause of open and unlink failure. I assume might be related to ipcs parameters. Here is my diskd status 32247 1.2 0.0 2112 400 ?RSep30 3:19 diskd 33019904 33019905 33019906 Here is the data from cache manager sent_count: 2988824 recv_count: 2988820 max_away: 73 max_shmuse: 73 open_fail_queue_len: 3267 block_queue_len: 24206046 OPS SUCCESSFAIL open 480045 414203 65842 create 102643 102642 0 close 516928 516842 0 unlink 807573 409047 398526 read 700244 634402 0 write 381391 381389 0 Regards, nooshin -Original Message- From: Daniel Lim [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 5:13 PM To: Zand, Nooshin; [EMAIL PROTECTED] Subject: Re: [squid-users] FATAL: Received Segment Violation...dying. Nooshin, Try upgrade to STABLE4 it may solve your problem. I had similar problem with Squid-2.5-STABLE1 few weeks ago but an upgrade to STABLE4 solved the probelm, my Squid is running on Redhat 7.2. Good luck, Daniel Zand, Nooshin [EMAIL PROTECTED] 1/10/2003 5:32:52 Hi, Running Squid 2.5Stable2 on Redhat Linux 9.0. I got FATAL: Received Segment Violation...dying. squid does not accept any more connection. Check out FAQ; no info found. Iptables is running on the server. No idea if this is causing it. Thanks in advance! nooshin * This email message, including any attached files, is confidential and intended solely for the use of the individual or entity to whom it is addressed. The NSW Department of Commerce prohibits the right to publish, copy, distribute or disclose any information contained in this email, or its attachments, by any party other than the intended recipient. If you have received this email in error please notify the sender and delete it from your system. No employee or agent is authorised to conclude any binding agreement on behalf of the NSW Department of Commerce by email. The views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Department, except where the sender expressly, and with authority, states them to be the views of NSW Department of Commerce. The NSW Department of Commerce accepts no liability for any loss or damage arising from the use of this email and recommends that the recipient check this email and any attached files for the presence of viruses. * * This email message, including any attached files, is confidential and intended solely for the use of the individual or entity to whom it is addressed. The NSW Department of Commerce prohibits the right to publish, copy, distribute or disclose any information contained in this email, or its attachments, by any party other than the intended recipient. If you have received this email in error please notify the sender and delete it from your system. No employee or agent is authorised to conclude any binding agreement on behalf of the NSW Department of Commerce by email. The views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Department, except where the sender expressly, and with authority, states them to be the views of NSW Department of Commerce. The NSW Department of Commerce accepts no liability for any loss or damage arising from the use of this email and recommends that the recipient check this email and any attached files for the presence of viruses. *
