[squid-users] Squid stops responding after 12 browser tabs opened

Francesco Chemolli gkinkie at gmail.com
Tue Mar 5 10:00:56 UTC 2024


Have you tried checking the number and status of open TCP connections
within squid?
You can check it by running netstat (as root) on either box, or by checking
with cache manager, if it's enabled and responding

On Tue, Mar 5, 2024 at 4:53 PM <nuit123 at earthlink.net> wrote:

> Squid 4.17 compiled on Debian 11
>
> Squid works, but, after 12 to 17 browser tabs are opened to any web site,
> subsequent tabs fail to load web site content. At the same time, telnet:80
> through Squid also fails. Yet, network traffic that bypasses Squid
> successfully communicates with the target web site.
>
> Ultimately, after about two minutes, unresponsive browser tabs usually
> finish loading web site content.
>
> Adjusting cache_mem makes no difference.
>
> This is remarked:
> #cache_dir ufs /var/spool/squid 100 16 256
> Tried to enable it, but squid -z fails with permission issues, so keeping
> cache_dir enabled breaks squid entirely.
>
> Any thoughts, please?
>
> With apologies if this violates etiquette (hey, I did
> --enable-http-violations!), this Squid server is taking on greater
> importance, and while it's infinitely fascinating, I recognize my limits,
> so
> I'm open to experienced help managing and maintaining it, and probably
> building a newer version. :-)
>
> Thanks!
>
>
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> https://lists.squid-cache.org/listinfo/squid-users
>


-- 
    Francesco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20240305/bbea4cd1/attachment.htm>


More information about the squid-users mailing list