We have just loaded and begun testing 2.0.4 on a Windows XP (sp1) workstation. The client we are testing with is a Novell Netware 6.5 server running the rsync port.
We have only done preliminary testing, but it seems to sync fine to both the internal hard drive and a firewire attached external drive, however, we have an interesting issue when trying to sync to a NAS which is mounted as a drive letter on the XP box.
If we start rsync as a Windows servers rsync to the NAS failes with the following error: "@ERROR: chdir failed". We have tried changing from ntsec to nontsec, but this did not seem to have any effect.
However, if we stop the service, open the bash prompt and start rsync from the command line using "rsync --daemon --verbose --config=rsyncd.conf" it works fine when syncing to the NAS which raises three questions:
1) Is there a reason it would work one way and not the other?
2) Is there a way to make it work as a windows service?
3) If not, what is the best way to automate starting the service from the bash prompt under windows?
Thanks!
The windows service representing rsync daemon runs under the service account SvcwRsync. You have to make sure that this account has change rights on your NAS-mounted directory, to be able to change directories, copy files and so on.
When you start rsync daemon from the bash prompt, it's been run by the current user, who seems to have required rights on the remote directory.
Tev,
Thanks for the idea. I thought this might be the case as well so I changed the local security policy to allow SvcwRsync to log into the local machine (i.e. removed the user from "deny log in locally"...), then logged into the local machine as SvcwRsync.
Again if I start rsync as a windows service I get the "@Error: chdir failed", however, if I stop the service, start the Bash prompt and start the daemon from there the communication proceeds.
Given this it *seems* like it must be some difference between the way it is run as a windows service vs. from the bash prompt.
Any other ideas would be appreciated.
Thanks again!
dt
what rsync command do you use ?
To start from the bash prompt: rsync --daemon --verbose --config=rsyncd.conf
To start from the bash prompt:
rsync --daemon --verbose --config=rsyncd.conf
Sorry, I meant rsync command you use for synchronization from Novell to NAS through XP.
D'oh!
rsync -v -ra --volume=sys: etc/ 10.113.11.36::nas1 --logfile=sys:/rsync1.conf
The logfile should have read: rsync1.log
Tev,
Thanks for the idea. I thought this might be the case as well so I changed the local security policy to allow SvcwRsync to log into the local machine (i.e. removed the user from "deny log in locally"...), then logged into the local machine as SvcwRsync.
Again if I start rsync as a windows service I get the "@Error: chdir failed", however, if I stop the service, start the Bash prompt and start the daemon from there the communication proceeds.
dt
What I wonder how you regulate access to your NAS-box. Is it an NTFS-system or something else ? SvcwRsync is a local account on your XP and cannot get access to network drives. The solution can be to start RsyncServer service under a domain account and give this account access to your NAS if possible!
I believe the NAS (Buffalo Terrastation)is running a version of Windoze. It has a nice web interface to create users and give them rights...
I am trying your suggestion to use a domain account, but I am having trouble getting the RsyncServer service to start under the account I created - service goes into a "starting" state, but never starts and eventually yields a time out.
Is there any documentation for the steps required to start RsyncServer as a service under a different account? I gave the account rights to run as a service, and ran the setperms.cmd using the new account name instead of the SvcwRsync, but it seems to hang while starting the service.
Thanks again for all of your suggestions.
Tev,
We have a similar issue as dt had. We installed cwRsync_2.1.3 on XP (sp2) and cwRsync_Server_2.1.3 on another XP (sp2). We mapped the network share to drive letter ‘n’ on the server XP box. We replaced the service account SvcwRsync with a user’s account which has the full rights on the network share.
The command we run on the client XP box is:
Rsync –ravzu “/cygdrive/c/work” IPAddress_Server_Box::test2
We get the following error: “@ERROR: chdir failed”.
However, as in dt’s case, if we stop the service and start rsync from the command line using “rsync --daemon --verbose --config=rsyncd.conf”, it works fine. The problem with this daemon method is that we need to keep the server XP box logged on with that user’s account. Would you please help us to identify the problem we have with the windows service method?
Thanks!
SM
This is my rsyncd.conf file
use chroot = false
strict modes = false
hosts allow = *
log file = rsyncd.log
pid file = rsyncd.pid
# Module definitions
# Remember cygwin naming conventions : c:\work becomes /cygwin/c/work
#
path = /cygdrive/n
read only = false
transfer logging = yes
Is the user you use as the service account a local user. In that case, access to network drive is not allowed.