From owner-freebsd-bugs Mon Apr 1 0:31:12 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 2E2E337B419; Mon, 1 Apr 2002 00:31:05 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g318V1K47539; Mon, 1 Apr 2002 10:31:01 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200204010831.g318V1K47539@zibbi.icomtek.csir.co.za> Subject: Re: misc/36368: sshd error: session_close_by_channel: kill xxxxxx: No such process In-Reply-To: <20020401000441.M99214@blossom.cjclark.org> from "Crist J. Clark" at "Apr 1, 2002 00:04:41 am" To: cjc@FreeBSD.ORG (Crist J. Clark) Date: Mon, 1 Apr 2002 10:31:01 +0200 (SAT) Cc: freebsd@spambox.dk (Henrik Larsson), freebsd-bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > On Sun, Mar 31, 2002 at 09:20:04AM -0800, Henrik Larsson wrote: > > The following reply was made to PR misc/36368; it has been noted by GNATS. > > > > From: Henrik Larsson > > To: freebsd-gnats-submit@FreeBSD.org, freebsd@spambox.dk > > Cc: > > Subject: Re: misc/36368: sshd error: session_close_by_channel: kill > > xxxxxx: No such process > > Date: Sun, 31 Mar 2002 19:19:57 +0200 > > > > > A little more detail on how to reproduce this? I can't. > > > > It is very simple. > > > > Login with sftp then logout. > > > > This produce the message in my message log. > > OK, on one machine I do, > > $ sftp buttercup > Connecting to buttercup... > sftp> ls > drwxr-xr-x 3 cjc cjc 512 Mar 19 03:22 . > drwxr-xr-x 3 root wheel 512 Aug 29 2001 .. > -rw-r--r-- 1 cjc cjc 1576 Aug 29 2001 .cshrc ... > -rw-r--r-- 1 cjc cjc 630 Mar 19 03:22 setupsetilog.sh > sftp> exit > $ > > And on the server I logged into, buttercup, > > $ grep sshd /var/log/messages > $ grep sshd /var/log/authlog | tail -2 > Apr 1 00:01:26 buttercup sshd[20796]: Accepted publickey for cjc from 192.168.64.60 port 3606 ssh2 > Apr 1 00:01:26 buttercup sshd[20796]: subsystem request for sftp > > No errors. You are lucky. I think it also have a little to do with timing. I had the problem when using bitkeeper over ssh too. After first blaming bitkeeper, they determined that it was openssh 2.9. I upgraded all my machines that use bitkeeper to openssh 3.x and the problems went away. Now if you look in the release notes for bitkeeper, you will see this: ################################################################### OpenSSH version 2.9 has a bug which can cause lost EOF errors when used as a BitKeeper transport, especially over slow links. We've confirmed that the problem has been fixed as of version 2.9.9; get an update at http://www.openssh.com/portable.html ################################################################### John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message