when the one of the proxies loses its internet connection.. the default route is gone. Not the route to the machine..
the 12.194 proxy then gives this message:
The following error was encountered while trying to retrieve the URL: http://www.tmz.com/
Connection to 54.230.36.213 failed.
The system returned: (101) Network is unreachable
The remote host or network may be down. Please try the request again.
12.194 can not get to 54.230.36.213 (tmz.com)..
I can still get to 12.194..
Squid is still running on 12.194, 12.194 has no gateway.. the Internet connection FROM 12.194 TO the outside is dead and gone.
That is what I am trying to fix..
When a cache_peer has a connectivity problem..
On Wed, Jun 22, 2016 at 12:46 AM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote:
You have a router misconfiguration somewhere. Probably ICMP is notOn 22/06/2016 7:12 a.m., B. Cook wrote:
> On Tue, Jun 21, 2016 at 3:18 AM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote:
>
>>
>> So you're trolling. The FAQ it is then:
>> <http://wiki.squid-cache.org/Features/CacheHierarchy>
>> <http://wiki.squid-cache.org/Features/LoadBalance>
>>
>>
> Thank you the response..
>
> squid.conf (3.5.19 debian host 192.168.10.115)
> cache_peer 10.20.12.144 parent 3128 0 no-digest no-netdb-exchange
> proxy-only
> cache_peer 10.20.12.194 parent 3128 0 no-digest no-netdb-exchange
> proxy-only
> cache_peer 10.20.32.99 parent 3128 0 no-digest no-netdb-exchange proxy-only
> default
> prefer_direct off
> nonhierarchical_direct off
>
> Turing off squid on host 10.20.12.144 immediately got 10.115 to pass
> connections over to 12.194 (great) as denoted in the logs below..
>
> 2016/06/21 15:02:16 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:16 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:24 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:24 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:24 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:24 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:24 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:24 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:24 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:24 kid1| TCP connection to 10.20.12.144/3128 failed
> 2016/06/21 15:02:24 kid1| Detected DEAD Parent: 10.20.12.144
> 2016/06/21 15:02:32 kid1| Detected REVIVED Parent: 10.20.12.144
>
> When I enabled squid on host 10.20.12.144 squid detected dead -> revived
> and passed traffic again.. (also great)..
>
> but when host 10.20.12.144 loses it's gateway, the default route on 12.144
> is dead.. traffic is still to 12.144.. squid didn't die, the process is
> still running..
>
> Nothing is detected and 12.194 is never contacted..
>
> How do I get squid to detect that no valid data is being returned from
> 12.144.. or am I missing something?
working on your network. Which is causing connnections to hang for long
periods instead of failing over to the other peer.
Attempts by Squid to contact 12.144 when there is no way to route
traffic to it should be getting an ICMP "no route to host" error back.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
If you can't explain it simply, you don't understand it well enough.
This message may contain confidential information and is intended only for the individual(s) named. If you are not an intended recipient you are not authorized to disseminate, distribute or copy this e-mail. Please notify the sender immediately if you have received this e-mail by mistake and delete this e-mail from your system.
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
