Error in rsync protocol data stream code 12 at io c 600

Backups and file transferring is important for server management.

And Rsync is one of the best shots, but errors are always a setback.

Rsync error code 12 is a tricky error that occurs due to insufficient disk space, network errors and so on.

That is why at Bobcares, we often get requests to fix Rsync errors as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix Rsync error code 12 for our customers.

Explaining Rsync error code 12

Rsync is one of the popular file synchronization tools. It is useful for both local and remote file transfer.

If the destination already contains the source file then the Rsync only copies the differences. This makes Rsync a faster file transfer option.

But, in many situations, the Rsync operation ends by showing the error message:

rsync error: error in rsync protocol data stream (code 12) at io.c(xxx).

So, why does the file transfer ends by showing an error code 12?

Usually, the reason for this varies from insufficient disk space to network errors, improper destination and so on.

Let’s now check on a few reasons and see how our Support Engineers fix them.

Causes and fixes for the Rsync error 12

Whenever a server operation ends up in error, the initial troubleshooting starts from the log file. In the case of Rsync, our Support Engineers always make sure to set up the log file right. As a result, the reason that leads to the error can be easily found out from teh log file.

The most common reasons for the Rsync error code 12 are:

1. Insufficient disk space

While trying to Rsync data from one server to another, one of our customers got the error code 12. Here, the user tried to transfer a large file.

So, our Support Engineers initially tried to transfer a small file. Since the file transfer was successful, we could infer that the disk space was insufficient in the first case.

Thus, we always recommend checking the disk space before transferring large files. For instance, the free disk space should be at least more than the size of the largest file.

2. Missing remote Rsync

In some cases, the remote side does not have Rsync installed. Also, the destination path specified does not exist. In both cases, the Rsync error 12 shows up.

For instance, one of our customers executed the command:

rsync -v -v -e 'ssh -p YY' ./testfile user@XXXXX:/home

Here, YY denotes the SSH port number.

This ended up in the error code 12.

Initially, our Dedicated Engineers made sure that ssh -p YY user@XXXXX works fine. Since this was working fine, we checked the Rsync in the remote end.

Rsync was found missing in the remote end. So, we installed it on the Ubuntu/Debian server using:

apt-get install rsync

That fixed the error and Rsync ran successfully.

3. Failure due to idle connection

Similarly, an idle connection can also show the error code 12 in remote file transfer.

In such situations, our Support Team always recommends using –timeout option in the Rsync command. Here, the Rsync sends keep-alive messages to the remote server to prevent a timeout.

We can also configure ssh to prevent timeout by setting a few parameters like KeepAlive, ServerAliveInterval, ServerAliveCountMax, etc.

[Having trouble in fixing Rsync errors? – We’ll help you.]

Conclusion

In short, Rsync error code 12 denotes ‘error in rsync protocol data stream’. Usually, this error occurs due to insufficient disk space, missing Rsync at the destination, idle connection timeout and so on. Today, we saw how our Support Engineers fix this error for our customers.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Comments

Иногда при копировании большого объема и количества файлов по сети с помощью RSYNC может возникнуть некая плохо трактуемая ошибка типа:

rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: connection unexpectedly closed (90241361 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6]

Она может означать что угодно, в том числе и банальное исчерпание свободного места на диске-приемнике.
Но иногда в этом проявляется странный косячок RSYNC, связанный с разделом SWAP.
Борьба с этим недостаточно изученным явлением природы производится следующим образом:

— Перед копированием отключаем использование раздела подкачки:

# swapoff -a

— После копирования возвращаем его во включенное состояние:

# swapon -a

И как ни странно, этот прием иногда помогает.

Хотя потом оказалось, что в подсети, в которой находился этот компьютер, находился другой компьютер с неисправной сетевой картой, которая зафлудила всю сеть лавиной бессмысленных пакетов, и нарушала работу многих других компьютеров и сетевых программ.

Вот тут нашел как сделать отладку при такой ошибке:
samba.anu.edu.au/rsync/issues.html

