From owner-freebsd-hubs@FreeBSD.ORG Fri Jul 11 09:53:59 2003 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C6C137B401 for ; Fri, 11 Jul 2003 09:53:59 -0700 (PDT) Received: from ldc.ro (ldc-gw.rdsnet.ro [213.157.163.8]) by mx1.FreeBSD.org (Postfix) with SMTP id 0A4FE43FA3 for ; Fri, 11 Jul 2003 09:53:58 -0700 (PDT) (envelope-from razor@ldc.ro) Received: (qmail 88868 invoked by uid 666); 11 Jul 2003 16:53:56 -0000 Date: Fri, 11 Jul 2003 19:53:56 +0300 From: Alex Popa To: Dan Langille Message-ID: <20030711165356.GB88640@ldc.ro> References: <3F0EABA5.18694.1A30CE3E@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F0EABA5.18694.1A30CE3E@localhost> User-Agent: Mutt/1.4.1i cc: freebsd-hubs@FreeBSD.org Subject: Re: cvsupd : TreeComp failed: Network write failure: Connection closed X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Distributions Hubs: mail sup ftp List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2003 16:53:59 -0000 On Fri, Jul 11, 2003 at 12:20:53PM -0400, Dan Langille wrote: > I am seeing this message frequently in /var/log/cvsupd.log on > cvsup.nz.freebsd.org but I don't know what it causing it: > > Jun 14 00:10:10 cvsup cvsupd[60286]: +801 user@example.org > [SNAP_16_1e/17.0] > Jun 14 00:24:44 cvsup cvsupd[60286]: =801 [2968Kin+1243Kout] src- > all/cvs > cvsup cvsupd[60286]: -801 [2968Kin+1243Kout] TreeComp failed: Network > write failure: Connection closed > > It does not occur on all client connections, but regularly enough for > me to be concerned. Any ideas? > -- > Dan Langille : http://www.langille.org/ > Sorry, I replied too soon. I have checked my logs more carefully, and the message you mention, as well as another one, mentioning "Network read failure: Connection closed", seem to occur on dial-up clients, usually after quite a while (over 10 minutes since the initial connection). This looks to me like some kind of timeout. I have also seen two "Network write failure: Connection lost" messages, which I haven't been able to trace. Hope this helps. Alex ------------+------------------------------------------------------- Alex Popa, | "Computer science is no more about computers than razor@ldc.ro| astronomy is about telescopes" -- E. W. Dijkstra ------------+------------------------------------------------------