From owner-freebsd-questions@FreeBSD.ORG Mon Jan 22 21:25:21 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 94CF216A4F1 for ; Mon, 22 Jan 2007 21:25:21 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 4F03113C54E for ; Mon, 22 Jan 2007 21:25:21 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from vanquish.pgh.priv.collaborativefusion.com (vanquish.pgh.priv.collaborativefusion.com [192.168.2.61]) (SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Mon, 22 Jan 2007 16:25:19 -0500 id 00056415.45B52BC0.00013EC3 Date: Mon, 22 Jan 2007 16:25:19 -0500 From: Bill Moran To: Peter Pluta Message-Id: <20070122162519.cc3a0838.wmoran@collaborativefusion.com> In-Reply-To: <45B5295D.3020205@placidpublishing.net> References: <45B4032C.3070404@placidpublishing.net> <45B5295D.3020205@placidpublishing.net> Organization: Collaborative Fusion X-Mailer: Sylpheed 2.3.0 (GTK+ 2.10.7; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: rsync issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 21:25:21 -0000 In response to Peter Pluta : > > Peter Pluta wrote: > > I have a win2k3 server running as my rsync server. I also have a > > freebsd web server being the rsync client. A shell script runs every > > night at 5am (it's below). > > > > Shell script: > > > > #!/bin/sh > > . `dirname $0`/settings.inc > > destination=**.***.***.***::backup > > if [ "$TERM" ]; then verbose=-v; fi > > rsync $verbose -azR --delete-after /usr/local/etc/ $destination > > rsync $verbose -azR --delete-after /usr/local/lib/sasl2/ $destination > > rsync $verbose -azR --delete-after /var/cron/ $destination > > rsync $verbose -azR --delete-after /root/ $destination > > rsync $verbose -azR --delete-after /etc/ $destination > > rsync $verbose -azR --delete-after --exclude httpd-*.log $wwwDir/ > > $destination > > > > After it runs for 5 minutes it throws this: > > rsync: writefd_unbuffered failed to write 16385 bytes [sender]: Broken > > pipe (32) > > rsync: read error: Connection reset by peer (54) > > rsync error: error in rsync protocol data stream (code 12) at > > io.c(613) [sender=2.6.9] > > > > Dmesg on the box only shows this: > > em0: promiscuous mode enabled > > em0: promiscuous mode disabled > > > > But that is probably pretty old. > > > > What can the problem be? backups are really important to me and they > > don't currently work as the transfer times out after the first few files. > > > > Anyone got an idea? Any feedback or suggestions would be greatly > > appreciated. I don't know what your problem is, but I can make some recommendations on debugging it. *) Are you running it verbosely when this happens? Crank the verbosity up as high as it will go on both the client and the server and see if anything shows up. Is the a DEBUG option available if you recompile? *) Got any network monitoring stuff available? Heavy packet loss? *) Try ktracing the process while it's running. Should narrow down the cause a good bit. Or maybe attach gdb to it. *) Try rsycing to a local directory to see if it still happens. That should narrow the problem down to either network or not. *) fsck your disks? Hope some of this is helpful. Generally, when I have mystery errors, I start with ktrace. If you're not familiar with it, ktrace can be a bit overwhelming, but it's got lotsa useful information. Same can be said for gdb. -- Bill Moran Collaborative Fusion Inc.