On Sat, 11 Dec 2004, Scott Phalen wrote:
> Squid1
> http_port 3128
> cache_peer carp1.mydomain.com parent 3128 0 carp-load-factor=0.4
> cache_peer carp2.mydomain.com parent 3128 0 carp-load-factor=0.6
Ok.
> Squid2 (carp1)
> http_port 3128
> icp_port 3130
> cache_peer carp2.mydomain.com sibling 3128 3130 proxy-only
> cache_peer 127.0.0.1 parent 8080 0 proxy-only (dansguardian hosts)
> cache_peer_access 127.0.0.1 allow dansguardian
> cache_peer_access 127.0.0.1 deny all
> always_direct allow all
This can't be your running configuration. With this configuration peers
won't be used at all as you are forcing all requests going direct via
always_direct. With this configuration access.log MUST say
DIRECT/xx.xx.xx.xx or cache hits only, never TIMEOUT_* or any peering
related tags as peers are excplicitly forbidden to be used.
Again, are you really really sure you are looking into the correct
squid.conf file on your Squid2 and Squid3 proxies? Perhaps you have more
than one copy..
> On squid2 and squid3 I am seeing the timeout_direct message in the
> access.log.
Nothing else?
You should focus on what Squid2 and Squid3 says when they forward the
requests to your Squid1.
> In the access.log on squid1 I am not seeing many references to the requests
> being sent to CARP/carp1.mydomain.com or CARP/carp2.mydomain.com either.
> Looks like they are all being sent "direct".
So how does they then end up in your two carp parents? You do not have any
clients using these from what I understand.
> In my test environment I saw
> most the requests going to "CARP/host.mydomain.com" except the domains I had
> configured to go always_direct.
>
> Snipet from access.log on squid1:
> 1102825620.299 105 199.86.18.23 TCP_MISS/200 298 GET
> http://wisapidata.weatherbug.com/WxAlertIsapi/WxAlertIsapi.dll? -
> DIRECT/69.25.38.101 text/plain
> 1102825620.400 0 carp1.mydomain.com TCP_DENIED/403 1474 GET
> http://wisapidata.weatherbug.com/WxAlertIsapi/WxAlertIsapi.dll? - NONE/-
> text/html
How did that request end up at carp1.mydomain.com, and what did it say
about how it forwarded the reqeust?
Regards
Henrik
Received on Sun Dec 12 2004 - 04:08:42 MST
This archive was generated by hypermail pre-2.1.9 : Sat Jan 01 2005 - 12:00:02 MST