[squid-users] Squid restarting when ssl_bump is enabled.
Greetings! I have a problem with enabling of ssl_bump on my proxy. When I'm trying to do it, only small amount of https requests succeeds, all others are failing and every fail causes squid restart. I tried to set debug_options ALL,9 in squid.conf and that's what i found in cache.log: 2013/05/16 12:13:30.863 kid1| client_side.cc(3501) getSslContextStart: Finding SSL certificate for vk.com in cache 2013/05/16 12:13:30.863 kid1| client_side.cc(3505) getSslContextStart: SSL certificate for vk.com have found in cache (squid-1)(_Z5deathi+0x4b)[0x8288b7b] /lib/libssl.so.1.0.0(ssl_set_cert_masks+0x3b)[0xb782d2fb] /lib/libssl.so.1.0.0(ssl_get_server_send_pkey+0x39)[0xb782d9e9] /lib/libssl.so.1.0.0(ssl_get_server_send_cert+0x1b)[0xb782dacb] /lib/libssl.so.1.0.0(SSL_get_certificate+0x38)[0xb782dfa8] (squid-1)(_ZN3Ssl24verifySslCertificateDateEP10ssl_ctx_st+0x30)[0x840b2b0] (squid-1)(_ZN13ConnStateData18getSslContextStartEv+0x95)[0x815e0b5] (squid-1)(_ZN13ConnStateData13switchToHttpsEPKc+0x1dc)[0x815ebbc] (squid-1)(_ZN14CommIoCbPtrFun4dialEv+0x35)[0x83159d5] (squid-1)(_ZN9AsyncCall4makeEv+0x3a5)[0x8302375] (squid-1)(_ZN14AsyncCallQueue8fireNextEv+0x1ee)[0x830656e] (squid-1)(_ZN14AsyncCallQueue4fireEv+0x30)[0x83067e0] (squid-1)(_ZN9EventLoop7runOnceEv+0xdd)[0x819fb2d] (squid-1)(_ZN9EventLoop3runEv+0x20)[0x819fd00] (squid-1)(_Z9SquidMainiPPc+0x11b0)[0x8219880] (squid-1)(main+0x23)[0x821a8f3] /lib/libc.so.6(__libc_start_main+0xf5)[0xb73870d5] (squid-1)[0x811caf1] FATAL: Received Segment Violation...dying. 2013/05/16 12:13:30.863 kid1| Closing HTTP port 192.168.0.252:3128 So, Squid crashes every time when trying to check previously generated certificate, while generating certificates goes fine. What i have: squid -v Squid Cache: Version 3.2.8 configure options: '--prefix=/usr' '--sysconfdir=/etc/squid' '--bindir=/usr/sbin' '--sbindir=/usr/sbin' '--localstatedir=/var' '--libexecdir=/usr/sbin' '--datadir=/usr/share/squid' '--mandir=/usr/share/man' '--libdir=/usr/lib' '--sharedstatedir=/var/squid' '--with-logdir=/var/log/squid' '--with-swapdir=/var/cache/squid' '--with-pidfile=/var/run/squid.pid' '--with-dl' '--with-large-files' '--enable-storeio' '--enable-disk-io=AIO,Blocking,DiskDaemon,DiskThreads' '--enable-removal-policies=heap,lru' '--enable-icmp' '--enable-delay-pools' '--enable-esi' '--enable-icap-client' '--enable-useragent-log' '--enable-referer-log' '--enable-kill-parent-hack' '--enable-arp-acl' '--enable-ssl' '--enable-forw-via-db' '--enable-cache-digests' '--enable-linux-netfilter' '--enable-underscores' '--enable-auth' '--enable-basic-auth-helpers=DB,LDAP,MSNT,NCSA,PAM,POP3,SASL,SMB,YP,getpwnam,multi-domain-NTLM,squid_radius_auth' '--enable-ntlm-auth-helpers=fakeauth,no_check,smb_lm' '--enable-negotiate-auth-helpers=squid_kerb_auth' '--enable-digest-auth-helpers=eDirectory,ldap,password' '--enable-external-acl-helpers=ip_user,ldap_group,session,unix_group,wbinfo_group' '--enable-ntlm-fail-open' '--enable-stacktraces' '--enable-x-accelerator-vary' '--with-default-user=squid' '--enable-ssl-crtd' '--disable-ipv6' --enable-ltdl-convenience openssl version OpenSSL 1.0.0k 5 Feb 2013 P.S. Sorry for my English if it's terrible.
Re: [squid-users] Squid Restarting
On 25/05/2012 7:54 p.m., Kamarudin Samsudin wrote: Hi Amos, I'm looking into this now. Could you guide me, how to get the two values in those FD form the core dump file. I did something... hope will give you clues. This is from Solaris. Sorry, I dont have much time any more. Will do what I can though. pflags core_mib01_01-19_04_2012 core 'core-19_04_2012' of 22938: (squid) -f /squid_dir/etc/squid.conf data model = _ILP32 flags = MSACCT|MSFORK /1:flags = 0 sigmask = 0xbefc,0x cursig = SIGABRT pstack core_mib01_01-19_04_2012 core 'core-19_04_2012' of 22938: (squid) -f /squid_dir/etc/squid.conf - lwp# 1 / thread# 1 feccc5f8 _lwp_kill (6, 0, fed34f98, fecabf18, , 6) + 8 fec4194c abort(23dd4e28, 1, 286790, eeb60, fed333d8, 0) + 110 000c2aa4 xassert (23b3b0, 23aca0, 1f0, 49, 1, 2) + c4 000d6d10 _ZN8FwdState12serverClosedEi (1f706cd0, e, 0, fed392a4, 3, 47c) + 48 They should show up in the parameters where xassert function parameters are listed. if not there then as local parameters to _ZN8FwdState12serverClosedEi (aka FwdState::serverClosed). GDB shows a good display format for these things if you have it available. I can't help with pstack sorry. Amos
RE: [squid-users] Squid Restarting
Hi Amos, I'm looking into this now. Could you guide me, how to get the two values in those FD form the core dump file. I did something... hope will give you clues. This is from Solaris. pflags core_mib01_01-19_04_2012 core 'core-19_04_2012' of 22938: (squid) -f /squid_dir/etc/squid.conf data model = _ILP32 flags = MSACCT|MSFORK /1:flags = 0 sigmask = 0xbefc,0x cursig = SIGABRT pstack core_mib01_01-19_04_2012 core 'core-19_04_2012' of 22938: (squid) -f /squid_dir/etc/squid.conf - lwp# 1 / thread# 1 feccc5f8 _lwp_kill (6, 0, fed34f98, fecabf18, , 6) + 8 fec4194c abort(23dd4e28, 1, 286790, eeb60, fed333d8, 0) + 110 000c2aa4 xassert (23b3b0, 23aca0, 1f0, 49, 1, 2) + c4 000d6d10 _ZN8FwdState12serverClosedEi (1f706cd0, e, 0, fed392a4, 3, 47c) + 48 0017cf1c _ZN17CommCloseCbPtrFun4dialEv (232a4ba4, 0, 2ea174, 1, 2ea178, 217384) + c 0016c178 _ZN9AsyncCall4makeEv (232a4b88, 3d28b8, , 2ea000, 1, 14) + 1b8 0016e5c4 _ZN14AsyncCallQueue8fireNextEv (47b828, 237800, 2ea174, 2ea178, 17a950, 232a4b88) + 1e4 0016e778 _ZN14AsyncCallQueue4fireEv (47b828, 1a20fd11, 6b061, 3000, 1, 3bf400) + 18 000cd680 _ZN9EventLoop13dispatchCallsEv (ffbffa50, ffbffa38, 1, 0, 81ca50, 15cae8) + c 000cd8a4 _ZN9EventLoop7runOnceEv (ffbffa50, ffbff9a0, 10, ffbffa38, 81ca50, ffbffa58) + 110 000cd990 _ZN9EventLoop3runEv (ffbffa50, ffbffa30, 246000, c0648, 0, 4835a0) + c 0011b934 _Z9SquidMainiPPc (3, ffbffc64, 288800, , ff312a00, fecb6144) + 8dc 0011bef0 main (3, ffbffc64, ffbffc74, 3f36b0, ff310140, 0) + 8 000833e4 _start (0, 0, 0, 0, 0, 0) + 5c Hope this will help. Thanks regards, --- Din -Original Message- From: Justin Lawler Sent: Friday, May 25, 2012 3:48 PM To: Kamarudin Samsudin Subject: FW: [squid-users] Squid Restarting FYI -Original Message- From: Amos Jeffries [mailto:squ...@treenet.co.nz] Sent: Monday, May 14, 2012 8:16 PM To: Justin Lawler Cc: squid-users@squid-cache.org Subject: Re: [squid-users] Squid Restarting On 14/05/2012 11:03 p.m., Justin Lawler wrote: Thanks Amos - we have heap dumps but unfortunately we could not share with the wider community as they're taken from a customer production environment. However, we can send on information taken from the heap dump - like output from pflags/pstack/etc. Would this be sufficient to investigate the issue? Private data should not be a problem. Initially we just need a backtrace from the dump to find which function calls led to it, and the two values in those FD. Amos Thanks and regards, Justin -Original Message- From: Amos Jeffries On 4/05/2012 9:59 p.m., Justin Lawler wrote: Hi, We're running squid 3.1.19 - and have seen it restarting from the logs, just after the below error: 2012/04/19 12:12:28| assertion failed: forward.cc:496: server_fd == fd 2012/04/19 12:12:59| Starting Squid Cache version 3.1.19 for sparc-sun-solaris2.10... Is this a known issue? any workaround? Seems to be new and a bit strange. Squid opens one connection to the server to fetch content sometime later a connection was closed, but not the one which was opened to begin with. Do you have a core dump or stack trace available to identify what the fd and server_fd values actually were during the crash? It's been in production for 6 weeks now, and have only seen it once, but we need to have an answer for the customer. We're worried it'll be more frequently as traffic goes up. Being the first report over a month after the release, it would seem to be very rare. Amos This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
RE: [squid-users] Squid Restarting
Thanks Amos - we have heap dumps but unfortunately we could not share with the wider community as they're taken from a customer production environment. However, we can send on information taken from the heap dump - like output from pflags/pstack/etc. Would this be sufficient to investigate the issue? Thanks and regards, Justin -Original Message- From: Amos Jeffries [mailto:squ...@treenet.co.nz] Sent: Sunday, May 06, 2012 7:16 AM To: squid-users@squid-cache.org Subject: Re: [squid-users] Squid Restarting On 4/05/2012 9:59 p.m., Justin Lawler wrote: Hi, We're running squid 3.1.19 - and have seen it restarting from the logs, just after the below error: 2012/04/19 12:12:28| assertion failed: forward.cc:496: server_fd == fd 2012/04/19 12:12:59| Starting Squid Cache version 3.1.19 for sparc-sun-solaris2.10... Is this a known issue? any workaround? Seems to be new and a bit strange. Squid opens one connection to the server to fetch content sometime later a connection was closed, but not the one which was opened to begin with. Do you have a core dump or stack trace available to identify what the fd and server_fd values actually were during the crash? It's been in production for 6 weeks now, and have only seen it once, but we need to have an answer for the customer. We're worried it'll be more frequently as traffic goes up. Being the first report over a month after the release, it would seem to be very rare. Amos This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
Re: [squid-users] Squid Restarting
On 14/05/2012 11:03 p.m., Justin Lawler wrote: Thanks Amos - we have heap dumps but unfortunately we could not share with the wider community as they're taken from a customer production environment. However, we can send on information taken from the heap dump - like output from pflags/pstack/etc. Would this be sufficient to investigate the issue? Private data should not be a problem. Initially we just need a backtrace from the dump to find which function calls led to it, and the two values in those FD. Amos Thanks and regards, Justin -Original Message- From: Amos Jeffries On 4/05/2012 9:59 p.m., Justin Lawler wrote: Hi, We're running squid 3.1.19 - and have seen it restarting from the logs, just after the below error: 2012/04/19 12:12:28| assertion failed: forward.cc:496: server_fd == fd 2012/04/19 12:12:59| Starting Squid Cache version 3.1.19 for sparc-sun-solaris2.10... Is this a known issue? any workaround? Seems to be new and a bit strange. Squid opens one connection to the server to fetch content sometime later a connection was closed, but not the one which was opened to begin with. Do you have a core dump or stack trace available to identify what the fd and server_fd values actually were during the crash? It's been in production for 6 weeks now, and have only seen it once, but we need to have an answer for the customer. We're worried it'll be more frequently as traffic goes up. Being the first report over a month after the release, it would seem to be very rare. Amos This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
Re: [squid-users] Squid Restarting
On 4/05/2012 9:59 p.m., Justin Lawler wrote: Hi, We're running squid 3.1.19 - and have seen it restarting from the logs, just after the below error: 2012/04/19 12:12:28| assertion failed: forward.cc:496: server_fd == fd 2012/04/19 12:12:59| Starting Squid Cache version 3.1.19 for sparc-sun-solaris2.10... Is this a known issue? any workaround? Seems to be new and a bit strange. Squid opens one connection to the server to fetch content sometime later a connection was closed, but not the one which was opened to begin with. Do you have a core dump or stack trace available to identify what the fd and server_fd values actually were during the crash? It's been in production for 6 weeks now, and have only seen it once, but we need to have an answer for the customer. We're worried it'll be more frequently as traffic goes up. Being the first report over a month after the release, it would seem to be very rare. Amos
[squid-users] Squid Restarting
Hi, We're running squid 3.1.19 - and have seen it restarting from the logs, just after the below error: 2012/04/19 12:12:28| assertion failed: forward.cc:496: server_fd == fd 2012/04/19 12:12:59| Starting Squid Cache version 3.1.19 for sparc-sun-solaris2.10... Is this a known issue? any workaround? It's been in production for 6 weeks now, and have only seen it once, but we need to have an answer for the customer. We're worried it'll be more frequently as traffic goes up. Thanks, Justin This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
[squid-users] Squid restarting
I have a web proxy solution (Squid + Dansguardian +75 Ntlm Helpers to authenticate in the AD) supporting 1500 users. In the last 3 days the squid started to Die (restart) with the following errors, about 4 times in the day. Resume Warning: all ntlmauthenticator process are busy. Consider increasing the number of ntlmauthenticator to at least 300 storeDirWriteCleanLogs: Starting ... Fatal: too many queued ntlmauthenticator requests (376 on 75) Squid cache : Terminated abnormaly 1 - I was using squid for 5 months and the problem started 3 days ago. Can a virus or trojan cause this problem?How could I detect it, my squid has 2 gb logs? Is there any tool or command (grep) that could help me? 2 - Am I using few authentication helpers for 1500 users? How many helpers should I use? 3 - Can the size of my logs cause this problem? Thanks!
Re: [squid-users] Squid restarting
I have a web proxy solution (Squid + Dansguardian +75 Ntlm Helpers to authenticate in the AD) supporting 1500 users. In the last 3 days the squid started to Die (restart) with the following errors, about 4 times in the day. Resume Warning: all ntlmauthenticator process are busy. Consider increasing the number of ntlmauthenticator to at least 300 storeDirWriteCleanLogs: Starting ... Fatal: too many queued ntlmauthenticator requests (376 on 75) Squid cache : Terminated abnormaly 1 - I was using squid for 5 months and the problem started 3 days ago. Can a virus or trojan cause this problem?How could I detect it, my squid has 2 gb logs? Is there any tool or command (grep) that could help me? - http://www.squid-cache.org/Scripts/ I use (like) calamaris - MRTG could be used to check traffic going through the SQUID box. - Check systems logs too , watchout for increase use of system resources such as swap, for instance due to increased load. M. 2 - Am I using few authentication helpers for 1500 users? How many helpers should I use? 3 - Can the size of my logs cause this problem? Thanks!
Re: [squid-users] Squid restarting
What is said in your system messages log? The messages from the OS are at the bottom, aren't very helpful though. ulimit -a , and ulimit -aH don't show any limit at 256MB. But by watching the mem usage through mrtg, I could clearly see the graphics hitting a ceiling at 256. Then, using an equiv. of top ,I could predict a crash to happen in the next few seconds. It might be this : (from http://www.ncsu.edu/itd/hpc/Documents/AIXMemoryModels.php) 32-bit Memory Models : AIX divides memory into 256 MB segments. The default memory model allocates a segment for kernel text and data associated with the user process, a segment for user text, a segment for user stack and data, a segment for shared library text, a segment for library data, and the remaining segments are available to use as shared memory segments. Since user stack and data share a 256 MB segment in this model, user data is restricted to 128 MB to allow room for the stack within the segment. and More info there : http://www-106.ibm.com/developerworks/eserver/articles/aix4java1.html#IDACDSKH Should I put it back to 8MB, or is 128 MB allright ? You should only make it larger than the default if you know for certain there is plenty of free memory and the process size is not in danger of hitting an OS limit. Well, I think I'll lower the value until I get to a stable situation. 128MB, then 64, etc ... Best Regards, Andrew. the LOGS : From syslog : Aug 20 11:00:35 srvuxrox squid[9390]: Squid Parent: child process 10924 exited d ue to signal 4 Aug 20 11:00:38 srvuxrox squid[9390]: Squid Parent: child process 19718 started From AIX Errorlog : LABEL: CORE_DUMP IDENTIFIER: B6048838 Date/Time: Fri Aug 20 11:00:35 2004 Sequence Number: 506 Machine Id: 004652BA4C00 Node Id: srvuxrox Class: S Type:PERM Resource Name: SYSPROC Description SOFTWARE PROGRAM ABNORMALLY TERMINATED Probable Causes SOFTWARE PROGRAM User Causes USER GENERATED SIGNAL Recommended Actions CORRECT THEN RETRY Failure Causes SOFTWARE PROGRAM Recommended Actions RERUN THE APPLICATION PROGRAM IF PROBLEM PERSISTS THEN DO THE FOLLOWING CONTACT APPROPRIATE SERVICE REPRESENTATIVE Detail Data SIGNAL NUMBER 4 USER'S PROCESS ID: 10924 FILE SYSTEM SERIAL NUMBER 5 INODE NUMBER 2 PROCESSOR ID 1 CORE FILE NAME /tmp/core PROGRAM NAME squid ADDITIONAL INFORMATION ?? ?? Impossible de g-E9-n-E9-rer une cha-EE-ne de sympt-F4-mes. ---
Re: [squid-users] Squid restarting
On Fri, 20 Aug 2004 [EMAIL PROTECTED] wrote: remaining segments are available to use as shared memory segments. Since user stack and data share a 256 MB segment in this model, user data is restricted to 128 MB to allow room for the stack within the segment. This puts a rather harsh limitation on how large your Squid can become.. Regards Henrik
Re: [squid-users] Squid restarting
remaining segments are available to use as shared memory segments. Since user stack and data share a 256 MB segment in this model, user data is restricted to 128 MB to allow room for the stack within the segment. This puts a rather harsh limitation on how large your Squid can become.. Regards Henrik That was for the default model , 2 other models are available : 32-bit Large Memory Model The large memory model is selected by specifing -bmaxdata:0xN000, where N may be 1-8. This allocates N memory segments for user data and also allows the user stack to completely occupy a segment. The maximum number of segments that can be used for user data is 8. 32-bit Very Large Memory Model The very large memory model is selected by specifing -bmaxdata:0xN000/DSA, where N may be 1-8. This allocates upto 8 memory segments for user data, but the segments are allocated dynamically. In AIX 5.2 the maximum number of segments increases to 10 with the stack having its own segment, or 13 if the stack segment is shared with shared library text and data. Under AIX 5.1 (current version running on p690) the limit is the same as for large memory model, 8. 64-bit Memory Model 64-bit memory model can address up to 1 Exabyte of memory. 256 MB memory segments are still used, but ~4,300,000,000 segments are available instead of 16. Segments are dynamically allocated within specified ranges for various uses. User data can occupy up to 448 Petabytes of memory. The 64-bit memory model is selected by specifing -q64. Best Regards, Andrew.
Re: [squid-users] Squid restarting
On Fri, 20 Aug 2004 [EMAIL PROTECTED] wrote: That was for the default model , 2 other models are available : 32-bit Large Memory Model The large memory model is selected by specifing -bmaxdata:0xN000, where N may be 1-8. This allocates N memory segments for user data and also allows the user stack to completely occupy a segment. The maximum number of segments that can be used for user data is 8. Looks reasonable. 32-bit Very Large Memory Model The very large memory model is selected by specifing -bmaxdata:0xN000/DSA, where N may be 1-8. This allocates upto 8 memory segments for user data, but the segments are allocated dynamically. In AIX 5.2 the maximum number of segments increases to 10 with the stack having its own segment, or 13 if the stack segment is shared with shared library text and data. Under AIX 5.1 (current version running on p690) the limit is the same as for large memory model, 8. Not much difference are there? Pick one. The whole segmenting business is confusing. Why should applications need to be built specifying these details? Why not simply have the kernel and dynamic linker decide based on OS set limits like all other OS:es? 64-bit Memory Model Overkill for Squid, and changes things a bit too much generally. Regards Henrik
[squid-users] Squid restarting
Hi there, It seems that I have a little trouble on our perfectly working squid installation (putting aside this topic). Here is the problem : squid restarts by itself 2 or 3 times a day. In fact, I have noticed that it restarts when it reaches it's cache_mem limit :256MB How can I avoid this ? I have 1GB RAM, 2 squid 2.5stable5 instances with cache_mem at 256 MB, on Aix5.2. cache_mem 256 MB cache_dir diskd /fs02/PRO/proxy1/cache 1024 22 256 Besides, I think the swap.state might be corrupted , and, the cache_dir is somewhat too small. But this isn't related. Or could it ? 2004/08/18 14:17:18| urlParse: Illegal hostname '.mail.lechti.com' 2004/08/18 14:30:44| Starting Squid Cache version 2.5.STABLE5 for powerpc-ibm-aix5.2.0.0... 2004/08/18 14:30:44| Process ID 20808 2004/08/18 14:30:44| With 8192 file descriptors available 2004/08/18 14:30:44| Performing DNS Tests... 2004/08/18 14:30:44| Successful DNS name lookup tests... 2004/08/18 14:30:44| DNS Socket created at 0.0.0.0, port 35984, FD 4 2004/08/18 14:30:44| Adding nameserver from /etc/resolv.conf 2004/08/18 14:30:44| helperOpenServers: Starting 10 'squid_ldap_auth' processes 2004/08/18 14:30:44| helperOpenServers: Starting 5 'squid_ldap_group' processes 2004/08/18 14:30:44| Unlinkd pipe opened on FD 25 2004/08/18 14:30:44| Swap maxSize 1048576 KB, estimated 80659 objects 2004/08/18 14:30:44| Target number of buckets: 4032 2004/08/18 14:30:44| Using 8192 Store buckets 2004/08/18 14:30:44| Max Mem size: 262144 KB 2004/08/18 14:30:44| Max Swap size: 1048576 KB 2004/08/18 14:30:44| Store logging disabled 2004/08/18 14:30:44| Rebuilding storage in /fs02/PRO/proxy1/cache (DIRTY) 2004/08/18 14:30:44| Using Least Load store dir selection 2004/08/18 14:30:44| Set Current Directory to /tmp 2004/08/18 14:30:44| Loaded Icons. 2004/08/18 14:30:45| Accepting HTTP connections at 0.0.0.0, port 1080, FD 26. 2004/08/18 14:30:45| Accepting SNMP messages on port 3410, FD 28. 2004/08/18 14:30:45| WCCP Disabled. 2004/08/18 14:30:45| Ready to serve requests. 2004/08/18 14:30:45| Store rebuilding is 1.2% complete 2004/08/18 14:30:52| WARNING: newer swaplog entry for dirno 0, fileno 0001C9AE 2004/08/18 14:30:52| WARNING: newer swaplog entry for dirno 0, fileno 3623 2004/08/18 14:30:52| WARNING: newer swaplog entry for dirno 0, fileno 526B # ls -l /tmp/core -rw-r- 1 squid1 squid 2687847 18 aoû 14:30 /tmp/core Best Regards , Andrew.
[squid-users] RE : [squid-users] Squid restarting
Hi quote What should be the recommended cache_mem? As I have 512MB ram in my system. The default (8 Mb) is good unless you have very specific reasons to change it. Regards Henrik /quote another one # TAG: cache_mem (bytes) # NOTE: THIS PARAMETER DOES NOT SPECIFY THE MAXIMUM PROCESS SIZE. # IT ONLY PLACES A LIMIT ON HOW MUCH ADDITIONAL MEMORY SQUID WILL # USE AS A MEMORY CACHE OF OBJECTS. SQUID USES MEMORY FOR OTHER # THINGS AS WELL. SEE THE SQUID FAQ SECTION 8 FOR DETAILS. 8.4 I set cache_mem to XX, but the process grows beyond that! The cache_mem parameter does NOT specify the maximum size of the process. It only specifies how much memory to use for caching ``hot'' (very popular) replies. Squid's actual memory usage is depends very strongly on your cache size (disk space) and your incoming request load. Reducing cache_mem will usually also reduce the process size, but not necessarily, and there are other ways to reduce Squid's memory usage (see below). Regards Kevin -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : jeudi 19 août 2004 12:09 À : [EMAIL PROTECTED] Objet : [squid-users] Squid restarting Hi there, It seems that I have a little trouble on our perfectly working squid installation (putting aside this topic). Here is the problem : squid restarts by itself 2 or 3 times a day. In fact, I have noticed that it restarts when it reaches it's cache_mem limit :256MB How can I avoid this ? I have 1GB RAM, 2 squid 2.5stable5 instances with cache_mem at 256 MB, on Aix5.2. cache_mem 256 MB cache_dir diskd /fs02/PRO/proxy1/cache 1024 22 256 Besides, I think the swap.state might be corrupted , and, the cache_dir is somewhat too small. But this isn't related. Or could it ? 2004/08/18 14:17:18| urlParse: Illegal hostname '.mail.lechti.com' 2004/08/18 14:30:44| Starting Squid Cache version 2.5.STABLE5 for powerpc-ibm-aix5.2.0.0... 2004/08/18 14:30:44| Process ID 20808 2004/08/18 14:30:44| With 8192 file descriptors available 2004/08/18 14:30:44| Performing DNS Tests... 2004/08/18 14:30:44| Successful DNS name lookup tests... 2004/08/18 14:30:44| DNS Socket created at 0.0.0.0, port 35984, FD 4 2004/08/18 14:30:44| Adding nameserver from /etc/resolv.conf 2004/08/18 14:30:44| helperOpenServers: Starting 10 'squid_ldap_auth' processes 2004/08/18 14:30:44| helperOpenServers: Starting 5 'squid_ldap_group' processes 2004/08/18 14:30:44| Unlinkd pipe opened on FD 25 2004/08/18 14:30:44| Swap maxSize 1048576 KB, estimated 80659 objects 2004/08/18 14:30:44| Target number of buckets: 4032 2004/08/18 14:30:44| Using 8192 Store buckets 2004/08/18 14:30:44| Max Mem size: 262144 KB 2004/08/18 14:30:44| Max Swap size: 1048576 KB 2004/08/18 14:30:44| Store logging disabled 2004/08/18 14:30:44| Rebuilding storage in /fs02/PRO/proxy1/cache (DIRTY) 2004/08/18 14:30:44| Using Least Load store dir selection 2004/08/18 14:30:44| Set Current Directory to /tmp 2004/08/18 14:30:44| Loaded Icons. 2004/08/18 14:30:45| Accepting HTTP connections at 0.0.0.0, port 1080, FD 26. 2004/08/18 14:30:45| Accepting SNMP messages on port 3410, FD 28. 2004/08/18 14:30:45| WCCP Disabled. 2004/08/18 14:30:45| Ready to serve requests. 2004/08/18 14:30:45| Store rebuilding is 1.2% complete 2004/08/18 14:30:52| WARNING: newer swaplog entry for dirno 0, fileno 0001C9AE 2004/08/18 14:30:52| WARNING: newer swaplog entry for dirno 0, fileno 3623 2004/08/18 14:30:52| WARNING: newer swaplog entry for dirno 0, fileno 526B # ls -l /tmp/core -rw-r- 1 squid1 squid 2687847 18 aoû 14:30 /tmp/core Best Regards , Andrew.
Re: [squid-users] Squid restarting
On Thu, 19 Aug 2004 [EMAIL PROTECTED] wrote: It seems that I have a little trouble on our perfectly working squid installation (putting aside this topic). Here is the problem : squid restarts by itself 2 or 3 times a day. In fact, I have noticed that it restarts when it reaches it's cache_mem limit :256MB Probably you run out of memory or the process grows larger than the max allowed process size in your OS. Is there any reason why you have set cache_mem this high? Mvh Henrik
Re: [squid-users] Squid restarting
By the time I went from DEV phase to PROD phase, my memory must have changed the meaning of the comments in squid.conf. I'm sorry. I thought it 'was' the max amount for hot objects. I had put 128MB on the developpement instance. the only reason I doubled it was to take the best out of the hardware. the larger the better ?. Should I put it back to 8MB, or is 128 MB allright ? I forgot to tell you that all these crashes are seamless to the users : processes restart on their own : is that because only child processes core dump, and then primary squid process respawns new ones ? Thank you, Andrew Quoting Henrik Nordstrom [EMAIL PROTECTED]: On Thu, 19 Aug 2004 [EMAIL PROTECTED] wrote: It seems that I have a little trouble on our perfectly working squid installation (putting aside this topic). Here is the problem : squid restarts by itself 2 or 3 times a day. In fact, I have noticed that it restarts when it reaches it's cache_mem limit :256MB Probably you run out of memory or the process grows larger than the max allowed process size in your OS. Is there any reason why you have set cache_mem this high? Mvh Henrik
Re: [squid-users] Squid restarting
On Thu, 19 Aug 2004 [EMAIL PROTECTED] wrote: By the time I went from DEV phase to PROD phase, my memory must have changed the meaning of the comments in squid.conf. I'm sorry. I thought it 'was' the max amount for hot objects. I had put 128MB on the developpement instance. the only reason I doubled it was to take the best out of the hardware. the larger the better ?. Should I put it back to 8MB, or is 128 MB allright ? You should only make it larger than the default if you know for certain there is plenty of free memory and the process size is not in danger of hitting an OS limit. I forgot to tell you that all these crashes are seamless to the users : processes restart on their own : is that because only child processes core dump, and then primary squid process respawns new ones ? It is because Squid automatically restarts itself on fatal errors. What is said in your system messages log? Regards Henrik
Re: [squid-users] Squid Restarting
i want to put a password to all my users before they logon to the internet F - Original Message - From: Henrik Nordstrom [EMAIL PROTECTED] To: atit jariwala [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, April 04, 2003 9:51 AM Subject: Re: [squid-users] Squid Restarting atit jariwala wrote: Hello Squid users, i am using squid 2.4 stable1 Then upgrade. Regards Henrik
[squid-users] Squid Restarting
Hello Squid users, i am using squid 2.4 stable1 I am getting following error message === ctx: enter level 0: 'http://www.dhl.com/html/art/del.gif' === assertion failed: refresh.c:163: age = 0 this is message i got in cache.log and after that squid restart automatically... can any one help me? == atit
Re: [squid-users] Squid Restarting
atit jariwala wrote: Hello Squid users, i am using squid 2.4 stable1 I am getting following error message === ctx: enter level 0: 'http://www.dhl.com/html/art/del.gif' === assertion failed: refresh.c:163: age = 0 this is message i got in cache.log and after that squid restart automatically... can any one help me? The funny thing is that this assertion crash has been reported before with dhl and squid 2.4 releases. We won't solve this before 11 o'clock in a fed-ex way probably :-) Anyway you are using a fairly old squid release. Please upgrade to the latest stable release, and see whether this problem keeps hunting you. M. == atit -- 'Love is truth without any future. (M.E. 1997)
