Date: Mon, 1 Apr 2002 02:24:53 -0800 From: "Crist J. Clark" <crist.clark@attbi.com> To: John Hay <jhay@icomtek.csir.co.za> Cc: Henrik Larsson <freebsd@spambox.dk>, freebsd-bugs@FreeBSD.ORG Subject: Re: misc/36368: sshd error: session_close_by_channel: kill xxxxxx: No such process Message-ID: <20020401022453.P99214@blossom.cjclark.org> In-Reply-To: <200204010831.g318V1K47539@zibbi.icomtek.csir.co.za>; from jhay@icomtek.csir.co.za on Mon, Apr 01, 2002 at 10:31:01AM %2B0200 References: <20020401000441.M99214@blossom.cjclark.org> <200204010831.g318V1K47539@zibbi.icomtek.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 01, 2002 at 10:31:01AM +0200, John Hay wrote: > > 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 <freebsd@spambox.dk> > > > 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 <auth.info> buttercup sshd[20796]: Accepted publickey for cjc from 192.168.64.60 port 3606 ssh2 > > Apr 1 00:01:26 <auth.info> 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 > ################################################################### There's not a lot we can do about this possible bug unless we have reasonably reliable way to reproduce it. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020401022453.P99214>