Hey All,
Been working on rolling out HTCP cache_peer relationships within my
squid cluster, but I'm running into a 'small' issue. After starting
squid with the cache_peers configured to use htcp, squid sends quite a
few UDP packets to the siblings on the htcp port, however, it then marks
them as
Try increasing the ICP/HTCP response time. The auto timeout
detection doesn't work too well for me, and my peers are on the same switch.
mike
At 06:01 PM 10/11/2007, Tony Dodd wrote:
Hey All,
Been working on rolling out HTCP cache_peer relationships within my
squid cluster, but I'm running i
Thanks for the suggestion, Mike. I tried adding:
icp_query_timeout 5000
dead_peer_timeout 10 seconds
To my configs, but this just resulted in it taking longer for the
instance to mark the sibling as dead. I'm assuming, however, that
icp_query_timeout does absolutely nothing for htcp queries?
Tony Dodd wrote:
Hey All,
Been working on rolling out HTCP cache_peer relationships within my
squid cluster, but I'm running into a 'small' issue. After starting
squid with the cache_peers configured to use htcp, squid sends quite a
few UDP packets to the siblings on the htcp port, however, it
Chris Robertson wrote:
Tony Dodd wrote:
Hey All,
Been working on rolling out HTCP cache_peer relationships within my
squid cluster, but I'm running into a 'small' issue. After starting
squid with the cache_peers configured to use htcp, squid sends quite a
few UDP packets to the siblings on the
Tony Dodd wrote:
Chris Robertson wrote:
Tony Dodd wrote:
Hey All,
Been working on rolling out HTCP cache_peer relationships within my
squid cluster, but I'm running into a 'small' issue. After starting
squid with the cache_peers configured to use htcp, squid sends quite a
few UDP packets to t
On lör, 2007-10-13 at 02:00 +0100, Tony Dodd wrote:
> > http://www.squid-cache.org/Versions/v2/2.6/cfgman/htcp_access.html
> >
> > It's likely deny by default.
> >
> > Chris
>
> Christ! In all my googling, and reading through squid books, not one
> single page mentioned that. =/
>
> 2007/10/1
> On lör, 2007-10-13 at 02:00 +0100, Tony Dodd wrote:
>
>> > http://www.squid-cache.org/Versions/v2/2.6/cfgman/htcp_access.html
>> >
>> > It's likely deny by default.
>> >
>> > Chris
>>
>> Christ! In all my googling, and reading through squid books, not one
>> single page mentioned that. =/
>>
>>
On tis, 2007-10-16 at 16:32 +1300, Amos Jeffries wrote:
> I've looked at the code and I think this is caused as a side-effect of
> "DEFAULT_IF_NONE: deny all" (@src/cf.data.pre:715) denying the initial
> peer query (@src/htcp.cc:1236) when no other htcp_access are defined but
> a peer is htcp_on
Adding squid-dev since this is getting well into policy and development area.
> On tis, 2007-10-16 at 16:32 +1300, Amos Jeffries wrote:
>
>> I've looked at the code and I think this is caused as a side-effect of
>> "DEFAULT_IF_NONE: deny all" (@src/cf.data.pre:715) denying the initial
>> peer qu
On tis, 2007-10-16 at 17:27 +1300, Amos Jeffries wrote:
> > The default for all accesses (HTTP, ICP, HTCP, SNMP) is deny unless
> > allowed.
>
> precisely. Simply flagging a peer as htcp is not enough to turn it on. As
> now documented.
A requesting peer needs to be allowed by in
http_access
and
11 matches
Mail list logo
