Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1200540 > unrolled thread

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

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1072990: rsync error: error in rsync protocol data stream (code 12) at token.c(481) [sender=3.2.7] Norbert Schulz <n.schulz@rotorwerk.de> - 2024-06-11 14:30 +0200
    Bug#1072990: rsync error: error in rsync protocol data stream (code 12) at token.c(481) [sender=3.2.7] Paul Slootman <paul@debian.org> - 2024-06-11 15:00 +0200
      Bug#1072990: rsync error: error in rsync protocol data stream (code 12) at token.c(481) [sender=3.2.7] Norbert Schulz <n.schulz@rotorwerk.de> - 2024-06-11 15:20 +0200
        Bug#1072990: rsync error: error in rsync protocol data stream (code 12) at token.c(481) [sender=3.2.7] Paul Slootman <paul@debian.org> - 2024-06-11 15:20 +0200
          Bug#1072990: rsync error: error in rsync protocol data stream (code 12) at token.c(481) [sender=3.2.7] Norbert Schulz <n.schulz@rotorwerk.de> - 2024-06-11 18:10 +0200

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

Package: rsync
Version: 3.2.7-1
Severity: normal

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  


-- System Information:
Debian Release: 12.5
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rsync depends on:
ii  init-system-helpers        1.65.2
ii  libacl1                    2.3.1-3
ii  libc6                      2.36-9+deb12u7
ii  liblz4-1                   1.9.4-1
ii  libpopt0                   1.19+dfsg-1
ii  libssl3                    3.0.11-1~deb12u2
ii  libxxhash0                 0.8.1-1
ii  libzstd1                   1.5.4+dfsg2-5
ii  lsb-base                   11.6
ii  sysvinit-utils [lsb-base]  3.06-4
ii  zlib1g                     1:1.2.13.dfsg-1

rsync recommends no packages.

Versions of packages rsync suggests:
ii  openssh-client       1:9.2p1-2+deb12u2
ii  openssh-server       1:9.2p1-2+deb12u2
ii  python3              3.11.2-1+b1
pn  python3-braceexpand  <none>

-- no debconf information

[toc] | [next] | [standalone]

#1200543

On Tue 11 Jun 2024, Norbert Schulz wrote:

> deflate on token returned 0 (6320 bytes left)

[...]

> The rsync command is:
> rsync  -avz --numeric-ids -e ssh --delete --delete-excluded   \

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

[toc] | [prev] | [next] | [standalone]

#1200547

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:

> On Tue 11 Jun 2024, Norbert Schulz wrote:
>
>> deflate on token returned 0 (6320 bytes left)
> [...]
>
>> The rsync command is:
>> rsync  -avz --numeric-ids -e ssh --delete --delete-excluded   \
> 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

[toc] | [prev] | [next] | [standalone]

#1200549

On Tue 11 Jun 2024, Norbert Schulz wrote:
> 
> 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]

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

[toc] | [prev] | [next] | [standalone]

#1200569

[Multipart message — attachments visible in raw view] — view raw

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


On Tue 11 Jun 2024, Norbert Schulz wrote:

> 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]

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web