Slow response -logs

[Troy McKinnon]

> Delays of about a minute traditionally mean you have a DNS resolution
> problem, possibly for localhost or for the server's 'real' hostname.
>
> Can you do
>
>   ping localhost

mail:~ # ping localhost
PING mail.myFooDomain.com (127.0.0.1) 56(84) bytes of data.
64 bytes from mail.myFooDomain.com (127.0.0.1): icmp_seq=1 ttl=64 time=0.027
ms
64 bytes from mail.myFooDomain.com (127.0.0.1): icmp_seq=2 ttl=64 time=0.018
ms
64 bytes from mail.myFooDomain.com (127.0.0.1): icmp_seq=3 ttl=64 time=0.017
ms
64 bytes from mail.myFooDomain.com (127.0.0.1): icmp_seq=4 ttl=64 time=0.015
ms
64 bytes from mail.myFooDomain.com (127.0.0.1): icmp_seq=5 ttl=64 time=0.016
ms
64 bytes from mail.myFooDomain.com (127.0.0.1): icmp_seq=6 ttl=64 time=0.015
ms

--- mail.myFooDomain.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5000ms
rtt min/avg/max/mdev = 0.015/0.018/0.027/0.004 ms



>
> and
>
>   ping `hostname`
>

same thing


> at a shell prompt on your server and get rapid results?  If DNS is the
> problem, you would see a big delay whle the system tries and fails to
> do the DNS lookups of localhost and the host name.
>
> As further confirmation, check that
>
>   telnet 127.0.0.1 1
>
> is quickly rejected, but
>
>   telnet localhost 1
>
> or
>
>   telnet `hostname` 1
>
> get delayed, and then rejected.  That would pretty much confirm it is
> a DNS-related issue.


All 3 are instant. I do not think it is dns necesarily. Appears to only
happen on mail related stuff.

>
> Jonathan
> --
> Jonathan Marsden       | Internet: jonathan at xc.org | Making electronic
> 1252 Judson Street  | Phone: +1 (909) 795-3877 | communications work
> Redlands, CA 92374     | Fax:   +1 (909) 795-0327 | reliably for Christian
> USA            | http://www.xc.org/jonathan | missions worldwide
>
>