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 experience in Blue Coat proxies, but
these settings were preconfigured in their system.
>By your mention of "backend.conf" I assume you are trying to use
>something based on our example SMP CARP cluster configuration.
>If that is correct please compare what you have to the current example
>config <https://wiki.squid-cache.org/ConfigExamples/SmpCarpCluster>.
>It has had a few changes since initially written, and people
>copy-pasting it into tutorials without linking back to our info have got
>various bugs in their texts. Sometimes because they copied old versions
>that no longer work, or because they made arbitrary changes without
>properly understanding the consequences.
We followed that example, but it was last edited at 2013-03-23 04:15, so it
has a mixture of AUFS and Rock caches, that's why I missunderstood the
/cache${process_number} with the cache modes.
As you say, there's a lot of info into the tutorials released on the web,
but it's difficult to find the information updated with the most updated
version of Squid.
Maybe it will be worth an update of this example, it would save you some
time not having to reply to people that missunderstood that info.
>So the fix is to:
>
>1) stop Squid.
>
>2) make sure it is fully shutdown with no residual instances or
>processes running.
>
>3) make sure the SMP /dev/shm sockets opened by Squid are fully gone.
>Delete manually if necessary.
>
>4) make sure the PID file is fully gone. Delete manually if necessary.
>
>5) erase everything in the /cache1 directory.
>
>5a) optionally: erase any other caches you may have.
> This will speed up the -z process, but only the cache showing errors
>actually needs to be fully clean to fix this error message.
>
>6) run "squid -z" manually and wait until it completes.
>
>7) start Squid.
The procedure worked perfectly.
But unfortunately, we faced other issues...
kid1| TCP connection to localhost/4003 failed
kid1| Detected DEAD Parent: backend-kid3
kid1| temporary disabling (Service Unavailable) digest from localhost
So, we changed the cache_peer definition from localhost to 127.0.0.1, as
suggested in https://wiki.squid-cache.org/Features/IPv6.
And that was all to make Squid running.
Your help is much appreciated.
Thanks!
Paco.
--
Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
