From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1IU4yc-0007YQ-WE for garchives@archives.gentoo.org; Sat, 08 Sep 2007 18:24:15 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l88IGAE0025014; Sat, 8 Sep 2007 18:16:10 GMT Received: from cmsout02.mbox.net (cmsout02.mbox.net [165.212.64.32]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l88IBYgY020056 for ; Sat, 8 Sep 2007 18:11:34 GMT Received: from cmsout02.mbox.net (cmsout02.mbox.net [165.212.64.32]) by cmsout02.mbox.net (Postfix) with ESMTP id 247BE5B47 for ; Sat, 8 Sep 2007 18:11:33 +0000 (GMT) Received: from cmsapps02.cms.usa.net [165.212.11.138] by cmsout02.mbox.net via smtad (C8.MAIN.3.34P) with ESMTP id XID193LiHsLh8290X02; Sat, 08 Sep 2007 18:11:32 -0000 X-USANET-Source: 165.212.11.138 IN josh.cepek@usa.net cmsapps02.cms.usa.net X-USANET-MsgId: XID193LiHsLh8290X02 Received: from [172.19.42.200] [75.72.245.151] by cmsapps02.cms.usa.net (ASMTP/josh.cepek@usa.net) via mtad (C8.MAIN.3.31J) with ESMTP id 883LiHsLf0144M38; Sat, 08 Sep 2007 18:11:31 GMT X-USANET-Auth: 75.72.245.151 AUTH josh.cepek@usa.net [172.19.42.200] Message-ID: <46E2E590.8030207@usa.net> Date: Sat, 08 Sep 2007 13:10:24 -0500 From: Josh Cepek User-Agent: Thunderbird 2.0.0.6 (X11/20070807) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] SSH won't restart References: <49bf44f10709080840k4f64df08r1f3ba9a4e3b4f031@mail.gmail.com> In-Reply-To: <49bf44f10709080840k4f64df08r1f3ba9a4e3b4f031@mail.gmail.com> X-Enigmail-Version: 0.95.3 OpenPGP: id=2E5A5127 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig739F6C0D2FA3045A5424F0F3" Z-USANET-MsgId: XID883LiHsLf0144X38 X-Archives-Salt: 36a30787-f392-4a4b-af82-a710b816c260 X-Archives-Hash: bb1ae5386c287da5d7a46cfb0bd157e9 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig739F6C0D2FA3045A5424F0F3 Content-Type: multipart/alternative; boundary="------------030800060402000005010804" This is a multi-part message in MIME format. --------------030800060402000005010804 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Grant wrote: > I just upgraded ssh and when I try to restart I get: > > * Stopping sshd ... [ !! ] > > I don't see anything about it in '/var/log/sshd/current'. How can I > figure out what is wrong? I'm a little nervous because I don't want > to shut myself out of this remote server. > =20 I had a similar issue after a previous update to ssh when I went to restart it to get it to use the new binaries. One of the nice features of sshd is that your current session will say active even if you kill the sshd daemon process. Of course, if you get disconnected then you will not be able to log back in, so it's good to do what you need to quickly if you do need to kill (or if it's really stuck, kill -9) the process. When I had this problem I issued a `kill -9 PID_NUMBER && /etc/init.d/sshd start` - just be *sure* that you're killing the /usr/sbin/sshd process and not one of your sshd login forks at the same time. Alex Schuster wrote: > If you think the upgrade is necessary and don't want to wait until you = or > s.o. else has physical access in case sshd doesn't come up again, you > could > try to restart sshd manually by issuing a "kill -SIGHUP $( pidof sshd )= ". I don't recommend doing this as it will also kill your current ssh session. If for some reason the SIGHUP doesn't take correctly on the listening daemon you will find yourself locked and kicked out of the server. Use top or htop to determine the actual PID of the daemon only. --=20 Josh --------------030800060402000005010804 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Grant wrote: 
I just upgraded ssh and when I try to restart I get:

* Stopping sshd ... [ !! ]

I don't see anything about it in '/var/log/sshd/current'.  How can I
figure out what is wrong?  I'm a little nervous because I don't want
to shut myself out of this remote server.

I had a similar issue after a previous update to ssh when I went to restart it to get it to use the new binaries.  One of the nice featu= res of sshd is that your current session will say active even if you kill the sshd daemon process.  Of course, if you get disconnected then yo= u will not be able to log back in, so it's good to do what you need to quickly if you do need to kill (or if it's really stuck, kill -9) the process.  When I had this problem I issued a `kill -9 PID_NUMBER && /etc/init.d/sshd start` - just be sure that you're killing the /usr/sbin/sshd process and not one of your sshd login forks at the same time.

Alex Schuster wrote:
If you think the upgrade is necessary and don't= want to wait until you or
s.o. else has physical access in case sshd doesn't come up again, you could
try to restart sshd manually by issuing a "kill -SIGHUP $( pidof sshd )".


I don't recommend doing this as it will also kill your current ssh session.  If for some reason the SIGHUP doesn't take correctly on th= e listening daemon you will find yourself locked and kicked out of the server.  Use top or htop to determine the actual PID of the daemon o= nly.

--=20
Josh
--------------030800060402000005010804-- --------------enig739F6C0D2FA3045A5424F0F3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFG4uWVHSSgJy5aUScRAnd0AJ9MYeAlhYDIcpd85sYxFiu9lMCvZgCcDXqc 5Vuhjl+MWJGdV+IaukihpP0= =E8ue -----END PGP SIGNATURE----- --------------enig739F6C0D2FA3045A5424F0F3-- -- gentoo-user@gentoo.org mailing list