rsync@ERROR: chdir failed's solution

CwRsyncServer encountered this problem on the windows server:

@ERROR: chdir failed
rsync error: error starting client-server protocol (code 5) at main.c(1495) [rec
eiver=3.0.2]

Permission questions:

1) create a new directory for example, enter the start menu > cwRsync Server > Prep a Dir for Upload, select D:\folder1, ok
2) right click on the folder1 folder to enter the properties > Security, "add" the user, enter the object name Svcwrsync, and set the permissions of Svcwrsync to all allow.

Enhance user rights:

If the security requirements are not very high, more directories can be promoted to Svcwrsync administrator rights, 1 set the configuration limit for ip to synchronize files.

ps: after modifying rsyncd.conf, the RsyncServer service must be restarted to take effect

Reason 3. Check whether there is something wrong with the directory. This is that the d and e are not synchronized due to the wrong characters

linux server:

System platform: RHEL 5.3
Client:
[root@test1 ~]# rsync -vzrtopg --progress --delete --password-file=/etc/rsyncd.pwd marsaber@10.10.10.3::backup /var/www/html
@ERROR: chdir failed
rsync error: error starting client-server protocol (code 5) at main.c(1296) [sender=2.6.8]

Server log (/ var/log rsyncd log) :
rsync: chdir /backup failed: Permission denied (13)

Causes and solutions:
SELinux;

setsebool -P rsync_disable_trans on

error summary:

@ERROR: chdir failed
rsync error: error starting client-server protocol (code 5) at main.c(1296) [receiver=2.6.8]
Causes and solutions:
This 1 is usually not created on the server side
Or if you have SELinux on just execute 1 command
SELinux;
setsebool -P rsync_disable_trans on

Remember: rsyncd.secrets must have permissions of 600
(note: this security setting is important and will prompt the client when it connects to the server if it does not:
password file must not be other-accessible
rsync error: some files could not be transferred (code 23) at main.c(1298) [generator=2.6.8]
@ERROR: auth failed on module
rsync: connection unexpectedly closed (102 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165)
Server-side logs will display an error:
2005/08/23 06:32:01 [8388] secrets file must not be other-accessible (see strict modes option)
2005/08/23 06:32:01 [8388] continuing without secrets file
2005/08/23 06:32:01 [8388] auth failed on module from documentserver
rsyncd.secrets (user: password) < The user must be the system user, password should not be the system user password >
rsyncd.secrets (password) < Server-side password >
The server and client account passwords must not have Spaces, otherwise they will appear
@ERROR: auth failed on module
Note:
If the port number is changed,1 must change the corresponding port in /etc/services to function properly

As rsync 873/tcp
3334 / rsync tcp can
error3:
rsyncd.secrets password 1 must be the same as the password 1 in the Rsync Server password Settings file. If it is different (as is not the case with linux legal user error 1), the following error will occur:
#rsync -azv /home rsync://root@192.168.1.107/hadoop --password-file=/home/rsyncd.secrets
@ERROR: auth failed on module hadoop
rsync error: error starting client-server protocol (code 5) at main.c(1296) [sender=2.6.8]
error4:
Problems encountered on client:
rsync -auzv --progress --password-file=/etc/rsync.pas root@192.168.133.128::backup /home/
rsync: could not open password file "/etc/rsync.pas": No such file or directory (2)
Password:
@ERROR: auth failed on module backup
rsync error: error starting client-server protocol (code 5) at main.c(1506) [Receiver=3.0.7]
This problem was encountered: client did not set /etc/ rsync.pas, but added this parameter when using the rsync command
password-file=/etc/rsync.pas

error5:
rsync -auzv --progress --password-file=/etc/rsync.pas root@192.168.133.128::backup /home/
@ERROR: chdir failed
rsync error: error starting client-server protocol (code 5) at main.c(1506) [Receiver=3.0.7]
This problem is encountered because the directory backup is not set on the server side /home/backup, so chdir failed is indicated
error6:
rsync: write failed on "/home/backup2010/wensong": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7]
rsync: connection unexpectedly closed (2721 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7]
Not enough disk space to operate.
Available and used space can be viewed through df /home/backup2010
error7:
1. Authority issues
Note: rsync: opendir "/kexue" (in dtsChannel) failed: Permission denied (13) check to see if the synchronized directory permission is 755
2, time out
rsync: failed to connect to 203.100.192.66: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.5]
Check the server port netstat, tunlp, remote telnet test.
3. The service is not started
rsync: failed to connect to 10.10.10.170: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.5]
Startup service: rsync --daemon --config=/etc/ rsyncd.conf
4. Disk space is full
rsync: recv_generator: mkdir "/ teacherclubBackup rsync..." failed: No space left on device (28)
*** Skipping any contents from this failed directory ***
5. Ctrl+C or a large number of files
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(544) [receiver=3.0.5]
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(544) [generator=3.0.5]
6. xnetid startup (linux)
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(759) [receiver=3.0.5]