Bug 141119 - sshd failed to bind to port 22
Summary: sshd failed to bind to port 22
Status: CLOSED DUPLICATE of bug 120302
Alias: None
Product: Fedora
Classification: Fedora
Component: openssh   
(Show other bugs)
Version: 3
Hardware: All Linux
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-29 14:24 UTC by feily
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

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

Attachments (Terms of Use)

Description feily 2004-11-29 14:24:19 UTC
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: 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):

How reproducible:

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 05:21:52 UTC
Confirmed, but only if IPv6 kernel module is loaded (which is the
default). On "service sshd restart" I see the following in

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
failed: Address already in use.

Comment 2 Christopher Beland 2005-01-08 12:30:56 UTC
This duplicates bug #122148 and bug #120302.

Comment 3 Tomas Mraz 2005-02-10 10:23:31 UTC

*** 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.