rsync /somedir work@backups::somearchive/ gets stuck in huge
maildirs, rsync /somedir root@backups:/some/path/ works
hashproduct+rsync at gmail.com
Mon Dec 18 22:21:13 GMT 2006
I believe you that rsync over SSH works but an rsync daemon hangs;
still, the hanging in the case of the daemon seems to be the fault of
the network. Possibly the network especially likes port 22 or
especially doesn't like port 873. You could run the SSH daemon or the
rsync daemon on different ports or run a single-use rsync daemon over
SSH and note which combinations succeed and which hang; that might
provide more hints about what is causing the hanging.
I'm forwarding your message to the rsync list in case anyone else has ideas.
On 12/18/06, Herwig Wittmann <hw at geizhals.at> wrote:
> Hi Matt,
> sorry, this is long.
> Matt McCutchen wrote:
> > On line 735 of rsyncdaemon.strace.13682, the receiver is waiting for
> > more data to arrive from the sender. Meanwhile, on line 1829 of
> > rsyncclient.strace, the outgoing buffer on the sender's socket has
> > filled up and the sender is waiting until there is room for more data
> > to be sent to the receiver.
> thank you for reading my straces!
> > Clearly the network is at fault for not
> > passing the data waiting in the sender's outgoing buffer on to the
> > receiver.
> i really apologize for trying to protest,
> and i just hope i'm not leading you on a wrong track, but i really try
> to do everything i can to find any misconfiguration or network
> and i've been using rsync since ~2000 (ok, that admittedly does not say
> much about any qualifications :P)
> "but" :)
> to me, it seems to be always the same pattern-
> rsync with double dot syntax repeatedly gets stuck
> (please see the included backup log file excerpts if you can take the
> time), and a single run as root always completes the synchronization
> and thereby clears the problem.
> 1) rsync will reproduceably hang in yet unsynchronized huge maildirs by
> invoking: rsync /somedir work at backups::somearchive/#
> while the other invocation will always work and synchronize:
> rsync /somedir root at backups:/some/path/
> (tried more than 30 times)
> 2) there is various other (lower volume) tcp traffic happening on the
> mentioned 16 mbit line, which is monitored by nagios, munin and smokeping.
> none of those tools showed any indications of trouble, and i mentioned
> that i left a ping running during the hanging transfers as well,
> which did not show any packet loss or unusally high round trip times.
> i try to supply more (weak) evidence of my claims:
> the following shows attempts of a nightly cron job to synchronize a few
> directories using the rsync double dot syntax, the exact command is:
> rsync --timeout=600 --port=873 -avz --numeric-ids --delete \
> --password-file=/etc/rsyncd.work /home/archiver \
> work at backups::work/home/archiver 2>> /root/backup.err >>
> please note that the /home/archiver directory contains a huge number of
> files not yet synchronized to the backup storage host running the rsynd
> daemon, and that that rsync run always times out with return value 30.
> the exact wording of the error message is:
> --- snip ---
> io timeout after 608 seconds -- exiting
> rsync error: timeout in data send/receive (code 30) at io.c(165) [sender=2.6.9]
> --- snap ---
> a backup log file of the last days, showing that
> the not yet manually synchronized /home/archiver/, which contains
> a very huge Maildir always gets "stuck":
> 15.12.06 05:10:02  STARTING BACKUP
> 15.12.06 05:10:47  /home/heidi status: 0
> 15.12.06 05:25:56  /home/big23 status: 0
> 15.12.06 05:41:31  /home/archiver status: 30
> 16.12.06 05:10:01  STARTING BACKUP
> 16.12.06 05:10:46  /home/heidi status: 0
> 16.12.06 05:26:10  /home/big23 status: 0
> 16.12.06 05:40:43  /home/archiver status: 30
> 17.12.06 05:10:01  STARTING BACKUP
> 17.12.06 05:10:23  /home/heidi status: 0
> 17.12.06 05:22:33  /home/big23 status: 0
> 17.12.06 05:38:05  /home/archiver status: 30
> 18.12.06 05:10:01  STARTING BACKUP
> 18.12.06 05:10:28  /home/heidi status: 0
> 18.12.06 05:23:13  /home/big23 status: 0
> 18.12.06 05:37:04  /home/archiver status: 30
> just right now, a single run using
> rsync --rsync-path=/root/rsync-debug \
> --timeout=600 -avz --numeric-ids --delete \
> --password-file=/etc/rsyncd.work \
> /home/archiver root at backups:/storage/mirror/work/home/archiver/ \
> 2> /root/rsyncdebug.err > /root/rsyncdebug.out
> synchronized the directory without hanging.
More information about the rsync