Re: [squid-users] squid fails + incremental ping

Not a Squid question. Squid does not respond to pings, your OS network
layer does.

This is a well-known 'problem' in Red Hat versions 6.2 and 7.0, if you
don't have DNS configured correctly. Make sure your DNS servers are
working, and are setup correctly in resolv.conf. That will fix this
problem. A Red Hat system, by default, attempts to resolve every host
that contacts it...I think they consider this a security feature.

This can make several services very slow on Red Hat systems if name
lookups are timing out.

If you are not using Red Hat Linux version 6.2 or 7.0 (maybe 7.1 as
well), then I don't know what your problem might be. But taking the
question to the appropriate OS list is the next step for figuring out a
solution.

Van Bossche Koen wrote:

> Hi to you all,
>
> I have a weird problem between a local and parent squid. These are some
> facts :
> - squid fails from one day to the other (see incremental ping for more
> info), we rerouted the local towards an other parent without any problems
> - it has an incremental ping from local -> parent, not the other way around
> - the backup namely local2 has the same problem
> - all other locals towards the parent do not have any problem
> - I do not think it has anything to do with dns, it's the same on ip and on
> hostname
>
> These are my results of a ping :
> PING 138.249.118.131 (138.249.118.131) from 138.249.161.4 : 56(84) bytes of
> data.
> 64 bytes from 138.249.118.131: icmp_seq=0 ttl=249 time=120.9 ms
> 64 bytes from 138.249.118.131: icmp_seq=1 ttl=249 time=1261.9 ms

                                   --
                      Joe Cooper <joe@swelltech.com>
                  Affordable Web Caching Proxy Appliances
                         http://www.swelltech.com
Received on Tue Jul 03 2001 - 11:43:05 MDT