Subject: Re: ssh problems (revisited)
From: Ken Schweigert (ken@byte-productions.com)
Date: Wed Mar 20 2002 - 09:09:40 MST
Dylan,
The error "Cannot bind any address" means that something is already
listening to the port that sshd normally binds to; in this case tcp/22.
This usually caused by inetd or xinetd grabbing the port before sshd
can. Check to see which one is running:
[root@byte-8 /root]# ps ax|grep inet
643 ? S 0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid
If it's xinetd, look for a file /etc/xinetd.d/sshd. It should have a
line 'disable = yes'. If you had to change the file, restart xinetd with:
[root@byte-8 /root]# /etc/rc.d/init.d/xinetd restart
If it's inetd, open /etc/inetd.conf in an editor and comment out the line
that refers to sshd, then restart it.
[root@byte-8 /root]# killall -HUP inetd
-ken
On Tue, Mar 19, 2002 at 07:14:54PM -0800, dylan wrote:
> rebuilt openssh from source with suport for PAM amongst other things
> and get this in messages:
>
> Mar 19 19:03:02 pm7100 rc: Starting sshd succeeded
> Mar 19 19:11:35 pm7100 sshd: Starting sshd:
> Mar 19 19:11:37 pm7100 sshd[376]: fatal: Cannot bind any address.
> Mar 19 19:11:37 pm7100 sshd: sshd startup succeeded
> Mar 19 19:11:37 pm7100 sshd: ^[[60G
> Mar 19 19:11:37 pm7100 sshd:
>
> however, i still cannot connect...
> any ideas?
>
> thanks
> dylan
> --
>
-- -Ken Schweigert, Aspiring Network Administrator Byte Productions, LLC http://www.byte-productions.com
This archive was generated by hypermail 2a24 : Wed Mar 20 2002 - 09:24:15 MST