rsync - Oct 2009 - exit status 13 in version 3.1

Got this in the log:

rsync error: errors with program diagnostics (code 13) at log.c(340)
[generator3.1.0dev]

What could it be? I suspect it's triggered by a timeout or disconnect
from the server side but I had never seen it.

Carlos Carvalho (carlos at fisica.ufpr.br) wrote on 29 October 2009 13:20:
 >Got this in the log:
 >
 >rsync error: errors with program diagnostics (code 13) at log.c(340)
 >[generator= 3.1.0dev]

Another event:

rsync: read error: Connection reset by peer (104)rsync error: errors with
program diagnostics (code 13) at log.c(340) [generator=3.1.0dev]
rsync error: received SIGUSR1 (code 19) at main.c(1384) [receiver=3.1.0dev]

On Thu, 2009-10-29 at 13:20 -0200, Carlos Carvalho
wrote:
> Got this in the log:
> 
> rsync error: errors with program diagnostics (code 13) at log.c(340)
[generator> 3.1.0dev]
I got this too on a big local run backing up my system to an external
disk using rsnapshot.

/etc/rsnapshot-rsync -aAXxx --del --numeric-ids --relative \
    --delete-excluded --remote-option=--munge-links --filter=P_/home/ \
    --filter=P_/boot/ --exclude=/home/*/.gvfs \
    --link-dest=/media/crypt-backup/snapshots-mattlaptop2/occasional.0/ml2/ \
    /home /media/crypt-backup/snapshots-mattlaptop2/.sync/ml2/ 
rsync error: errors with program diagnostics (code 13) at log.c(340)
[sender=3.1.0dev]
rsync error: received SIGUSR1 (code 19) at log.c(340) [generator=3.1.0dev]

(The /etc/rsnapshot-rsync wrapper script is just prepending another
--link-dest option to the command line.)

This probably has to do with Wayne's recent I/O changes.  When I have
some time tonight, I'll see if I can reproduce the problem and capture
some more information that might help Wayne figure it out.

-- 
Matt