[FreeNX-kNX] Still can't ssh with keys, wtf

[dewey hylton]

> From: Clay McCoy <freenx at claymccoy.com>
> 
> dewey hylton wrote:
> 
> >>Date: Sun, 07 Aug 2005 09:50:30 -0500
> >>From: Clay McCoy <freenx at claymccoy.com>
> >>Subject: Re: [FreeNX-kNX] cannot ssh as nx-user
> >>To: freenx-knx at kde.org
> >>Message-ID: <42F61FB6.9010902 at claymccoy.com>
> >>
> >>I think that I restarted in debug mode.   "/etc/init.d/sshd start -d -d 
> >>-d" is what I had to use because "sshd -d -d -d" wouldn't work.  I hope 
> >>it accomplished the same thing.
> >>Here is output from "tail -f /var/log/secure" There is an error, but I 
> >>don't know what it means.
> >>
> >>Aug  7 09:49:19 localhost sshd[8076]: Received signal 15; terminating.
> >>Aug  7 09:49:32 localhost sshd[8125]: Server listening on :: port 22.
> >>Aug  7 09:49:32 localhost sshd[8125]: error: Bind to port 22 on 0.0.0.0 
> >>failed: Address already in use.
> >>Aug  7 09:50:04 localhost sshd[8130]: Failed password for nx from 
> >>::ffff:192.168.0.4 port 50053 ssh2
> >>
> >>Thanks,
> >>Clay
> >>
> >>
> >>dewey hylton wrote:
> >>
> >>    
> >>
> >>>troubleshoot sshd:
> >>>
> >>>1) stop sshd:
> >>>   /etc/init.d/sshd stop
> >>>2) start sshd with debugging:
> >>>   sshd -d -d -d
> >>>3) attempt to ssh in as you were before; 
> >>>  look through the sshd output and you should find why the key isn't
> >>>  working.
> >>>4) fix the problem, restart sshd: /etc/init.d/sshd start
> >>>      
> >>>
> >
> >the sshd error above (about binding to 0.0.0.0) shows that sshd was still
> >running. try `killall sshd` (from the console!) to get rid of sshd. then
> try
> >`netstat -an|grep -i list` and see of you're still listening on port 22. if
> so,
> >then most likely inetd/xinetd is listening and sshd isn't getting started
> until
> >someone attempts to connect. in this case, you'll have to temporarily
> disable
> >sshd in inetd/xinetd.
> >
> >afterwards, try `sshd -d -d -d` - do not call from the /etc/init.d/sshd
> script,
> >for i doubt the debug parameters will be passed to the daemon that way. i
> know
> >it won't work that way in gentoo, at least.
> >_______________________________________________
> >FreeNX-kNX mailing list
> >FreeNX-kNX at kde.org
> >https://mail.kde.org/mailman/listinfo/freenx-knx
> >  
> >
> 
> I have read that the binding error may not be a problem:
> http://portal.suse.com/sdb/en/2001/11/tsaupe_kde_startmsg.html
> 
> I don't understand how to do debug mode.  I don't know how to tell if I 
> am actually there.  And "sshd -d -d -d" tells me "sshd re-exec requires 
> execution with an absolute path."  But when I give it that path, you say 
> that the parameters won't work.  What am I supposed to do?  What about 
> "service sshd start -d -d -d?"

your /etc/init.d scripts are just that, scripts - they start/stop daemons (which
live elsewhere) with specific parameters. to start sshd manually in debug mode,
execute it yourself; i didn't give you the path before because i don't use suse.
it's probably in /usr/sbin or /usr/local/sbin; execute `which sshd` as root and
you'll probably find out for sure. assuming it exists as /usr/sbin/sshd, then as
root execute `/usr/sbin/sshd -d -d -d` to start sshd in verbose debug mode.