Re: [squid-users] Squid as Acceleration Proxy in a Squid Cluster

tor 2007-05-10 klockan 10:11 +0200 skrev Marcel Alburg:

> But if i stop the local apache on a server and ask over the server the
> website - squid sad
>
> 2007/05/10 08:10:30| Detected DEAD Parent: 127.0.0.1
> 2007/05/10 08:10:30| TCP connection to 127.0.0.1/80 failed
>
> Thats ok
>
> but the result is this:
>
> The following error was encountered:
>
> * Unable to forward this request at this time.
>
> 2007/05/10 08:10:55| Failed to select source for 'http://www.xxx.tld'
> 2007/05/10 08:10:55| always_direct = 0
> 2007/05/10 08:10:55| never_direct = 0
> 2007/05/10 08:10:55| timedout = 0

For this to work well you need a fallback non-ICP parent relation to the
other.. siblings is only queried for the content they have already
cached.

You should also have a cache_peer_access rule preventing circular
forwarding in case both is having problems..

Someting like the following should work:

cache_peer the_apache parent ... no-query originserver default
cache_peer the_other_server parent ... no-query
cache_peer the_other_server sibling ... name=other_server_sibling
(note: no no-query on the sibling relation, only the parent relations)

acl from_other_server src the_other_server
cache_peer_access the_other_server deny from_other_server
cache_peer_access the_other_server_sibling deny from_other_server

The dual sibling & parent relation to the other server is needed so that
ICP only acts in sibling mode, but that it's still used as a parent if
the preferred web server is down.

Regards
Henrik