Rsync synchronization error handling

Rsync synchronization error handling

Rsync synchronization error handling

1. incorrect user password

@ERROR: auth failed on module testrsync error: error starting client-server protocol (code 5) at main.c(1503) [receiver=3.0.6]

Check whether server A stores the password file and server B password file.
Server A password file:/etc/rsyncd. secrets format: username: password
Server B password File:/etc/rsyncd. secrets format: password

2. Occupied Rsync Port

rsyncd version 3.0.6 starting, listening on port 873bind() failed: Address already in use (address-family 2)socket(10,1,6) failed: Address family not supported by protocolunable to bind any inbound sockets on port 873rsync error: error in socket IO (code 10) at socket.c(541) [receiver=3.0.6]

Check whether the port is occupied

> lsof -i：873

3. The Rsync service is not started properly.

rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [generator=2.6.9]rsync error: received SIGUSR1 (code 19) at main.c(1182) [receiver=2.6.9]

Note: Most of the reasons for this problem are that the server service is not started properly. Go to the server and check whether the service is started. Then, check/var/run/rsync. if the pid file exists, the simplest way is to kill the started service, then start the service again, or add the script to the system startup service level, and then shutdown the-r now server.

Rsync + inotify implement real-time synchronization and backup of Git data

Rsync for file backup Synchronization

Rsync synchronizes two servers

Remote synchronization of Rsync in CentOS 6.5

Use Rsync in Ubuntu Linux for data backup and Synchronization

Linux uses the Rsync client to synchronize directories with the server for backup

Rsync details: click here
Rsync: click here

This article permanently updates the link address: