#1072990 rsync error: error in rsync protocol data stream (code 12) at token.c(481) [sender=3.2.7]

Package:
rsync
Source:
rsync
Description:
fast, versatile, remote (and local) file-copying tool
Submitter:
Norbert Schulz
Date:
2024-06-11 16:09:07 UTC
Severity:
normal
#1072990#5
Date:
2024-06-11 12:17:00 UTC
From:
To:
Dear Maintainer,

rsync faild to sync with the following error after syncing a few files:
receiving file list ... done
./
etc/cups/
etc/cups/printers.conf
etc/cups/printers.conf.O
etc/cups/subscriptions.conf
etc/cups/subscriptions.conf.O
etc/cups/ppd/
etc/cups/ppd/Brother_MFC_L2710DW_series.ppd
etc/cups/ppd/Brother_MFC_L2710DW_series_BRNB422000DB15D_local_barsch.ppd
etc/cups/ppd/Brother_MFC_L2710DW_series_barsch.ppd
etc/cups/ppd/Generic_PostScript_barsch.ppd
etc/cups/ppd/PDF_barsch.ppd
home/norbert/
home/norbert/.Xauthority
home/norbert/.bash_history
deflate on token returned 0 (6320 bytes left)
rsync error: error in rsync protocol data stream (code 12) at token.c(481) [sender=3.2.7]
rsync: connection unexpectedly closed (4847775 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(231) [receiver=3.2.7]
rsync: [generator] write error: Broken pipe (32)
rsync error: error in socket IO (code 10) at io.c(848) [generator=3.2.7]

The rsync command is:
rsync  -avz --numeric-ids -e ssh --delete --delete-excluded   \
        --exclude-from="$EXCLUDES" --exclude="- *.LN*" \
        $EXTRAOPT \
        $SERVER:/ $DATA_PATH/$SERVER/daily.0

The $XXX variables are defined before in the backup script.
This rsync script runs on the backup server and saves computers in the local network. In the network
there are also outdatet versions of rsynch (3.0.9-4+deb7u2 and 3.1.2-1+deb9u3) which runs without
any errors. Errors occur only with version of 3.2.7-1.

Any help would be great and thanksfull

Regards
Norbert Schulz
#1072990#10
Date:
2024-06-11 12:32:24 UTC
From:
To:
[...]

Could you try without the 'z' option?
There were issues with compression sometimes causing errors.

It's also possible that the compression is actually slowing the
transfer, if the network is fast enough.

Note that '-e ssh' is redundant, that has been default for a long time
now.


Thanks,
Paul
#1072990#15
Date:
2024-06-11 13:04:15 UTC
From:
To:
Hi Paul,

thanks for your quick answer.

If I run rsync without 'z' option the error is:

[receiver] exceeded --max-alloc=1073741824 setting (file=fileio.c, line=260)
rsync error: error allocating core memory buffers (code 22) at util2.c(80) [receiver=3.2.7]
rsync: [generator] write error: Broken pipe (32)
rsync: connection unexpectedly closed (18054825 bytes received so far) [generator]

Thanks for the hint '-e ssh'.


Regards
Norbert


Am 11.06.24 um 14:32 schrieb Paul Slootman:
#1072990#20
Date:
2024-06-11 13:15:12 UTC
From:
To:
Hmm, you could be running into a memory constraint, are you transferring
a very large number of files? If so, is it possible to split the
transfer up into smaller parts?


Thanks,
Paul
#1072990#25
Date:
2024-06-11 16:06:10 UTC
From:
To:
Yes, I am transferring a very large number of files. The curiosity is,
that it works until debian 12.4 or even with the last update of rsync
without these errors.

I can split the transfer into smaller parts. I will try and come back with the results.

Thanks,
Norbert

Hmm, you could be running into a memory constraint, are you transferring
a very large number of files? If so, is it possible to split the
transfer up into smaller parts?


Thanks,
Paul