Hey,
In order to understand the issue and it's sources there is a need for
more information.
What OS?
What version of squid?
run "squid -v" in the command line in order to get the basic information
about squid.
Also if you do have access to the cache-mgr interface the "server-list"
section should contain couple details about this specific sources of the
issue.
What is the level which the squid-B is not reachable? PING level? route
level? TCP level?
Eliezer
On 09/12/13 20:28, babajaga wrote:
I have a squid-A for my LAN, which forwards all http-traffic to a parent
squid-B using simple config:
......
cache_peer x.x.x.x parent yyyy 0 no-query no-digest no-netdb-exchange
......
never_direct allow all
But in case, the parent (squid-B) is not reachable, the clients accessing
squid-A simply hang,
and in cache.log for squid-A I see
TCP connection to x.x.x.x/yyy failed
What would be the simplest method to set up an automatic backup, either
another parent (preferred) OR just to have a direct connection from squid-A
?
In case of backup parent, it should ONLY be used in case squid-B fails.
