Re: [squid-users] Go direct if parent dies

Henrik, thanks for your patience.

> Then your Squid is probably not happy about your parents for one reason
> or another. Usually this is seen on an incorrect ICP configuration.
> Try configuring the parents without ICP (no-query cache_peer option).

This is my cache_peer:

cache_peer localhost parent 9090 0 no-query

> Another possibility is if you have only tested by using the reload
> button.. the reload button asks Squid to bypass the cache which will
> also make it bypass parents..

I have tried loading the page in 'lynx' which has no own cache. Also I
restarted lynx and did not "reload". This is how the access.log looks
like when just using "prefer_direct off":

1045837362.582 116 129.25.30.74 TCP_MISS/200 4265 GET
http://www.porn.com/ username DIRECT/200.210.220.230 text/html

And this is how it looks like when also using the "never_direct":

1045837239.264 56 129.25.30.74 TCP_MISS/403 1992 GET
http://www.porn.com/ username ANY_PARENT/localhost text/html

This is what I get told in the cache.log when the parent goes down:

2003/02/21 15:25:38| The request GET http://www.porn.com/ is ALLOWED,
because it matched 'all'
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| TCP connection to localhost/9090 failed
2003/02/21 15:25:38| Detected DEAD Parent: localhost/9090/0

I pray that you have further ideas. I'm really stuck. :)

 Christoph

-- 
~
~
".signature" [Modified] 3 lines --100%--                3,41         All