minor ssh problem with new 7.3
Hi, Just upgraded to 7.3 and now get the following messages on every boot: Oct 16 19:30:29 thinkpad sshd[431]: Server listening on :: port 22. Oct 16 19:30:29 thinkpad sshd[431]: error: Bind to port 22 on 0.0.0.0 failed: Ad dress already in use. But, sshd is working OK and is running as pid 431. -- ____________________________________________________________________ Robert Paulsen paulsen@texas.net
You have two startups of sshd. The second is failing because the
first one has already bound the port. Do a "ps ax | grep sshd" and
you will see that it is not process ID 431. Trying to find where the
second one is started from gets a little tricky/tedious. I'd check
/etc/rc.d for two startup scripts, one legacy and one new. Also the
rcX.d subdirectories for two links to /etc/rc.d/sshd.
HTH,
Jeffrey
Quoting Robert C. Paulsen Jr.
Hi,
Just upgraded to 7.3 and now get the following messages on every boot:
Oct 16 19:30:29 thinkpad sshd[431]: Server listening on :: port 22. Oct 16 19:30:29 thinkpad sshd[431]: error: Bind to port 22 on 0.0.0.0 failed: Ad dress already in use.
But, sshd is working OK and is running as pid 431.
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck
* Jeffrey Taylor [Tue, 16 Oct 2001 20:49:37 -0500]:
I'd check /etc/rc.d for two startup scripts, one legacy and one new. Also the rcX.d subdirectories for two links to /etc/rc.d/sshd.
Just a minor nit: /etc/init.d is the real directory holding the files. /etc/rc.d is only a symlink to it. Philipp -- caffeine low .... brain halted
Hi Philipp, @ 10:35:27 PM on 10/16/2001, Philipp Thomas wrote:
I'd check /etc/rc.d for two startup scripts, one legacy and one new. Also the rcX.d subdirectories for two links to /etc/rc.d/sshd.
PT> Just a minor nit: /etc/init.d is the real directory holding the PT> files. /etc/rc.d is only a symlink to it. What I can't understand is why 7.2 (I realize they're at 7.3 now) doesn't have that symlink, or why SuSE didn't just put them in /etc/init.d in the first place. :-\ I had to add that symlink to please a few RPMs just the other day. I'm still new to the distribution, but he might also try: egrep -r sshd /etc/rc* And see if that leads to any clues.. -- -Brian Clark | PGP is spoken here: 0xE4D0C7C8 Please, DO NOT carbon copy me on list replies.
On Tue, Oct 16, 2001 at 08:49:37PM -0500, Jeffrey Taylor wrote:
You have two startups of sshd. The second is failing because the first one has already bound the port. Do a "ps ax | grep sshd" and you will see that it is not process ID 431. Trying to find where the second one is started from gets a little tricky/tedious. I'd check /etc/rc.d for two startup scripts, one legacy and one new. Also the rcX.d subdirectories for two links to /etc/rc.d/sshd.
HTH, Jeffrey
There is only one instance of sshd running (PID 431). Using "ps ax I grep sshd" is how I knew that the running PID matched the PID in the error message. The only links to sshd in rc5.d are K15sshd and S08sshd.
Quoting Robert C. Paulsen Jr.
: Hi,
Just upgraded to 7.3 and now get the following messages on every boot:
Oct 16 19:30:29 thinkpad sshd[431]: Server listening on :: port 22. Oct 16 19:30:29 thinkpad sshd[431]: error: Bind to port 22 on 0.0.0.0 failed: Ad dress already in use.
But, sshd is working OK and is running as pid 431.
-- ____________________________________________________________________ Robert Paulsen paulsen@texas.net
participants (4)
-
Brian Clark
-
Jeffrey Taylor
-
philippt@t-online.de
-
Robert C. Paulsen Jr.