<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<pre>>><i> Hi all.
</i>><i>>
</i>><i>> Squid has a strange behavior: suddenly, it stops writing the log files
</i>><i>> (access.log and cache.log) for about 30 seconds clients cannot access the
</i>><i>> cache. Because my proxy is using AD auth, I checked the link between them
</i>><i>> and is OK. During the time squid "is down", the number of
</i>><i>> ext_wbinfo_group_acl processes starts growing until Squid operates
</i>><i>> normally. My squid box has 4GB of RAM and enough disk space to store the
</i>><i>> cache.
</i>
>1. Which version of Squid?
Squid 3.4.8
> 2. What operating system / version is it running under?
Debian Jessie 8.7
> 3. How many clients access this proxy?
About 100
> 4. How many requests per {second|minute|hour} are you processing?
> 5. When you say "enough disk space to store the cache", what are the details?
50GB
> 6. 4Gbytes is not a great deal these days - how much is being used, and do you
have any swap (and is any of that being used)?
Squid uses about 50% of the physical memory. 8GB of swap.
> 7. How often does the above behaviour occur?
It happens randomly. Maybe twice, three times or maybe nothing happens.
> 8. Does it manifest itself immediately after starting Squid, or is there a
longer period where it works normally before this starts happening?
No. It happens randomly.
> 9. Does it seem to occur after any specific requests have gone through, or when
a specific request gets made?
No. It happens randomly. I couldn't find nothing relevant about the requests.
> 10. What does access_log tell you about the requests immediately before, and
during, the 30 second holdup?
Nothing. Squid continues responding all the requests normally.
This is the last request until it holdups:
<b>1503416750.346 386 192.168.0.2 TCP_REFRESH_UNMODIFIED/304 235 GET <a class="moz-txt-link-freetext" href="http://www.mysite.com">http://www.mysite.com</a> user HIER_DIRECT/www.mysite.com -</b>
This is the next request:
<b>1503416781.864 141376 </b><b><b>192.168.0.2 </b>TCP_MISS/200 5599 CONNECT play.google.com:443 user HIER_DIRECT/play.google.com -</b>
</pre>
<div class="moz-signature">-- <br>
<b>@verovan</b></div>
</body>
</html>