[squid-users] assertion failed: Controller.cc:930: "EX"
Gaetano
gaedeb01 at gmail.com
Sun Nov 17 23:41:09 UTC 2024
Hi all,
We are running three squid proxy 5.5, on three different VMs, same
number of CPUs (4), same memory, and same FS type (xfs) on Alma Linux
9.
All servers are staged with Ansible and they all have the same squid.conf.
workers 4
...
cache_dir ufs /var/spool/squid 512 16 256
One of those servers (always the same) crashes with this assert:
kid1| assertion failed: Controller.cc:930: "EX"
kid can be from 1 to 4
everytime we enter a simple curl request to localhost proxy and proxy
to an OCSP responder.
Everything works fine when we remove workers as explained in an old
post about ufs and multithreading:
https://lists.squid-cache.org/pipermail/squid-users/2021-November/024285.html
However, why don't the other two proxies suffer from the same issue?
Removing /var/spool/squid/* (+ squid -z) makes things work for a
little while, then again Empty response from the server (=> assertion
failed: Controller.cc:930: "EX").
So somehow it seems related to the cache and/or the response.
Any ideas that could help to understand the problem?
Thank you!
More information about the squid-users
mailing list