Problem 1:
@ERROR: chroot failed
rsync error: error starting client-server protocol (code 5) at main.c(1522) [receiver=3.0.3]
Cause:
The directory on the server side does not exist or has incorrect permissions. Create the directory and correct the permissions to fix this issue.
Problem 2:
@ERROR: auth failed on module tee
rsync error: error starting client-server protocol (code 5) at main.c(1522) [receiver=3.0.3]
Cause:
The server-side module (tee) requires username and password authentication, but the client did not provide the correct credentials, resulting in an authentication failure. Providing the correct username and password resolves this issue.
Problem 3:
@ERROR: Unknown module ‘tee_nonexists’
rsync error: error starting client-server protocol (code 5) at main.c(1522) [receiver=3.0.3]
Cause:
The specified module does not exist on the server. Provide the correct module name or modify the server configuration to add the desired module to fix this issue.
Problem 4:
password file must not be other-accessible
continuing without password file
Password:
Cause:
The permissions on rsyncd.pwd or rsyncd.secrets are incorrect; they should be set to 600. For example: chmod 600 rsyncd.pwd
Problem 5:
rsync: failed to connect to 218.107.243.2: No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(104) [receiver=2.6.9]
Cause:
The target host may be powered off, blocked by a firewall, or a firewall on the network path is blocking the connection. Disabling the firewall or opening TCP/UDP port 873 usually resolves this.
Problem 6:
rsync error: error starting client-server protocol (code 5) at main.c(1524) [Receiver=3.0.7]
Cause:
There is an error in the /etc/rsyncd.conf configuration file. Please check and correct the configuration file.
Problem 7:
rsync: chown "" failed: Invalid argument (22)
Cause:
Permissions could not be replicated. Remove the parameter for synchronizing permissions to fix this. (This often occurs when syncing from Linux to Windows.)
This article originates from the “运维IT” blog; please be sure to retain this source http://yanghuawu.blog.51cto.com/2638960/1066278
@ERROR: chroot failed
rsync error: error starting client-server protocol (code 5) at main.c(1522) [receiver=3.0.3]
Cause:
The directory on the server side does not exist or has incorrect permissions. Create the directory and correct the permissions to fix this issue.
Problem 2:
@ERROR: auth failed on module tee
rsync error: error starting client-server protocol (code 5) at main.c(1522) [receiver=3.0.3]
Cause:
The server-side module (tee) requires username and password authentication, but the client did not provide the correct credentials, resulting in an authentication failure. Providing the correct username and password resolves this issue.
Problem 3:
@ERROR: Unknown module ‘tee_nonexists’
rsync error: error starting client-server protocol (code 5) at main.c(1522) [receiver=3.0.3]
Cause:
The specified module does not exist on the server. Provide the correct module name or modify the server configuration to add the desired module to fix this issue.
Problem 4:
password file must not be other-accessible
continuing without password file
Password:
Cause:
The permissions on rsyncd.pwd or rsyncd.secrets are incorrect; they should be set to 600. For example: chmod 600 rsyncd.pwd
Problem 5:
rsync: failed to connect to 218.107.243.2: No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(104) [receiver=2.6.9]
Cause:
The target host may be powered off, blocked by a firewall, or a firewall on the network path is blocking the connection. Disabling the firewall or opening TCP/UDP port 873 usually resolves this.
Problem 6:
rsync error: error starting client-server protocol (code 5) at main.c(1524) [Receiver=3.0.7]
Cause:
There is an error in the /etc/rsyncd.conf configuration file. Please check and correct the configuration file.
Problem 7:
rsync: chown "" failed: Invalid argument (22)
Cause:
Permissions could not be replicated. Remove the parameter for synchronizing permissions to fix this. (This often occurs when syncing from Linux to Windows.)
This article originates from the “运维IT” blog; please be sure to retain this source http://yanghuawu.blog.51cto.com/2638960/1066278