Hello, For some reason ssh has stopped working. Its been a good while since I tried to login remotely so I figure an upgrade is probably to blame as it was working some time ago. This is the only error I see when sshd is started: Oct 28 21:55:52 sshd[7137]: Server listening on :: port 22. Oct 28 21:55:52 sshd[7137]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. What does this mean? TIA
> > For some reason ssh has stopped working. Its been a good > while since I > tried to login remotely so I figure an upgrade is probably to > blame as it > was working some time ago. > > This is the only error I see when sshd is started: > > Oct 28 21:55:52 sshd[7137]: Server listening on :: port 22. > Oct 28 21:55:52 sshd[7137]: error: Bind to port 22 on 0.0.0.0 failed: > Address already in use. > > What does this mean?It probably means sshd is already running. try ps aux | grep sshd And netstat -tupan | grep sshd Then maybe service sshd restart Gerald
Thomas E Dukes wrote on Fri, 28 Oct 2005 22:22:27 -0400:> For some reason ssh has stopped working. Its been a good while since I > tried to login remotely so I figure an upgrade is probably to blame as it > was working some time ago.Are you sure that is is not working? You will get this kind of message after upgrade to 4.2 but it won't stop sshd working (see earlier thread about a week ago). Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de & http://msie.winware.org
On Saturday 29 October 2005 02:22 am, Thomas E Dukes wrote:> Oct 28 21:55:52 sshd[7137]: Server listening on :: port 22. > Oct 28 21:55:52 sshd[7137]: error: Bind to port 22 on 0.0.0.0 failed: > Address already in use.Under /etc/ssh/sshd_config change #ListenAddress 0.0.0.0 to ListenAddress [IP-address-you-want-to-connect-to] restart SSHd and see if it works
Am Sa, den 29.10.2005 schrieb Thomas E Dukes um 4:22:> For some reason ssh has stopped working. Its been a good while since I > tried to login remotely so I figure an upgrade is probably to blame as it > was working some time ago. > > This is the only error I see when sshd is started: > > Oct 28 21:55:52 sshd[7137]: Server listening on :: port 22. > Oct 28 21:55:52 sshd[7137]: error: Bind to port 22 on 0.0.0.0 failed: > Address already in use. > > What does this mean?It is caused by IPv6 in use. Nothing to worry about and no "hard error". Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 02:30:59 up 1 day, 31 users, load average: 0.20, 0.33, 0.24 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: <http://lists.centos.org/pipermail/centos/attachments/20051030/c29ce38c/attachment-0001.sig>
> -----Original Message----- > From: centos-bounces at centos.org > [mailto:centos-bounces at centos.org] On Behalf Of Alexander Dalloz > Sent: Saturday, October 29, 2005 9:32 PM > To: CentOS mailing list > Subject: Re: [CentOS] sshd problems > > Am Sa, den 29.10.2005 schrieb Thomas E Dukes um 4:22: > > > For some reason ssh has stopped working. Its been a good > while since > > I tried to login remotely so I figure an upgrade is > probably to blame > > as it was working some time ago. > > > > This is the only error I see when sshd is started: > > > > Oct 28 21:55:52 sshd[7137]: Server listening on :: port 22. > > Oct 28 21:55:52 sshd[7137]: error: Bind to port 22 on > 0.0.0.0 failed: > > Address already in use. > > > > What does this mean? > > It is caused by IPv6 in use. Nothing to worry about and no > "hard error". > > AlexanderHello Alexander, Thanks, got it working by uncommenting 'ListenAddress 0.0.0.0" Eddie