by Devin Yang
(This article was automatically translated.)

Published - 9 years ago ( Updated - 9 years ago )

All rsync error codes are listed here, so in scheduling, we can understand the reason for the failure.
Example: 9979 [22/Jan/2017:12:46:11] /usr/bin/rsnapshot hourly: ERROR: /usr/bin/rsync returned 11 while processing

0 Success
1 Syntax or usage error
2 Protocol incompatibility
3 Errors selecting input/output files, dirs
4 Requested action not supported: an attempt was made to manipulate 64-bit
files on a platform that cannot support them; or an option was specified
that is supported by the client and not by the server.
5 Error starting client-server protocol
6 Daemon unable to append to log-file
10 Error in socket I/O
11 Error in file I/O
12 Error in rsync protocol data stream
13 Errors with program diagnostics
14 Error in IPC code
20 Received SIGUSR1 or SIGINT
21 Some error returned by waitpid()
22 Error allocating core memory buffers
23 Partial transfer due to error
24 Partial transfer due to vanished source files
25 The --max-delete limit stopped deletions
30 Timeout in data send/receive
35 Timeout waiting for daemon connection

Tags: linux

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Similar Stories


linux

The old version of CentOS 6.2 compiles the git process

This article uses CentOS 6.2 to rebuild curl and git. The main reason is that the operating system is too old, so I directly build the latest version of git from source.

linux,system,config

Fix the problem that CentOS6.x can no longer be updated

There may still be some old programs in some places, which can only run the old system. But you want to be able to execute and install some desired packages, you may try this method. Please note that if this system is important to you, please evaluate it yourself. It is recommended that you have a Docker environment and have a backup image before trying it.

linux

How rsync automatically allows ssh key fingerprints

When we use ssh to connect to the host for the first time, a fingerprint confirmation of the host key will be displayed. Sometimes use rsync for some automated scheduling, maybe the remote host has changed and needs to be automatically allowed, How to let ssh automatically allow fingerprints to connect without manually pressing yes in interactive mode?