Rsync common Errors and Solutions collation _ server Other

We're all looking through the error log.
Inside the Rsyncd.log or the. err file, you can open the view with Notepad.

Note that under Windows we need to give svcwrsync users the ability to manage all the permissions on the sync directory, basically.

Question one:
@ERROR: Chroot failed
Rsync Error:error starting Client-server Protocol (code 5) at MAIN.C (1522) [receiver=3.0.3]

Reason:
The server-side directory does not exist or does not have permissions, creating a directory and correcting permissions resolves the problem.

Question two:
@ERROR: Auth failed on module tee
Rsync Error:error starting Client-server Protocol (code 5) at MAIN.C (1522) [receiver=3.0.3]

Reason:
The server side of this module (TEE) needs to authenticate the username password, but the client does not provide the correct username password, authentication failed.
Provide the correct username password to resolve this issue.

Question three:
@ERROR: Unknown module ' tee_nonexists '
Rsync Error:error starting Client-server Protocol (code 5) at MAIN.C (1522) [receiver=3.0.3]

Reason:
The specified module does not exist on the server. Provide the correct module name or modify the server side to the module you want to solve the problem.


Question 1:
Encountering problems on the client:
Rsync-auzv--progress--password-file=/etc/rsync.pas root@192.168.133.128::backup/home/
Rsync:could not open password file "/etc/rsync.pas": No such file or directory (2)
Password:
@ERROR: Auth failed on module backup
Rsync Error:error starting Client-server Protocol (code 5) at MAIN.C (1506) [receiver=3.0.7]
This problem was encountered: The client side did not set/etc/rsync.pas this file, and when using the rsync command, this parameter was added--
Password-file=/etc/rsync.pas

Question 2:
Rsync-auzv--progress--password-file=/etc/rsync.pas root@192.168.133.128::backup/home/
@ERROR: Auth failed on module backup
Rsync Error:error starting Client-server Protocol (code 5) at MAIN.C (1506) [receiver=3.0.7]
Encountered this problem: Client side has set/etc/rsync.pas this file, inside also set the password 111111, and server consistent, but
Server segment settings have errors, the server should be set/etc/rsync.pas, the contents of the root:111111, where the landing name is indispensable

Question 3:
Rsync-auzv--progress--password-file=/etc/rsync.pas root@192.168.133.128::backup/home/
@ERROR: ChDir failed
Rsync Error:error starting Client-server Protocol (code 5) at MAIN.C (1506) [receiver=3.0.7]
This problem is due to server-side/home/backup where backup is not set up in this directory, so prompt: ChDir failed

Question 4:
Rsync:write failed on "/home/backup2010/wensong": No spaces left on device (28)
rsync error:error in file IO (code one) at RECEIVER.C (302) [receiver=3.0.7]
Rsync:connection unexpectedly closed (2721 bytes received so far) [generator]
Rsync Error:error in Rsync protocol The data Stream (code) at IO.C (601) [generator=3.0.7]
There is not enough disk space to operate.
You can view free and used space through df/home/backup2010

Problem 5: Network collection issues
1, Permission issues
A hint similar to the following: Rsync:opendir "/kexue" (in Dtschannel) Failed:permission denied (13) notice whether the directory permissions for the synchronization are 755
2, Time Out
rsync:failed to connect to 203.100.192.66:connection timed out (110)
Rsync error:error in Socket IO (code ten) at CLIENTSERVER.C (124) [receiver=3.0.5]
Check the server's port NETSTAT–TUNLP, remote Telnet test.
You may be able to set rules to release rsync (873 ports) or shut down the firewall directly, possibly because the client or the server-side firewall is open to prevent communication.

There is also a synchronization process may be prompted without permissions (the synchronization directory plus svcwrsync full permissions, the simpler way is to set the Svcwrsync as an administrator)


