Re: [squid-users] Squid 3.4.2 workers dying then re-spawned ones don't process connections

On 01/23/2014 12:49 AM, Eliezer Croitoru wrote:
> Hey Will,
>
> About the 3.4.2, what OS are you using?
> Is it a self compiled version of squid?
> "squid -v" will give the basic idea of the squid configurations.

I'm using a self-compiled version on Debian 6 (64bit only at the moment).

configure options: '--build=x86_64-linux-gnu' '--prefix=/usr'
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man'
'--infodir=${prefix}/share/info' '--sysconfdir=/etc'
'--localstatedir=/var' '--libexecdir=${prefix}/lib/squid3'
'--disable-maintainer-mode' '--disable-dependency-tracking'
'--disable-silent-rules' '--srcdir=.' '--datadir=/usr/share/squid3'
'--sysconfdir=/etc/squid3' '--mandir=/usr/share/man' '--enable-inline'
'--disable-disk-io' '--disable-storeio' '--disable-removal-policies'
'--disable-icmp' '--disable-delay-pools' '--disable-esi'
'--disable-icap-client' '--disable-ecap' '--disable-wccp'
'--disable-wccpv2' '--disable-snmp' '--disable-eui' '--disable-htcp'
'--disable-ssl' '--disable-forw-via-db' '--disable-cache-digests'
'--disable-follow-x-forwarded-for' '--disable-ident-lookups'
'--enable-auth' '--enable-auth-basic=none' '--enable-auth-digest=file'
'--disable-auth-negotiate' '--disable-auth-ntlm'
'--enable-log-daemon-helpers=file' '--enable-external-acl-helpers=none'
'--disable-url-rewrite-helpers' '--disable-storeid-rewrite-helpers'
'--disable-zph-qos' '--disable-translation' '--disable-auto-locale'
'--with-swapdir=/var/spool/squid3' '--with-logdir=/var/log/squid3'
'--with-pidfile=/var/run/squid3.pid' '--with-filedescriptors=65536'
'--with-large-files' '--with-default-user=proxy'
'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fPIE -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -g
-Wall -O2' 'LDFLAGS=-fPIE -pie -Wl,-z,relro -Wl,-z,now'
'CPPFLAGS=-D_FORTIFY_SOURCE=2' 'CXXFLAGS=-g -O2 -fPIE -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -g -Wall -O2'

>
> In order to verify if there is or there isn't a limit of FD that is
> being reached there are couple tools that are available.
> One is the /proc/ FS which can show the number of FD that is being
> used by each and every one of the instances of squid.
> The other one is "lsof" which you can filter using a "grep" command or
> the internal options such as PID and\or SOCKETS.
> the ulimit command in couple variations can indicate the basic limits:
> ulimit -aH
> ulimit -aS

The server I just checked has about 906 FDs open, however, looking at
the limits it can have up to 65535 open. So that's probably not directly
the issue, unless there's a select call somewhere that's failing.

>
> Note that the squid cache-mgr interface has lots of information if
> available.
>
> Are you using cache_dir ?

I haven't looked much at the cache-mgr interface, I'll take a look at
that and see what it says. I am not using a cache_dir. In fact, no
caching is allowed at all:

cache deny all

--Will
Received on Thu Jan 23 2014 - 13:17:14 MST