topic Re: Red Hat Enterprise Linux 5.3 login time too long in Operating System - Linux

Red Hat Enterprise Linux 5.3 login time too long

WilliamSmith11 — Sat, 21 Nov 2009 00:21:12 GMT

Hi everybody
I have a Red Hat Enterprise Linux version 5.3 running on two Integrity machines.

After entering the root password the # prompt take almost 10 to 12 second to appear.
This only happen in one node, in the second node after entering the root password the # prompt come inmmediately.

Some idea , every thing is ok , just by single detail.

Regards

W.S

Re: Red Hat Enterprise Linux 5.3 login time too long

Steven Schweda — Sat, 21 Nov 2009 02:24:43 GMT

Login HOW? Serial port? Telnet? rsh? ssh?
...?

A Forum search for keywords like, say
slow telnet
(or whatever) might find many old threads on
similar complaints. One popular problem is a
(reverse) DNS look-up problem, where the
(Telnet, rsh, ssh, ...) server system has
trouble getting the name of the client host
from its IP address. It's also possible for
some operation in a shell start-up script
(~/.profile, or whatever) to take excessive
time for some reason.

Re: Red Hat Enterprise Linux 5.3 login time too long

WilliamSmith11 — Sat, 21 Nov 2009 03:59:14 GMT

ssh throught putty, or from other linux host node.

Re: Red Hat Enterprise Linux 5.3 login time too long

Steven Schweda — Sat, 21 Nov 2009 06:01:22 GMT

> ssh [...]

So, adding "-v" to the "ssh" command might
provide a clue as to where it's getting
stuck.

But it's pretty easy to try something like:
nslookup
on the server, which should reveal a DNS
problem if there is one.

Re: Red Hat Enterprise Linux 5.3 login time too long

dirk dierickx — Mon, 23 Nov 2009 09:39:51 GMT

any chance you have ipv6 enabled on the machine with the 'slow' login syndrome? please check and turn it off if you're not using it (probably not).

Re: Red Hat Enterprise Linux 5.3 login time too long

Steven E. Protter — Mon, 23 Nov 2009 15:48:13 GMT

Shalom,

1) Quick fix is to make sure the system can look itself up in /etc/hosts instead of waiting for DNS. This usually stops 50% of these issues.

SEP