<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>
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
errors with the same configuration, same users, same network (
replace binaries and keep same configuration )<br>
<br>
All production servers are installed in a virtual environment (
ESXI 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
impact with the stability. <br>
We encounter same errors on a 20 users proxy and the same way of a
5000 users proxy.<br>
<br>
<br>
1) Memory leak <br>
---------------------------------<br>
This was encounter on computer that handle more than 10Gb of
memory, squid eat more than 8Gb of memory.<br>
After eating all memory, squid is unable to load helpers and
freeze 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
parameter: <br>
Example we set 65535 filedescriptors but squidclient mgr:info
report 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
filedescriptors<br>
listening port: MyPortNameID1<br>
2021/11/11 17:10:29 kid1| WARNING! Your cache is running out of
filedescriptors<br>
listening port: MyPortNameID1<br>
2021/11/11 17:10:51 kid1| WARNING! Your cache is running out of
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
filedescriptors<br>
listening port: MyPortNameID1<br>
2021/11/11 17:13:19 kid1| WARNING! Your cache is running out of
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
surf.<br>
a just "squid -k reconfigure" fix the issue and the proxy return
to normal mode for several minutes and back again to
filedescriptors issues.<br>
<br>
There is no relationship between </font><font face="Arial"><font
face="Arial">filedescriptors issues and the number of clients.<br>
Sometimes the issue is discovered during the night when there is
no user that using the proxy ( just some robots like windows
update ) </font><br>
<br>
<br>
</font><br>
<font face="Arial"><font face="Arial"><br>
Is there something other we can investigate to help more
stability of the 5.x branch ?</font><br>
Regards<br>
<br>
</font>
</body>
</html>