Hello Amos,
>If you have a mix of "/cache${process_number}" and "/cache1" in your
>config files you may still be mixing SMP-aware and SMP-disabled access
>to the "/cache1" path.
That's exactly what happened to us, as I mentioned, we are new in the
Squid's world. I have several years of experienc
On 24/11/18 3:21 am, pacolo wrote:
> Hello again,
>
> We have found an issue in backend.conf, as the Rock cache_dir is SMP aware.
>
> Change this...
> #cache_dir rock /cache${process_number} 2097152
> to this...
> cache_dir rock /cache1 2097152
>
>
> ... then the new errors are:
> Nov 23 14:55:
Hello again,
We have found an issue in backend.conf, as the Rock cache_dir is SMP aware.
Change this...
#cache_dir rock /cache${process_number} 2097152
to this...
cache_dir rock /cache1 2097152
... then the new errors are:
Nov 23 14:55:28 px06 squid[12559]: ERROR: /cache1/rock communication cha
Hello people,
@Alex, thanks for your help, we took your advise and change the deployment
to SMP, some issues were solved, but others appeared :-(.
The config files are attached, in case anybody could help or to help others
with our same issues, as we have been searching several days and we didn't
On 11/8/18 8:46 AM, pacolo wrote:
> assertion failed: filemap.cc:50: "capacity_ <= (1 << 24)"
> I have noticed that this problem could be related to the maximum value of
> our cache_dir size, according to...
> https://bugs.squid-cache.org/show_bug.cgi?id=3566
As that bug discussion attempt
Hello,
I am having performance issues with a deployment of a farm of 5 servers
(CentOS Linux release 7.5.1804) with Squid 3.5.20-12.el7, that are used for
the internet access of a scholar community.
This is around 7 Gbps at peak hour, including 60% of HTTPS not processed at
the moment by Squid (we
