Fedora Users — Re: What happened to SSH?

ame error on mine. SSH is starting. The first line is it starting and binding to port 22 on ::. Since it already has started, the second line where it tries to bind again to port 22 on 0.0.0.0 fails. The reason is that IPv6 and IPv4 are both enabled. SSH starts and binds on port 22 to all available IPv6 IPs (::). Then, it also tries to bind to all IPv4 IPs (0.0.0.0) in case IPv6 is disabled, but the port is already bound. What I did to get rid of the error message was

On 11/14/06, Ashley M. Kirchner <ashley@xxxxxxxxxx> wrote:

    Something happened after the last openssh update.  Now every time
ssh is (re)started, I get this message in my syslog:

Nov 14 08:16:57 lansky sshd[1760]: Server listening on :: port 22.
Nov 14 08:16:57 lansky sshd[1760]: error: Bind to port 22 on 0.0.0.0
failed: Address already in use.

    That was after a server restart this morning (to boot up the new
2239 kernel).  The thing is, it does start up, it does run.  And I can
shut it down completely (service sshd stop) and I can verify that no ssh
process is running and that there's nothing listening on port 22 ('nmap
-sS localhost' and by actually trying to connect to port 22 with another
machine).  Yet when I tell it to start ssh again, it starts, but not
after complaining with the above message.

    Soooo, inquiring minds want to know.

--
W | It's not a bug - it's an undocumented feature.
  +--------------------------------------------------------------------
  Ashley M. Kirchner <mailto:ashley@xxxxxxxxxx >   .   303.442.6410 x130
  IT Director / SysAdmin / Websmith             .     800.441.3873 x130
  Photo Craft Imaging                       .     3550 Arapahoe Ave. #6
  http://www.pcraft.com ..... .  .    .       Boulder, CO 80303, U.S.A.

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list