Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-13 Thread Alex Rousskov
On 2025-03-13 07:49, Andrey K wrote: I implemented the A-example functionality and made PR: https://github.com/squid-cache/squid/pull/2023 Thank you. ButthemodifiedSquid projectis notbeingbuilt ongithub,althoughthere are noproblemsduringthe localbuilds. Alex, Amos and Francesco, could you

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-13 Thread Andrey K
Hello, > Quality pull requests welcome. I implemented the A-example functionality and made PR: https://github.com/squid-cache/squid/pull/2023 But the modified Squid project is not being built on github, although there are no problems during the local builds. Alex, Amos and Francesco, could you s

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-11 Thread Andrey K
Hello Alex, Thank you for sharing your thoughts. The A-example looks easier to implement and more reliable. Kind regards, Ankor. вт, 11 мар. 2025 г. в 17:12, Alex Rousskov : > On 2025-03-10 23:56, Andrey K wrote: > > > > Alex: FWIW, related future Squid improvements may include: > > >

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-11 Thread Alex Rousskov
On 2025-03-10 23:56, Andrey K wrote: > Alex: FWIW, related future Squid improvements may include: >  * Detecting such shared memory segments clashes; refusing to start. >  * Disabling shared memory use when caching is completely disabled. But ... segments may remain from the previous Squid

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-10 Thread Andrey K
Hello, > FWIW, related future Squid improvements may include: > * Detecting such shared memory segments clashes; refusing to start. > * Disabling shared memory use when caching is completely disabled. > Quality pull requests welcome. I looked at the source code and found the detection of th

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-07 Thread Andrey K
Hello Alex, Thanks for the analysis. Squid only allows alphanumeric characters in the service name, so it refuses to use the original service name in the -n option (-n squid.user.service). I added -n squiduser option to the ExecStart string of the second instance. Now it looks good: # the first i

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-07 Thread Alex Rousskov
On 2025-03-07 06:50, Andrey K wrote: Squid Cache: Version 6.13 Service Name: squid Squid Cache: Version 6.10 Service Name: squid # the first instance 1318 DEL ... 30205 /dev/shm/squid-cf__queues.shm 1318 DEL ... 30206 /dev/shm/squid-cf__readers.shm 1318 DEL ...

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-07 Thread Andrey K
Hello, Amos, Alex, thanks for the information! > What is your Squid version? The first one: squid -v Squid Cache: Version 6.13 Service Name: squid This binary uses OpenSSL 1.1.1k FIPS 25 Mar 2021. For legal restrictions on distribution see https://www.openssl.org/source/license.html configure

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-06 Thread Alex Rousskov
On 2025-03-06 08:59, Amos Jeffries wrote: On 6/03/25 19:17, Andrey K wrote: Hello, I have a similar configuration: two SMP squids running on the same OEL host. They were built with different configurations: with different installation path prefixes and different names of binary files: squid

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-06 Thread Amos Jeffries
On 6/03/25 19:17, Andrey K wrote: Hello, I have a similar configuration: two SMP squids running on the same OEL host. They were built with different configurations: with different installation path prefixes and different names of binary files: squid and squid.user and they listen to different

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-05 Thread Andrey K
Hello, I have a similar configuration: two SMP squids running on the same OEL host. They were built with different configurations: with different installation path prefixes and different names of binary files: squid and squid.user and they listen to different ports. They are launched from two dif

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-05 Thread Amos Jeffries
On 6/03/25 13:16, Lubos Uhliarik wrote: In the end, we discovered that a customer was running two Squid instances on the same machine—one SMP instance with 16 workers and one single-process ... The fix is simple—just specify a service name using the -n Squid parameter for one of the Squid

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-05 Thread Lubos Uhliarik
Hello Alex, Thanks for your reply! On Mon, Mar 3, 2025 at 3:44 PM Alex Rousskov < rouss...@measurement-factory.com> wrote: > On 2025-03-02 15:47, Lubos Uhliarik wrote: > > > > 2024/10/16 17:52:44 kid10| Adaptation support is off. > > 2024/10/16 17:52:44 kid10| assertion failed: Queue.cc:388: "EX

Re: [squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-03 Thread Alex Rousskov
On 2025-03-02 15:47, Lubos Uhliarik wrote: 2024/10/16 17:52:44 kid10| Adaptation support is off. 2024/10/16 17:52:44 kid10| assertion failed: Queue.cc:388: "EX" Squid v6 has a few changes that affect SMP startup and shutdown sequences. Since you have ruled out upgrading to a supported versio

[squid-users] assertion failed: Queue.cc:388: "EX"

2025-03-02 Thread Lubos Uhliarik
Hello everyone, We have recently experienced Squid crashes when running Squid in SMP mode with 16 workers (workers 16). While reviewing the Squid cache logs, I noticed that assertion failures sometimes occurred (usually during the shutdown process): 2024/10/16 17:52:44 kid10| Adaptation support i