<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#464646" bgcolor="#FFFFFF">
<font face="Arial">Hi<br>
<br>
Max filedescriptors is defined in squid.conf.<br>
Yes, in some cases a c-icap was installed and the proxy became
more stable for a while. <br>
But Filedescriptors issue still unstable... I really did not know
why.<br>
<br>
<br>
Running Debian 11 is very difficult it is a very new OS and we
consider debian 10 as </font><font face="Arial"><font
face="Arial">currently </font>stable .<br>
Also the Squid 4 working very well on Debian 10 <br>
<br>
</font><br>
<div class="moz-cite-prefix">Le 11/11/2021 à 20:58, Flashdown a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:62a7784138282fa3665fc03b1815112c@data-core.org">Hi
David,
<br>
<br>
well I am curious, where did you set the max filedescriptors? Only
in the OS configuration? If so, you also need to define it in the
squid.conf as well ->
<a class="moz-txt-link-freetext" href="http://www.squid-cache.org/Versions/v5/cfgman/max_filedescriptors.html">http://www.squid-cache.org/Versions/v5/cfgman/max_filedescriptors.html</a>
<br>
<br>
Regarding the memory leak, do you use an adaption service such as
c-icap?
<br>
If so, what is the result of: ss -ant | grep CLOSE_WAIT | wc -l
<br>
<br>
May you should try to build Squid5 against Debian 11 to have the
latest version of any dependencies needed to see if the memory
leak is gone or not.
<br>
<br>
I run multiple Squid 5.2 servers on Debian 11 in production and do
not have any issues.
<br>
---
<br>
Best regards,
<br>
Enrico Heine
<br>
<br>
Am 2021-11-11 20:08, schrieb David Touzeau:
<br>
<blockquote type="cite">Hi
<br>
<br>
Just for information and i hope it will help.
<br>
<br>
We have installed Squid 5.1 and Squid 5.2 in production mode.
<br>
It seems that after several days, the Squid become very
unstable.
<br>
We mention that when switching to 4.x we did not encounter these
<br>
errors with the same configuration, same users, same network (
replace
<br>
binaries and keep same configuration )
<br>
<br>
All production servers are installed in a virtual environment (
ESXI
<br>
or Nutanix ) on Debian 10.x with about 4 to 8 vCPUs and 8GB of
memory.
<br>
and from 20 to 5000 users.
<br>
<br>
After severals tests we see that the number of users did not
have
<br>
impact with the stability.
<br>
We encounter same errors on a 20 users proxy and the same way of
a
<br>
5000 users proxy.
<br>
<br>
1) Memory leak
<br>
---------------------------------
<br>
This was encounter on computer that handle more than 10Gb of
memory,
<br>
squid eat more than 8Gb of memory.
<br>
After eating all memory, squid is unable to load helpers and
freeze
<br>
listen ports.
<br>
A restart service free the memory and fix the issue.
<br>
<br>
2) Max filedescriptors issues:
<br>
--------------------------------
<br>
This is a strange behavior that Squid did not accept defined
<br>
parameter:
<br>
Example we set 65535 filedescriptors but squidclient mgr:info
report
<br>
4096 and sometimes return back to 1024.
<br>
<br>
Several times squid report
<br>
<br>
current master transaction: master15881
<br>
2021/11/11 17:10:09 kid1| WARNING! Your cache is running out of
<br>
filedescriptors
<br>
listening port: MyPortNameID1
<br>
2021/11/11 17:10:29 kid1| WARNING! Your cache is running out of
<br>
filedescriptors
<br>
listening port: MyPortNameID1
<br>
2021/11/11 17:10:51 kid1| WARNING! Your cache is running out of
<br>
filedescriptors
<br>
listening port: MyPortNameID1
<br>
2021/11/11 17:11:56 kid1| TCP connection to 127.0.0.1/2320
failed
<br>
current master transaction: master15881
<br>
2021/11/11 17:13:02 kid1| WARNING! Your cache is running out of
<br>
filedescriptors
<br>
listening port: MyPortNameID1
<br>
2021/11/11 17:13:19 kid1| WARNING! Your cache is running out of
<br>
filedescriptors
<br>
<br>
But a mgr:info report:
<br>
<br>
memPoolFree calls: 4295601
<br>
File descriptor usage for squid:
<br>
Maximum number of file descriptors: 10048
<br>
Largest file desc currently in use: 262
<br>
Number of file desc currently in use: 135
<br>
Files queued for open: 0
<br>
Available number of file descriptors: 9913
<br>
Reserved number of file descriptors: 9789
<br>
<br>
After these errors the listen port is freeze and nobody is able
to
<br>
surf.
<br>
a just "squid -k reconfigure" fix the issue and the proxy return
to
<br>
normal mode for several minutes and back again to
filedescriptors
<br>
issues.
<br>
<br>
There is no relationship between filedescriptors issues and the
number
<br>
of clients.
<br>
Sometimes the issue is discovered during the night when there is
no
<br>
user that using the proxy ( just some robots like windows update
)
<br>
<br>
Is there something other we can investigate to help more
stability of
<br>
the 5.x branch ?
<br>
Regards
<br>
_______________________________________________
<br>
squid-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a>
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>