rsync Troubleshooting Solutions

Trouble shooting
***************************
[Email protected]: Auth failed on module xxxxx
Rsync:connectionUnexpectedly closed (bytes read so far)
Rsync Error:error in Rsync protocol data Stream (code) at IO.C (150)
This is because the password is wrong, unable to log in successfully, please check the password in the RSYNCD.SCRT, the two end is consistent?

2.password file must not being other-accessible
Continuing without password file
Password:
This indicates that the RSYNCD.SCRT file permission property is incorrect and should be set to 600.

3[email protected]: Chroot failed
Rsync:connection unexpectedly closed (bytes read so far)
Rsync Error:error in Rsync protocol data Stream (code) at IO.C (150)
This is usually caused by the directory that is located in the path path of your rsyncd.conf. Please start with mkdir. To back up the directory

[Email protected]: 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 data Stream (code) at IO.C (359)
The last reason was finally found. Because there are two network segments that need to synchronize the contents of the folder, no additional IP segments are added after the hosts allow
Hosts allow = 192.168.1.0/24
Switch
Hosts allow = 192.168.1.0/24 192.168.2.0/24
Restart Rsync service, problem solving

5.rsync:failed to connect to 172.21.50.8:no route to host (113)
Rsync error:error in Socket IO (code ten) at CLIENTSERVER.C (104) [receiver=2.6.9]
The other side does not boot, firewall blocking, through the network has a firewall blocking, it is possible. Shutting down the firewall is actually opening the TCP UDP port 873
Start service: rsync--daemon--config=/etc/rsyncd.conf

[email protected]: Auth failed on Module BACKUP
    Rsync Error:error starting Client-server Protocol (code 5) at MAIN.C (1506) [RECEIVER=3.0.7]
    Client did not set/etc/rsync.pas this file, and when using the rsync command, this parameter was added--PASSWORD-FILE=/ETC/RSYNC.SCRT 

7.rsync:recv_generator:mkdir "/ Teacherclubbackup/rsync ... "Failed:no space left on device
    * * * skipping any contents from this failed directory ***
    disk space is full of  

8.rsync:opendir "/kexue" (in Dtschannel) Failed:permission denied (     Sync directory permissions settings are not correct, instead 755 

9.rsync:read error:connection Reset by peer (104)
    rsync error:error in Rsync protocol data Stream (code) at IO.C (759) [RECEIVER=3.0.5]
    Not started xinetd daemon
    [[email protected]/]# service xinetd start

10.rsync:unable to open configuration file " /etc/rsyncd.conf ": No such file or directory
    Xnetid Find the configuration file location by default is/etc, in/etc cannot find rsyncd.conf file

11.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]
Connection server timed out, check server port NETSTAT–TUNLP, remote Telnet test

12.[[email protected] cron.daily.rsync]# sh root.sh
Error:password file must not being other-accessible
Rsync Error:syntax or usage error (code 1) at AUTHENTICATE.C (175) [receiver=3.0.9]
Create password file, root user is Rsyncroot.password, permission is 600

13. How to do rsync via SSH without entering the password?
There are a few steps you can follow
1. Set up SSH keys on Server A via Ssh-keygen, do not specify the password, you will see the identity and identity.pub files under ~/.ssh
2. Create a subdirectory in the home directory on Server B. SSH
3. Copy the identity.pub of a to Server B
4. Add Identity.pub to ~[user B]/.ssh/authorized_keys
5. As a user on Server A, you can ssh to Server B with User B via the following command. e.g. Ssh-l UserB ServerB. This allows user A on server A to SSH to Server B without a password as User B.

The answers are as follows:
  This usually has two cases, one is the server is inside the firewall, and the other is the server is outside the fire wall. In either case, SSH is usually used, and it is best to create a new backup user, and configure SSHD to allow only this user access via RSA authentication. If the server is inside a firewall, it is better to qualify the client's IP address and deny all other connections. If the client is inside the firewall, you can simply allow the firewall to open the SSH outgoing connection on TCP port 22 OK.

15. Can I back up files that have been changed or deleted?
Of course. You can use such as: Rsync-other-options-backupdir =./backup-2000-2-13 ... Such a command to implement. So if the source file:/path/to/some/file.c changed, then the old file will be moved to./backup-2000-2-13/path/to/some/file.c, this directory needs to be set up by hand.

16. What ports do I need to open on the firewall to accommodate rsync?
Subject to availability. Rsync can transfer files directly over a 873 port TCP connection, or through 22 port SSH, but you can also change its port with the following command:
Rsync--port 8730 otherhost::
Or
Rsync-e ' Ssh-p 2002 ' Otherhost:

17. How can I only copy the directory structure via rsync, ignoring the files?
Rsync-av--include ' */'--exclude ' * ' Source-dir dest-dir

18. Why do I always appear "Read-only file system" error?
See if you forgot to set "Read Only = no"

UID 4294967295 ( -1) is impossible to set on

Add a row of parameters on the server side:

Fake Super = yes

Restart the rsync service. There is no error message in the resynchronization.

This article is from the "Stop fighting = Stop Life" blog, make sure to keep this source http://53cto.blog.51cto.com/9899631/1771826

rsync Troubleshooting Solutions