Re: ssh problems...

[dichro-7158404@eris.rcpt.to (Mikolaj J. Habryn)]

>>>>> "LS" == Lonnie Sauter <sauter@math.ukans.edu> writes:

    LS> I did strace the sshd on the target host that does not work
    LS> correctly:

    LS> (61) # strace -p 15044 select(4, [3], NULL, NULL, NULL

    LS> It does not react when a ssh session is requested.

  Okay, this is useful. Next step is to work out what that socket is
doing. Look at /proc/15044/fd. It will give you something like this:

hypochondriac:/home/dichro# ls -l /proc/157/fd
total 0
lrwx------   1 root     root           64 Aug  9 10:35 0 -> /dev/null
lrwx------   1 root     root           64 Aug  9 10:35 1 -> /dev/null
lrwx------   1 root     root           64 Aug  9 10:35 2 -> /dev/null
lrwx------   1 root     root           64 Aug  9 10:35 3 -> socket:[104]
lrwx------   1 root     root           64 Aug  9 10:35 4 -> socket:[107]
hypochondriac:/home/dichro#

  Then, look socket 3 up in the tcp table.

hypochondriac:/home/dichro# egrep 104 /proc/net/tcp
  11: 00000000:0016 00000000:0000 0A 00000000:00000000 00:00000000 00000000     0        0 104
hypochondriac:/home/dichro# 

  Is it wildly different to this? Can you connect to other tcp ports
on the machine? How many processes are running? Does 'dmesg' show
anything interesting?

m.