Rsync:failed to set time on "xxxx" in rsync sync: Operation not permitted_ server other

Today, when synchronizing the data, prompt rsync:failed to set time on "xxxx": Operation is not permitted, generally speaking, if it is not the server time is incorrect or the permissions are not set, the following cloud Habitat Community Small series for everyone to organize some information

The first method:

The "XXXX" appears on the rsync:failed to set "s": Operation not permitted is largely due to the lack of operation permissions on the folder (or file) xxxx. If the user performing the synchronization is root, there is no such problem, but rsync can also not use the root user to synchronize, without using the root user, even if the use of-o,-g, synchronization to the destination folder files users and groups have become synchronized users, However, file permissions can be retained with-p. When the destination folder (or file) xxxx after the modification so that owner is not rsync users, even if the permissions of XXXX is 777, the above error will occur.

The second method:

When I use Rsync synchronization, from my local machine to the remote server machine, sync error, prompted
Rsync:failed to set times on ' directory ' Operation not permitted (1)
Where directory is a directory on the remote target server.

The problem is that, because of the UID, GID problem that you specify in the/etc/rsync.conf file, you synchronize the directory to which the file is to be written, and his or her group is/etc/rsync.conf the UID and GID specified in the file.
This will not rsync:failed errors like the To set times on!

(1) Before the modification, rsync pushed the file to the target server error:

(2) to the target server to view/etc/rsync.conf files, see UID and GID are respectively:

(3) Then according to the configuration file, the target directory of the targeted server, the Chown directory of the owners and groups

After the above settings, OK, sync is normal:

Method Three

Rsync:failed to set times on "/." (in module): Operation not permitted (1)

This is rsyncd.conf inside read Only = No logoff is not possible, because the default value is Yes

Method Four under Windows is typically caused by incorrect server-side directory permissions. In general, Svccwrsync users need to join the synchronization directory and give all the permissions or set Svccwrsync as Administrator rights (it is best to disable Svccwrsync this user from remote logins).

Cloud-dwelling Community Small note: If you change the permissions of something, you need to restart the Rsync service. The test solves the problem perfectly.