Good news. My Squid process "failed" earlier than expected.
This is one of the first warning messages I see in the log when it happens:
WARNING! Your cache is running out of filedescriptors
# squidclient mgr:info | grep 'file descri'
Maximum number of file descriptors: 1024
Available number of f
From: Amos Jeffries
>
> cache_log is one of the Squid directives which require a unique file
> path+name per instance when running multiple instances.
I defined a unique name for this directive for each squid service (squid.conf
used by the failing caching
On 25/08/17 20:34, Vieri wrote:
From: Amos Jeffries
At ALL,9 that is a sign of major trouble. The log data is not going
where it should be. Please check your squid.conf that it is not sending
cache_log directive to /dev/null, a pipe or something.
I do not de
From: Amos Jeffries
>
> At ALL,9 that is a sign of major trouble. The log data is not going
> where it should be. Please check your squid.conf that it is not sending
> cache_log directive to /dev/null, a pipe or something.
I do not define cache_log, so it should
On 23/08/17 20:15, Vieri wrote:
Hi,
After a long time working correctly, Squid stops working all of a sudden.
No new requests/replies show up in the logs. Complete silence.
If I issue "squid -k reconfigure" I get this message in cache.log:
Set Current Directory to /var/cache/squid
If I set "d
Hi,
After a long time working correctly, Squid stops working all of a sudden.
No new requests/replies show up in the logs. Complete silence.
If I issue "squid -k reconfigure" I get this message in cache.log:
Set Current Directory to /var/cache/squid
If I set "debug_options rotate=1 ALL,9" and r
