This is a discussion on Rsync errors when running from cron within the Rsync forums, part of the Networking and Network Related category; if I run rsync directly I get no errors (I am running it from a simple bash script) When I ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
if I run rsync directly I get no errors (I am running it from a simple
bash script) When I launch those scripts from cron I get the following error each script same error (the only difference between the scripts is the source and destinations) 0 files... 100 files... 200 files... rsync: writefd_unbuffered failed to write 4092 bytes: phase "send_file_entry" [sender]: Broken pipe (32) overflow: flags=0x72 l1=101 l2=1142977646 lastname=^A^B_.^A ERROR: buffer overflow in receive_file_entry [receiver] rsync error: error allocating core memory buffers (code 22) at util.c(121) [receiver=2.6.9] rsync: read error: Connection reset by peer (54) rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-31/rsync/io.c(515) building file list ... I've been trying to scroogle (www.scroogle.org) the info and I'm not finding anything useful. The system initiating this is Mac OS X (10.5.2) with rsync 3.0.2 and the destination is a ReadyNAS NV+ I believe the rsync on that is 2.6.9 but don't quote me on that. Thanks, |