"Robert Dahlem" writes:
>Hi,
>
>I'm running Squid 2.1.PATCH2 on Linux 2.0.35. I have only one parent peer defi
ned as
>
> cache_peer proxy.xxx.xxx.de parent 81 3130
>
>After a short while most requests run into the following message:
>
> Unable to forward this request at this time.
> This request could not be forwarded to the origin server or to
> any parent caches. The most likely cause for this error is that:
>
> The cache administrator does not allow this cache to make direct
> connections to origin servers, and
> All configured parent caches are currently unreachable.
>
>cachemgr.cgi (when asked for Peer Cache Statistics) shows:
>
> Parent : proxy.xxx.xxx.de/81/3130
> Flags :
> Address[0] : xxx.xxx.xxx.xxx
> Status : Down
> AVG RTT : 0 msec
> LAST QUERY : 5 seconds ago
> LAST REPLY : 45 seconds ago
> PINGS SENT : 91
> PINGS ACKED: 0 0%
> FETCHES : 80 0%
> IGNORED : 0 0%
> Histogram of PINGS ACKED:
> keep-alive ratio: 0%
>
>Initially I had not configured icp_query_timeout. Setting this to 10000 made t
he
>situation somewhat better, but after a while the error messages came back.
>
>The quick&dirty solution for me was to set
>
> cache_peer proxy.xxx.xxx.de parent 81 7
>
>imitating a non-ICP neighbor. Im quite sure it is an ICP neighbor (its a Netsc
ape Proxy):
>Requests are running good for a while with ICP port 3130 until - after some mi
nutes - the
>described problem comes up.
>
>What can I do to analyze the problem? Or should I configure something else?
>
>Thanks in advance!
See the "PINGS ACKED" line? You have not received ANY ICP replies from
this parent cache.
My guess would be there is a firewall or something between the two
machines which blocks UDP packets.
Duane W.
