You're right, that is it. Still don't know why sshd is trying to start twice, but I can try to track it down. At least I have one going - that was my big worry. Guess I could have seen that I had one running if I had done a "ps ax", but after the boot scripts reported failure, I didn't even bother to look. Guess I shouldn't believe everything I read! Thanks, Sean On Monday 18 February 2002 18:01, Jeffrey Taylor wrote:

Somehow, sshd is being started twice. The helpful displays are "netstat -A inet -an" (shows open ports) and "lsof -i :22" (connects to/from port 22).

HTH, Jeffrey

Quoting Theo.Sean Schulze :

...

Hello,

While trying to fix my monitor's invalid scan problem, I rebooted the machine. When it came back up, sshd failed to start. A glance in /var/log/messages shows:

Feb 18 17:42:11 dragoon sshd[16878]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Feb 18 17:42:11 dragoon sshd[16878]: fatal: Cannot bind any address.

When I do a netstat -rn, I get this:

Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.99 0.0.0.0 255.255.255.255 UH 40 0 0 ippp0 217.5.98.42 0.0.0.0 255.255.255.255 UH 40 0 0 ppp0 192.168.1.100 0.0.0.0 255.255.255.255 UH 40 0 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth1 0.0.0.0 xxx.xxx.xxx.xxx 0.0.0.0 UG 40 0 0 ppp0

/etc/route.conf looks like this:

192.168.1.0 0.0.0.0 255.255.255.0 eth0 192.168.1.100 0.0.0.0 255.255.255.255 eth1 192.168.1.99 0.0.0.0 255.255.255.255 ippp0 default 192.168.1.100 0.0.0.0 eth1

I am wondering if I should change the gateways for the different interfaces. For example, 192.168.1.0 is my local network address and the NIC that the local traffic passes through (eth0) has the IP 192.168.1.3. Should 192.168.1.3 be eth0's gateway? Since eth1 is the NIC attached to my DSL connection, should it have its own IP as the gateway? Same for ippp0 my ISDN card? Everything else would get the default (eth1)?

TIA, Sean

-- Theo. Sean Schulze tschulze@nuthole.de "[T]he key to maintaining leadership in the economy and the technology that are about to emerge is likely to be the social position of knowledge professionals and social acceptance of their values." -- Peter Drucker

Dan Am writes:

On Monday 18 February 2002 17:51, Theo.Sean Schulze wrote:

...

Feb 18 17:42:11 dragoon sshd[16878]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Something is using port 22. try netsat -an and ps -ef to see what it is. If you cannot find it, check back with the results. hth dan

lsof will show you the process that occupying the port: lsof -i tcp | grep 22

Thanks, that does help out. Now I know sshd is trying to start twice and that SuSE says that they know it is happening. Funny though that the fix is to just ignore it. On Monday 18 February 2002 18:40, Chris Kuhi wrote:

On Monday 18 February 2002 17:51, Theo.Sean Schulze wrote:

...

While trying to fix my monitor's invalid scan problem, I rebooted the machine. When it came back up, sshd failed to start. A glance in /var/log/messages shows:

Feb 18 17:42:11 dragoon sshd[16878]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.

You didn't say which distro/version you're using, but if it's SuSE 7.3, this might be what you're looking for: http://sdb.suse.de/en/sdb/html/tsaupe_kde_startmsg.html

hth, chris

-- Theo. Sean Schulze tschulze@nuthole.de "[T]he key to maintaining leadership in the economy and the technology that are about to emerge is likely to be the social position of knowledge professionals and social acceptance of their values." -- Peter Drucker

Yep. It says to use /etc/rc.config and put "-4" in the sshd options. Didn't work. In the meantime, I have seen that this doesn't happen consistently. Given the other problem I am having with ADSL right now, I am not going to bother with it now. Cheers, Sean On Sunday 24 February 2002 01:47, Stuart Powell wrote:

Hello, Theo.

If you read the SDB article more closely, Solution 1. tells you how to stop the error message by editing rc.config (easiest via YaST) in order to stop sshd loading up the second time for IPv6.

Bye for now, Stuart.

-----Original Message----- From: Theo.Sean Schulze [mailto:tschulze@nuthole.de] Sent: 19 February 2002 05:44 To: suse-linux-e@suse.com Subject: Re: [SLE] sshd can't bind to port 22

Thanks, that does help out. Now I know sshd is trying to start twice and that SuSE says that they know it is happening. Funny though that the fix is to just ignore it.

On Monday 18 February 2002 18:40, Chris Kuhi wrote:

...

On Monday 18 February 2002 17:51, Theo.Sean Schulze wrote:

...

While trying to fix my monitor's invalid scan problem, I rebooted the machine. When it came back up, sshd failed to start. A glance in /var/log/messages shows:

Feb 18 17:42:11 dragoon sshd[16878]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.

You didn't say which distro/version you're using, but if it's SuSE 7.3, this might be what you're looking for: http://sdb.suse.de/en/sdb/html/tsaupe_kde_startmsg.html

hth, chris

-- Theo. Sean Schulze tschulze@nuthole.de "[T]he key to maintaining leadership in the economy and the technology that are about to emerge is likely to be the social position of knowledge professionals and social acceptance of their values." -- Peter Drucker