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 <gentoo-user+bounces-69237-garchives=archives.gentoo.org@gentoo.org>)
id 1IUnzS-0004xV-Qu
for garchives@archives.gentoo.org; Mon, 10 Sep 2007 18:28:07 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l8AIJQFe008572;
Mon, 10 Sep 2007 18:19:26 GMT
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242])
by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l8AIAYKl029049
for <gentoo-user@lists.gentoo.org>; Mon, 10 Sep 2007 18:10:34 GMT
Received: by an-out-0708.google.com with SMTP id c8so184371ana
for <gentoo-user@lists.gentoo.org>; Mon, 10 Sep 2007 11:10:33 -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=M4/tkSyCPqrT4NtMcvjsKuldEcLFebgVce5CO4/49Io=;
b=n/4EjSLgdHywF6FcW6N1OSe7ehPmFis/2HTXje9YDxqKafDie2e4LSI1tUu782Y86G+y8F0uNWctIm+bXb2n3AybqBN6Qvgpe1K1eHntrcKoYY+QFy2FZOkipLSNwsxC44sRGgDAoEfNUi/6dMBY55re15tDLJY3wYl8vF8YzlY=
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=PKOQnYUnDpIAwAFbAp5xJeu9M/wbKILKH1fEq3cqoca2VEiDIorUTvZIk3aPKH8zJrTV85yX1hWrvQTX53NnCbEK+YYEaRT3ZyiSBsIk+5vLl+JaZ5owT4scU8Uhx35tNe5wOtMzvhvzJl3XZdvbZAoSMkcZGTIfpqB4jej6BuU=
Received: by 10.100.3.20 with SMTP id 20mr4934348anc.1189447833338;
Mon, 10 Sep 2007 11:10:33 -0700 (PDT)
Received: by 10.100.95.6 with HTTP; Mon, 10 Sep 2007 11:10:33 -0700 (PDT)
Message-ID: <f1c96f570709101110p48177a73x2ea8d812237f9175@mail.gmail.com>
Date: Mon, 10 Sep 2007 13:10:33 -0500
From: "Stephen Wittig" <nofx911@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] SSH won't restart
In-Reply-To: <49bf44f10709101054r13c8b7c4w90f0051ade528dcb@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
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>
<f1c96f570709101029k4d726772rbfe25be57cb12de2@mail.gmail.com>
<49bf44f10709101054r13c8b7c4w90f0051ade528dcb@mail.gmail.com>
X-Archives-Salt: d8400410-50d8-4894-82c8-407bc3f65715
X-Archives-Hash: 40c76ed6b710d80c0d8d6383201f5c9d
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.
-Stephen
On 9/10/07, Grant <emailgrant@gmail.com> wrote:
> > 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