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 1IUrNb-0005wL-1M for garchives@archives.gentoo.org; Mon, 10 Sep 2007 22:05:19 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l8ALulmD002400; Mon, 10 Sep 2007 21:56:47 GMT Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l8ALqEol029929 for ; Mon, 10 Sep 2007 21:52:15 GMT Received: by an-out-0708.google.com with SMTP id c8so195844ana for ; Mon, 10 Sep 2007 14:52:10 -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=5iWYCJZRloRp3FUH+3nnGvg4rTa6ukw9pmruwJpEXS0=; b=Te4Baxo88Y3KDYVse8BJyumqjvuUNiVdVJPkk1ZBFzwebf2GVwh03rt8rmby+HX1gfWpUapeJX1qnUJkrzH3th8LGDhZPePTV1sGxB/mpzNegoXljSnfj8MNQkhxjiHLDil8HkuNCPb5gXBO3878I53DH+sQViSA73IO12917hg= 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=h2a0IyyS+Sqk4qajZ+lG5CEYLA3mkdeOkJSUdmEKbKnHrgN8N6Pe9WETCfvmzEGGOKx5CDSLRWX5A4guahbwkifguhIo9LZ4Z9S/433GK6vdgv71uIlvaXicunicHt09WimYtccW+/uz+Gd4T1wV1lUn4EXvWVCw2gZH3zWYjXA= Received: by 10.100.10.20 with SMTP id 20mr5309605anj.1189461130853; Mon, 10 Sep 2007 14:52:10 -0700 (PDT) Received: by 10.100.95.6 with HTTP; Mon, 10 Sep 2007 14:52:10 -0700 (PDT) Message-ID: Date: Mon, 10 Sep 2007 16:52:10 -0500 From: "Stephen Wittig" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] SSH won't restart In-Reply-To: <49bf44f10709101212r26f869d9n2b6c7e6fd1f8395f@mail.gmail.com> 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> <49bf44f10709101212r26f869d9n2b6c7e6fd1f8395f@mail.gmail.com> X-Archives-Salt: aa990ec0-f194-4fb0-9b1a-e40ff0d44300 X-Archives-Hash: 6084c61e4410464e7bee0e6019f5a310 I think that there may be something significantly wrong with your box (or configuration of sshd). I have never had a server disconnect an active connection when killing the ssh daemon. If there is someone that you can contact in the data center I would ask them to: 1) Backup your current sshd_config file 2) Restore the default sshd_config on the box, and then try restart the daemon Are there any other applications that are not behaving correctly? -Stephen On 9/10/07, Grant wrote: > > 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 > > -- gentoo-user@gentoo.org mailing list