3. Service not Started
rsync:failed to connect to 10.10.10.170:connection refused (111)
Rsync error:error in Socket IO (code ten) at CLIENTSERVER.C (124) [receiver=3.0.5]
Start service: rsync--daemon--config=/etc/rsyncd.conf
4. Full disk space
Rsync:recv_generator:mkdir "/teacherclubbackup/rsync ..." failed:no spaces left on device (28)
Skipping any contents from this failed directory * * *
5, CTRL + C or a large number of documents
Rsync error:received SIGINT, Sigterm, or Sighup (code) at RSYNC.C (544) [receiver=3.0.5]
Rsync error:received SIGINT, Sigterm, or Sighup (code) at RSYNC.C (544) [generator=3.0.5]
Description: Most of the problem is that the service-side service is not started normally, go to the server to check whether the service has started, and then see if the next/var/run/rsync.pid file exists, the most simply way is to kill has started the service, Then start the service again or have the script join the System boot service level and Shutdown-r now server

6, Xnetid start
Rsync:read error:connection Reset by Peer (104)
Rsync Error:error in Rsync protocol The data Stream (code) at IO.C (759) [receiver=3.0.5]
View Rsync logs
Rsync:unable to open configuration file "/etc/rsyncd.conf": No such file or directory
The Xnetid Lookup profile location defaults to/etc, creating soft links based on specific circumstances. For example:
Ln-s/etc/rsyncd/rsyncd.conf/etc/rsyncd.conf
or change the specified default profile path, in the/etc/xinetd.d/rsync configuration file.

Rsync Configure:
Configuration one:
Ignore errors
Description: This option is best to add, otherwise many crontab often occur when mistakes you also do not know, because you can not see every day to see the log, not to add this error probability is very high, because any large project and system, disk IO is a bottleneck

Rsync Error:
Error One:
@ERROR: Auth failed on module xxxxx
Rsync:connection unexpectedly closed (bytes read so far)
Rsync Error:error in Rsync protocol The data Stream (code) at IO.C (150)
Description: This is because the password is set incorrectly, can not login successfully, check the rsync.pwd, the spectator suit whether match. This is also the case with the server-side failure to start the rsync service.

Error Two:
Password file must not is other-accessible
Continuing without password file
Password:
Description: This is because the Rsyncd.pwd rsyncd.sec permissions are not correct and should be set to 600. such as: chmod rsyncd.pwd

Error Three:
@ERROR: Chroot failed
Rsync:connection unexpectedly closed (bytes read so far)
Rsync Error:error in Rsync protocol The data Stream (code) at IO.C (150)
Description: This is because the path path you set in rsync.conf does not exist and you want to create a new directory to open synchronization

Error Four:
rsync:failed to connect to 218.107.243.2:no route to host (113)
Rsync error:error in Socket IO (code ten) at CLIENTSERVER.C [receiver=2.6.9]
Description: Firewall problem, this is best to completely shut down the firewall, the Basic Law is wrong, whether it is S or C, there are ignore errors option problems will also cause

Error Five:
@ERROR: Access denied to www. from unknown (192.168.1.123)
Rsync:connection unexpectedly closed (0 bytes received so far) [receiver]
Rsync Error:error in Rsync protocol The data Stream (code) at IO.C (359)
Description: This problem is obvious, is the configuration option host allow problem, beginners like a allow segment to make a configuration, and then the module is the same, resulting in

Error Six:
Rsync error:received SIGINT, Sigterm, or Sighup (code) at RSYNC.C (244) [generator=2.6.9]
rsync error:received SIGUSR1 (code) at MAIN.C (1182) [receiver=2.6.9]
Description: Most of the problem is that the service-side service is not started normally, go to the server to check whether the service has started, and then see if the next/var/run/rsync.pid file exists, the most simply way is to kill has started the service, Then start the service again or have the script join the System boot service level and Shutdown-r now server

Error Seven:
Rsync:read error:connection Reset by Peer (104)
Rsync Error:error in Rsync protocol The data Stream (code) at IO.C (604) [sender=2.6.9]
Description: No data exists in the original data directory