Rsync server troubleshooting

Rsync server troubleshooting

Rsync server troubleshooting

1. Check whether the rsync service configuration file path is correct. The correct default path is/etc/rsyncd. conf.
2. Check whether the IP address CIDR Block allowed by the client is the IP address CIDR Block allowed by the host allow and host deny in the configuration file.
3. Check whether the path in the path parameter in the configuration file exists and whether the permission is correct (normally the owner and group corresponding to the UID parameter in the configuration file)
4. Check whether the rsync service is started. The command is PS-Ef | grep rsync. Check whether the port has netstat-lnt | grep 873
5. Check whether the iptables firewall and SELinux are enabled to allow the rsync service to pass through. You can also consider the intersection
6. Check whether the password file configured by rsync on the server is 600 and the password file format is correct.
7. To push data, check whether the user in the rsyncd. conf file has the read/write permission on the directory under the module.

 

 

Rsync client troubleshooting

1. Check whether the password file configured by rsync on the client has the 600 permission and the password file format is correct. Note: you only need a password, which is consistent with the password on the server.
2. Use telnet to connect to port 873 of the rsync server IP address and check whether the service is started (you can test whether the server firewall is blocked ). Telnet 192.168.1.111 873
3. The client executes the rsync-avzrtopgp command.[Email protected]: Dingjian/test // test/-- password-file =/etc/rsync. Password

Note the details of this command, especially the double colon at 192.168.1.111: Dingjian/test/and the Dingjian following it as the module name.

Rsync server troubleshooting