--- On Wed, 7/16/08, Amos Jeffries <[EMAIL PROTECTED]> wrote:

> From: Amos Jeffries <[EMAIL PROTECTED]>
> Subject: Re: [squid-users] getting icp siblings to talk to each other --      
> squid/2.6.STABLE20
> To: [EMAIL PROTECTED]
> Cc: [email protected]
> Date: Wednesday, July 16, 2008, 8:32 PM
> > Hello Squid world,
> >
> > I can't get siblings to talk to each other.  Maybe
> there's some reason
> > that they don't need to that I'm missing?  Or
> I have it misconfigured.
> >
> >
> > I have two squid caches. host1 has 75GB cache and
> host2 has a 40GB cache.
> >
> > in host1 I have:
> >
> > cache_peer host2 sibling 8888 3130 proxy-only
> >
> > and on host2:
> >
> > cache_peer host1 sibling 8888 3130 proxy-only
> >
> >
> > I must be missing something obvious, the setup seems
> simple enough.
> >
> > Other settings in both:
> > acl local src 192.168.0.0/255.255.0.0
> 
> You can make that /16 for easier reading.
> 
> > icp_port 3130
> > icp_query_timeout 500
> > icp_access allow local
> > icp_access deny all
> >
> > I don't find anything in access_log i.e. grep
> CACHE_DIGEST_HIT access_log
> >
> > Any ideas?
> >
> 
> In order rough of relevance and easy checking...
> 
>  - It may be a SIBLING_HIT or ICP_HIT in the log.


Nothing like those in the logs either.


> 
>  - That the squid are actually listening for traffic on
> http_port 8888.


Yes, it's listening on that port.


> 
>  - Check that there is no firewall between them on port
> 3130.


Nope.  Although it may be something UDP related, just not sure what yet.
Are there any debugging flags to be enabled?
I did some sniffing and didn't see any UDP packets destined for port 3130.



> 
>  - check that forwarded_for and Via headers are turned ON
> (the defaults).


If they're defaults then they are on.


> 
>  - Maybe the timeout is too short. Try it at default
> (unset) first before
> tweaking.

I hadn't set the timeout, it was something I tried since it wasn't working at 
the default.


> 
> Amos


      

Reply via email to