getnameinfo failed


sorry if this has been asked before, but i couldn't find any relating thread
within the last 600 posts in this group and not much articles via google
that offers a solution/explanation.

I know this issue hasn't occured in the past, but i'm not sure about the

while starting sshd my Suse 9.3, i get the folliowing error:
Mar 6 12:20:44 rex sshd[15113]: Server listening on :: port 9797.
Mar 6 12:20:44 rex sshd[15113]: error: Bind to port 9797 on failed:
Address already in use.

This always happens while restarting and i already heard about this issue
that one sometimes has to first stop and then start sshd to avoid this.
But sometimes, this occurs in the bootprocess, too.

And even if i start/stop it, it always says
Mar 6 19:35:56 rex sshd[6405]: error: getnameinfo failed
Mar 6 19:35:56 rex sshd[6405]: Server listening on :: port 9797

although sshd now works (properly?), so that i can login from remote.

So what does this getnameinfo failure mean? Something to do with ipv6?

[nf@rex ~]$ rpm -q openssh
[nf@rex ~]$ uname -a
Linux rex #1 Thu Feb 2 20:54:26 UTC 2006 i686 athlon
i386 GNU/Linux

StrictModes yes
RSAAuthentication yes
PermitRootLogin no
PermitEmptyPasswords no
IgnoreRhosts yes
RhostsRSAAuthentication no
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes
UsePAM yes
ChallengeResponseAuthentication no ### default war yes
PasswordAuthentication yes
Port #not port 22#
Protocol 2
#ListenAddress # tried uncommented, but it seems the default
lg niko
icq:# 129022192
Wie glücklich viele Menschen wären, wenn sie sich genauso wenig um die
Angelegenheiten anderer kümmern würden, wie um die eigenen (Georg Christoph

Relevant Pages

  • [kde-linux] Am I secured ? ( 2nd Hack attempt to my computer )
    ... unknown: 4 Time ... root: 3 Time ... SSHD Killed: 6 Time ... PermitRootLogin no ...
  • How did this happen?
    ... May 12 06:50:43 localhost sshd: Failed password for illegal user ... cgi from port 2265 ... Starting sshd: ...
  • Re: bypassing employers proxy to surf anonymously
    ... port 443, so it's harder to distinguish from an https server. ... through the remote sshd. ... You have an option to go with a managed service or an enterprise software. ...
  • Re: ssh under attack - sessions in accepted state hogging CPU
    ... I haven't tried this specific port knocking sequence but you could setup a knock where if a user attempts to connect to port 22 say 3 times it then opens up port 22 to that ip and allows them to connect to sshd. ... I'm working on getting sshguard+ipfw in place to deal with it, but in the meantime, my box is getting pegged because sshd is accepting some connections which are getting stuck in state and eating CPU. ...
  • RE: possible ssh hack
    ... What version of SSHD were you running, ... Apache and we can help you out. ... Subject: possible ssh hack ... port 4207 ...