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 1IUov2-0004HY-En for garchives@archives.gentoo.org; Mon, 10 Sep 2007 19:27:38 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l8AJICq3020279; Mon, 10 Sep 2007 19:18:12 GMT Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.227]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l8AJCFpv013768 for ; Mon, 10 Sep 2007 19:12:17 GMT Received: by nz-out-0506.google.com with SMTP id s18so567096nze for ; Mon, 10 Sep 2007 12:12:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Mg7zOZratqkPZoY33XHpd9S2A9O33GADnrFCN1YeSAQ=; b=lA70BO5MjtE/iaRymhC5cUp++YIs1VL/Ja8TXm0Vb0ZhX9EeMSb4QeAm8ZshBfDWcMLPaaqxcrwF/PjH2JJ7P6x8JkGqqiDzK4SWyIJuVzSgynspCyFM4NAipKrunj/hOPUvlxG24lcRq94xVCcVOail0ez7A8BJsmV7GWGcxRM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YTDhh5kZ8/COPcLSzCPqsak7P2CAV1q7BSfzqQqQWhgQFxdAikGxPersIoB0mumW317+OA42FzbRJvEs7yXsuMgrADzRRFAOG67voOHTdO1oRE0D6iwcJueV36J3GDoNJaX3iA6+QPDNCqVTBXOtjYcZfgDpcvEZ9bZS3cqcehA= Received: by 10.114.107.19 with SMTP id f19mr148035wac.1189451533883; Mon, 10 Sep 2007 12:12:13 -0700 (PDT) Received: by 10.115.110.15 with HTTP; Mon, 10 Sep 2007 12:12:13 -0700 (PDT) Message-ID: <49bf44f10709101212r26f869d9n2b6c7e6fd1f8395f@mail.gmail.com> Date: Mon, 10 Sep 2007 12:12:13 -0700 From: Grant To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] SSH won't restart In-Reply-To: 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49bf44f10709080840k4f64df08r1f3ba9a4e3b4f031@mail.gmail.com> <46E2E590.8030207@usa.net> <49bf44f10709100958jd3516d7tbdf5bf1e804f412f@mail.gmail.com> <49bf44f10709101054r13c8b7c4w90f0051ade528dcb@mail.gmail.com> X-Archives-Salt: a25c7aa1-82fb-4589-b6b1-8d49a4b675db X-Archives-Hash: 24c7c3e6402e592fd4be8434e62668b6 > Yes. As a personal preference I don't usually chain commands together > when trouble shooting something, but there is technically nothing > wrong with doing so. And now I'm locked out. What do you think guys? - Grant > > > This process is the ssh daemon: > > > root 2988 1 0 Sep04 ? 00:00:00 /usr/sbin/sshd > > > > > > Two things: before killing the process with the KILL signal, I would > > > try killing it with TERM > > > kill -TERM 2988 > > > > > > If that doesn't work then kill the process with the KILL signal. > > > > > > I would also use: > > > /etc/init.d/sshd restart > > > > > > This will give the init script a chance to do some cleanup work before > > > restarting > > > > Do this: > > > > kill -TERM 2988 && /etc/init.d/sshd restart > > > > and if that doesn't work, do: > > > > kill -9 2988 && /etc/init.d/sshd restart > > > > ? > > > > - Grant > > > > > > > > > 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 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. > > > > > > > > OK, I've got to be really careful here. I see the following processes > > > > in 'ps -ef': > > > > > > > > root 2988 1 0 Sep04 ? 00:00:00 /usr/sbin/sshd > > > > root 7573 2988 0 07:28 ? 00:00:00 sshd: root@pts/0 > > > > > > > > Should I: > > > > > > > > kill -9 2988 && /etc/init.d/sshd start > > > > > > > > Are you sure? :) > > > > > > > > - Grant -- gentoo-user@gentoo.org mailing list