Re: [squid-users] Define two cache_peer directives with same IP but different ports

-----Amos Jeffries <squid3_at_treenet.co.nz> schrieb: -----
An: squid-users_at_squid-cache.org
Von: Amos Jeffries <squid3_at_treenet.co.nz>
Datum: 14.07.2014 12:39
Betreff: Re: [squid-users] Define two cache_peer directives with same IP but different ports

> On 14/07/2014 10:32 p.m., Antony Stone wrote:
> On Monday 14 July 2014 at 12:21:19, Klaus Reithmaier wrote:
>
>> Hello,
>>
>> I  have two machines with each two squid processes. I want that every
>> process is querying the other three over htcp if it has a specified
>> element in its cache.
>>
>> So this is my setting:
>>
>> --------------------------------     --------------------------------
>>
>> | Proxyserver1: IP 192.168.1.1 |     | Proxyserver2: IP 192.168.1.2 |
>>
>> --------------------------------     --------------------------------
>>   | squid1: Port 8080 |                   | squid1: Port 8080 |
>>   | squid2: Port 8081 |                   | squid2: Port 8081 |
>>   ---------------------                   ---------------------
>>
>> This is the cache_peer configuration on Proxyserver1 process squid1:
>> -- START config --
>> cache_peer 192.168.1.1 sibling 8081 4828 proxy-only htcp
>> cache_peer 192.168.1.2 sibling 8080 4827 proxy-only htcp
>> cache_peer 192.168.1.2 sibling 8081 4828 proxy-only htcp
>> -- END config --
>>
>> It's obvious, that
>> cache_peer 192.168.1.2 sibling 8080 4827 proxy-only htcp and
>> cache_peer 192.168.1.2 sibling 8081 4828 proxy-only htcp
>> are different proxies, because they are using different ports. But squid
>> can't be started:
>>
>> FATAL: ERROR: cache_peer 192.168.1.2 specified twice
>> Squid Cache (Version 3.3.12): Terminated abnormally.
>>
>> How can I define two siblings on the same machine?
>
> Define the cache_peer name= option to a unique value for each cache_peer
> line. The default name is the IP/host parameter value.
>
> Amos

Thanks Amos, exactly what i searched for. Sorry overlooking this in the documentation...

Klaus

This e-mail contains confidential and/or privileged information from the Lindner Group. If you are not the intended recipient or have received this e-mail by fault, please notify the sender immediately and destroy this e-mail. Any unauthorized copying and/or distribution of this e-mail is strictly not allowed.

This e-mail contains confidential and/or privileged information from the Lindner Group. If you are not the intended recipient or have received this e-mail by fault, please notify the sender immediately and destroy this e-mail. Any unauthorized copying and/or distribution of this e-mail is strictly not allowed.
Received on Mon Jul 14 2014 - 11:09:01 MDT