From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L5sAJ-0001dX-UR for garchives@archives.gentoo.org; Fri, 28 Nov 2008 01:29:04 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 486E2E04F2; Fri, 28 Nov 2008 01:29:02 +0000 (UTC) Received: from mail.askja.de (mail.askja.de [83.137.103.136]) by pigeon.gentoo.org (Postfix) with ESMTP id 24607E04F2 for ; Fri, 28 Nov 2008 01:29:02 +0000 (UTC) Received: from static-87-79-89-40.netcologne.de ([87.79.89.40] helo=zone.wonkology.org) by mail.askja.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1L5sAG-0002fs-Oe for gentoo-user@lists.gentoo.org; Fri, 28 Nov 2008 02:29:00 +0100 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by zone.wonkology.org with local; Fri, 28 Nov 2008 02:28:58 +0100 id 00011B87.492F495A.000032C8 From: Alex Schuster Organization: Wonkology To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] sshd won't restart on remote system Date: Fri, 28 Nov 2008 02:28:54 +0100 User-Agent: KMail/1.9.9 References: <49bf44f10811120937g2af6ef6dj685da2c31d749f0a@mail.gmail.com> <350fc7cf0811121538r343218efwc78fb9881c889e01@mail.gmail.com> <49bf44f10811121629w5d68b98fxfd24634370a9eb92@mail.gmail.com> In-Reply-To: <49bf44f10811121629w5d68b98fxfd24634370a9eb92@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811280228.56881.wonko@wonkology.org> X-Archives-Salt: fbc7b370-ad1a-438e-b4c2-9e00080fca4b X-Archives-Hash: 4546625ab1523eb99749f700217f3fff Grant wrote: > >>> >> If it doesn't start I'm locked out of the remote system. > >>> > > >>> > You may be interested in : > >>> > /etc/init.d/sshd reload > >>> > >>> I get: > >>> > >>> # /etc/init.d/sshd reload > >>> * Reloading sshd ... > >>> No /usr/sbin/sshd found running; none killed. [ ok ] "/etc/init.d/ssh zap" should do it. If "/etc/init.d/ssh start" then still does not work, you may need to kill -9 the running sshd server. You may do this, running ssh sessions will not be terminated by this. You can also start/test the new sshd parallel to the running old one, but on another port: /usr/sbin/sshd -p 12345. Then connect with ssh -p 12345. [...] > >> When is the last time you did an etc-update? > > > > I just checked on my system. sshd is in /usr/bin/sshd. Not sbin. You > > have an outdated /etc/init.d/sshd file. You might need to etc-update, > > or reinstall sshd and run etc-update afterwards > > Thanks for helping me out with this. I re-emerged openssh and now > sshd restarts just fine. I just had the same problem. After upgrading from openssh-4.7_p1-r6 to 5.1_p1-r1, /etc/init.d/sshd did not work. Configs had been updated already. I emerged 5.1_p1-r1 again, and now /etc/init.d/sshd works fine. Wonko