На удаленном сервере сделал файл rsync-debug:
#!/bin/sh
ulimit -c unlimited
strace -f rsync «${@}» 2>~/tmp/rsync-$$.out

Запустил rsync с опцией —rsync-path=~/rsync-debug

В результате получился файл с отладочной инфой от strace:

execve(«/usr/bin/rsync», [«rsync», «—server», «-e.Lsf», «.», «/home/un1t/tmp/test»], [/* 12 vars */]) = 0
brk(0) = 0x1198000
access(«/etc/ld.so.nohwcap», F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5af6383000
access(«/etc/ld.so.preload», R_OK) = -1 ENOENT (No such file or directory)
open(«/etc/ld.so.cache», O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=43482, …}) = 0
mmap(NULL, 43482, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5af6378000
close(3) = 0
access(«/etc/ld.so.nohwcap», F_OK) = -1 ENOENT (No such file or directory)
open(«/lib/libacl.so.1», O_RDONLY) = 3
read(3, «177ELF2113>136036″…, 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=30472, …}) = 0
mmap(NULL, 2125648, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f5af5f61000
mprotect(0x7f5af5f68000, 2093056, PROT_NONE) = 0
mmap(0x7f5af6167000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7f5af6167000
close(3) = 0
access(«/etc/ld.so.nohwcap», F_OK) = -1 ENOENT (No such file or directory)
open(«/lib/libpopt.so.0», O_RDONLY) = 3
read(3, «177ELF2113>1340″»…, 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=41984, …}) = 0
mmap(NULL, 2137264, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f5af5d57000
mprotect(0x7f5af5d61000, 2093056, PROT_NONE) = 0
mmap(0x7f5af5f60000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x9000) = 0x7f5af5f60000
close(3) = 0
access(«/etc/ld.so.nohwcap», F_OK) = -1 ENOENT (No such file or directory)
open(«/lib/libc.so.6», O_RDONLY) = 3
read(3, «177ELF2113>1`3551″…, 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1432968, …}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5af6377000
mmap(NULL, 3541032, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f5af59f6000
mprotect(0x7f5af5b4e000, 2093056, PROT_NONE) = 0
mmap(0x7f5af5d4d000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x157000) = 0x7f5af5d4d000
mmap(0x7f5af5d52000, 18472, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5af5d52000
close(3) = 0
access(«/etc/ld.so.nohwcap», F_OK) = -1 ENOENT (No such file or directory)
open(«/lib/libattr.so.1», O_RDONLY) = 3
read(3, «177ELF2113>1p24″…, 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=17808, …}) = 0
mmap(NULL, 2112952, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f5af57f2000
mprotect(0x7f5af57f6000, 2093056, PROT_NONE) = 0
mmap(0x7f5af59f5000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7f5af59f5000
close(3) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5af6376000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5af6375000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5af6374000
arch_prctl(ARCH_SET_FS, 0x7f5af6375700) = 0
mprotect(0x7f5af5d4d000, 16384, PROT_READ) = 0
mprotect(0x7f5af6385000, 4096, PROT_READ) = 0
munmap(0x7f5af6378000, 43482) = 0
rt_sigaction(SIGUSR1, {0x41ab20, [], SA_RESTORER|SA_NOCLDSTOP, 0x7f5af5a281e0}, NULL, = 0
rt_sigaction(SIGUSR2, {0x41b450, [], SA_RESTORER|SA_NOCLDSTOP, 0x7f5af5a281e0}, NULL, = 0
rt_sigaction(SIGCHLD, {0x41b4a0, [], SA_RESTORER|SA_NOCLDSTOP, 0x7f5af5a281e0}, NULL, = 0
geteuid() = 1041
umask(0) = 022
brk(0) = 0x1198000
brk(0x11b9000) = 0x11b9000
open(«/usr/lib/locale/locale-archive», O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2942400, …}) = 0
mmap(NULL, 2942400, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5af5523000
close(3) = 0
open(«/usr/etc/popt», O_RDONLY) = -1 ENOENT (No such file or directory)
open(«/etc/popt», O_RDONLY) = -1 ENOENT (No such file or directory)
stat(«/etc/popt.d», 0x7fff5ac491b0) = -1 ENOENT (No such file or directory)
open(«/home/un1t/.popt», O_RDONLY) = -1 ENOENT (No such file or directory)
rt_sigaction(SIGINT, {0x40b0e0, [], SA_RESTORER|SA_NOCLDSTOP, 0x7f5af5a281e0}, NULL, = 0
rt_sigaction(SIGHUP, {0x40b0e0, [], SA_RESTORER|SA_NOCLDSTOP, 0x7f5af5a281e0}, NULL, = 0
rt_sigaction(SIGTERM, {0x40b0e0, [], SA_RESTORER|SA_NOCLDSTOP, 0x7f5af5a281e0}, NULL, = 0
rt_sigprocmask(SIG_UNBLOCK, [HUP INT USR1 USR2 TERM CHLD], NULL, = 0
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER|SA_NOCLDSTOP, 0x7f5af5a281e0}, NULL, = 0
rt_sigaction(SIGXFSZ, {SIG_IGN, [], SA_RESTORER|SA_NOCLDSTOP, 0x7f5af5a281e0}, NULL, = 0
getcwd(«/home/un1t», 4095) = 13
fcntl(0, F_GETFL) = 0 (flags O_RDONLY)
fcntl(0, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
fcntl(1, F_GETFL) = 0x1 (flags O_WRONLY)
fcntl(1, F_SETFL, O_WRONLY|O_NONBLOCK) = 0
fcntl(0, F_GETFL) = 0x800 (flags O_RDONLY|O_NONBLOCK)
fcntl(1, F_GETFL) = 0x801 (flags O_WRONLY|O_NONBLOCK)
select(2, NULL, [1], [1], {60, 0}) = 1 (out [1], left {59, 999997})
write(1, «36», 4) = 4
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {59, 966985})
read(0, «», 4) = 0
write(2, «rsync: connection unexpectedly c»…, 74rsync: connection unexpectedly closed (0 bytes received so far) [receiver]) = 74
write(2, «n», 1
) = 1
rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER, 0x7f5af5a281e0}, NULL, = 0
rt_sigaction(SIGUSR2, {SIG_IGN, [], SA_RESTORER, 0x7f5af5a281e0}, NULL, = 0
write(2, «rsync error: error in rsync prot»…, 88rsync error: error in rsync protocol data stream (code 12) at io.c(600) [receiver=3.0.6]) = 88
write(2, «n», 1
) = 1
select(0, NULL, NULL, NULL, {0, 100000}) = 0 (Timeout)
exit_group(12) =?

Чесно говоря не особо понятно, кроме того что не моет найти какой-то файл /etc/ld.so.nohwcap

rsync -v -v -e 'ssh -p YY' ./testfile me@XXXXX:/home

opening connection using: ssh -p YY -l me 146.6.84.206 rsync ->-server -vvve.s . /home 
[sender] make_file(testfile,*,0)
send_file_list done
send_files starting
server_recv(2) starting pid=17537
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600)[sender=3.0.6]
_exit_cleanup(code=12, file=io.c, line=600): about to call exit(12)

ssh -p YY me@XXXXX

Ответы:

$ rsync -avz public/ static:apps/myapp.com
building file list ... done
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/io.c(453) [sender=2.6.9]

sudo apt-get install rsync

ssh -p YY me@XXXXX /bin/true > out.txt

if [ ! -t 1 ]; then
  echo garbage
fi

rsync -v -v -e '/usr/bin/ssh -p YY' ./testfile me@XXXXX:/home

rsync -e 'ssh -v'

debug1: Exit status 11

rsync error: error in rsync protocol data stream (code 12) at /BuildRoot
/Library/Caches/com.apple.xbs/Sources/rsync/rsync-51/rsync/io.c(453)
[sender=2.6.9]