Bug 141119 - sshd failed to bind to 0.0.0.0 port 22
sshd failed to bind to 0.0.0.0 port 22
Status: CLOSED DUPLICATE of bug 120302
Product: Fedora
Classification: Fedora
Component: openssh (Show other bugs)
3
All Linux
medium Severity low
: ---
: ---
Assigned To: Tomas Mraz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-29 09:24 EST by feily
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-02-10 05:23:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description feily 2004-11-29 09:24:19 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
everytime openssh starts up I get the following error in my logwatch:

--------------------- SSHD Begin ------------------------ 

Failed to bind:
   0.0.0.0 port 22 (Address already in use) : 1 Time(s)

---------------------- SSHD End ------------------------- 

but sshd seems to work as expected. Cannot find any problem


Version-Release number of selected component (if applicable):
openssh-3.9p1-7

How reproducible:
Always

Steps to Reproduce:
1. start sshd with default settings
    

Expected Results:  this error should not be there

Additional info:

I've an eth0, an eth1 and an ppp0 interface set up
Comment 1 Michael Schwendt 2005-01-03 00:21:52 EST
Confirmed, but only if IPv6 kernel module is loaded (which is the
default). On "service sshd restart" I see the following in
/var/log/secure:

Jan  3 06:20:09 gw sshd[29213]: Server listening on :: port 22.
Jan  3 06:20:09 gw sshd[29213]: error: Bind to port 22 on 0.0.0.0
failed: Address already in use.
Comment 2 Christopher Beland 2005-01-08 07:30:56 EST
This duplicates bug #122148 and bug #120302.
Comment 3 Tomas Mraz 2005-02-10 05:23:31 EST

*** This bug has been marked as a duplicate of 120302 ***

Note You need to log in before you can comment on or make changes to this bug.