Date:  Mon, 7 Dec 2009 17:58:20 +0000
From:  "Colin Jack" <colin (at mark) mainline.co.uk>
Subject:  [coba-e:16189] Re: Slow login
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <45DACA7BE1DEA245AF6C95E5B94E531B1C9EE50D86 (at mark) datastore.mainline.local>
In-Reply-To:  <200912071847.36354.bq (at mark) solarspeed.net>
References:  <45DACA7BE1DEA245AF6C95E5B94E531B1C9EE50D81 (at mark) datastore.mainline.local> <200912071847.36354.bq (at mark) solarspeed.net>
X-Mail-Count: 16189



-----Original Message-----
From: Michael Stauber [mailto:bq (at mark) solarspeed.net] 
Sent: 07 December 2009 17:48
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:16188] Re: Slow login

Hi Colin,

> slow to login ãà“ both on SSH and FTP.
>  
> Anybody able to give me a clue? It used to be almost instantaneous.

That typically indicates a DNS problem. Check if the nameservers in 
/etc/resolve.conf are all answering in due course. Maybe the first one doesn't 
answer and after a timeout the 2nd one kicks in. That then delays things.

Firewall could also play a role there - more so for FTP than SSH, though. If 
FTP logins are MUCH slower for FTP than SSH, then it could be that you need to 
check your firewall to see if it has any provisions for letting FTP pass in 
both active/passive FTP mode. Most firewalls have such provisions.

-- 
With best regards,

Michael Stauber


Thanks Michael. I will check the DNS (although it was working fine).

Proftpd won't start now at all  ...

[root@server5 etc]# service proftpd start
Starting proftpd: server5.mainline.co.uk - fatal: Socket operation on non-socket
                                                           [FAILED]

If I change it from Inetd to standalone in proftpd.conf  it will start but nobody can login ... maybe the problems are linked?

Colin



Mainline company details are available at http://www.mainline.co.uk/disclosure.html