Re: rsync issues
I've gotten a few replies and i've tried almost all of the suggestions but the problem still resides. I re-installed rsync on both box's and it still does this. Peter Pluta wrote: Anyone? 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. Thanks, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync issues
Hi, I've gotten a few replies and i've tried almost all of the suggestions but the problem still resides. I re-installed rsync on both box's and it still does this. Most likely won't help, but do you have any sort of traffic shaping between the two boxes (not sure if they are on the same LAN or remote), but it is something to check - give appropriate bandwidth for the operation. If they are remotely localted, how about trying to rsync locally (picking up a similar machine) and see if you get the same error. I am not a technical guy. I am just suggesting to check QoS. Warm regards, -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync issues
just to go through what i'd normally check: 1) make sure the source host is up at 100full 2) make sure the port the source host is plugged into is 100full 3) make sure the destination host is up at 100full 4) make sure the port the destination host is plugged into is 100full given all of that, if you still have trouble you might want to start doing some packet dumps and see if one host or the other are terminating the connection: $ tcpdump -n -vvv -s 1518 -g On 23/01/07, Peter Pluta [EMAIL PROTECTED] wrote: I've gotten a few replies and i've tried almost all of the suggestions but the problem still resides. I re-installed rsync on both box's and it still does this. Peter Pluta wrote: Anyone? 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. Thanks, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Greg Albrecht ([EMAIL PROTECTED]) An Indie, Hip Hop and IDM Podcast: The Letter G http://theletterg.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync issues
Anyone? 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. Thanks, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync issues
In response to Peter Pluta [EMAIL PROTECTED]: 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync issues
Peter Pluta wrote: Anyone? 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. Thanks, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Looks like the 2k3 box is resetting the connection for whatever reason. -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / [EMAIL PROTECTED] Today's Excuse: excess surge protection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync issues
On 21/01/07, Peter Pluta [EMAIL PROTECTED] wrote: 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] i had a similar problem and the fix ended up being pretty simple: make sure the windows box has the right duplex setting, eg: 100full -g -- Greg Albrecht ([EMAIL PROTECTED]) An Indie, Hip Hop and IDM Podcast: The Letter G http://theletterg.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
