[squid-users] Enabling SIBLING causes TIMEOUT_DIRECT.

I seem to be stuck here, no-one on the list seems to be able to help me.
Is anyone using siblings successfully?

Regards
Rabie

-----Original Message-----
From: Rabie van der Merwe [mailto:Rvdmerwe@mhg.co.za]
Sent: 07 April 2003 10:18
To: 'squid-users@squid-cache.org'
Subject: RE: [squid-users] Enabling SIBLING causes TIMEOUT_DIRECT.

Has anyone everseen something like this?
Can I enable some form of debugging to try and track it, so far no-one
seems to be able to help me, and I don't want to put this into production
if there is a problem with my config, or Squid itself.

Regrads
Rabie van der Merwe

-----Original Message-----
From: Rabie van der Merwe [mailto:Rvdmerwe@mhg.co.za]
Sent: 05 April 2003 17:29
To: 'squid-users@squid-cache.org'
Subject: [squid-users] Enabling SIBLING causes TIMEOUT_DIRECT.

I have 2 squid gateways for the whole org running Squid 2.5 Stable 1
When I enble :

cache_peer sibling02.dmz sibling 80 3130 proxy-only

On sibling01 (I have changed the ACL's on both servers to allow access)
And:

cache_peer sibling01.dmz sibling 80 3130 proxy-only

On sibling02.

When I reconfigure squid, the sibling is seen in the cache.log, but
I start getting an excessive ammounts of TIMEOUT_DIRECT's in the access
logs on both server, and very little SIBILING entries.

Both servers are on the same lan segment, and some of the
TIMEOUT_DIRECT's
are to web servers that are on that same segment.

As soon as I remove the sibling entries, then TIMEOUT_DIRECT stops.

Any help would be appreceated.

Regards
Rabie van der Merwe
Received on Tue Apr 08 2003 - 01:47:34 MDT