I'm having prolems with cwRsync on server 2003. I'm getting pretty much identical results to this from the archive: http://lists.samba.org/archive/rsync/2004-April/009187.html, and as far as I can see the only suggestion there was to check permissions. I have one further complication too- I'm trying to sync a remote server on to a vmware virtual disk that I've mounted using the tools at http://chitchat.at.infoseek.co.jp/vmware/vdk.html. I've got the package installed and set the upload directory during the install to the virtual disk (V: under windows), and I've checked that the disk is writeable. I've got the service started and here's the config file: **************************************************************** use chroot = false strict modes = false hosts allow = * log file = rsyncd.log pid file = rsyncd.pid # Module definitions # Make sure that writable modules are implemented as subdirectories of <cwRsync installation # directory>\data. That would ensure propagation of correct ownership for files/directories. # [test] path = /cygdrive/c/cwrsync/data read only = false transfer logging = yes [files] path = /cygdrive/v read only = false transfer logging = yes ************************************************************* So I then go to another PC and (either with cwrsync or rsync under manually installed cygwin, or rsync on linux) do the following: ------------------------------------------------------------ $ rsync /some/directory hq-dr01::files @ERROR: chdir failed rsync: connection unexpectedly closed (33 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at /home/lapo/packagi ng/tmp/rsync-2.6.0/io.c(189) ------------------------------------------------------------ And looked in the logfile on the server: 2004/09/30 13:52:28 [500] rsyncd version 2.6.2 starting, listening on port 873 2004/09/30 13:52:52 [176] chdir /cygdrive/v failed : No such file or directory BUT, if I start a cygwin shell on the server machine, I get this: ####################################################################### $ cd /cygdrive/ Administrator@hq-dr01 /cygdrive $ ls -al total 0 dr-xr-xr-x 11 0 root 0 Jan 1 1970 . drwxrwx---+ 9 Administ mkgroup- 0 Sep 30 11:18 .. drwxrwxr-x+ 17 Administ root 0 Sep 28 12:30 c drwxrwxr-x+ 13 Administ SYSTEM 0 Sep 29 11:30 d drwxrwxr-x+ 9 Administ SYSTEM 0 Sep 29 08:41 e drwxrwxr-x+ 9 Administ SYSTEM 0 Sep 27 15:49 f drwxrwxrwx+ 15 Administ root 0 Sep 30 11:41 v drwxr-xr-x 1 Administ mkgroup- 0 Sep 20 11:41 w drwxrwxr-x+ 4 Administ SYSTEM 0 Aug 6 12:20 y Administrator@hq-dr01 /cygdrive $ cd v Administrator@hq-dr01 /cygdrive/v $ ls -al total 818 drwxrwxrwx+ 15 Administ root 0 Sep 30 11:41 . dr-xr-xr-x 11 0 root 0 Jan 1 1970 .. drwxrwxrwx+ 5 Administ ???????? 0 Jun 11 10:13 Audit drwxrwxrwx+ 7 Administ ???????? 0 Sep 15 12:12 CTXHOME d--------- 25 Administ ???????? 0 Sep 29 10:43 Departments d--------- 114 Administ ???????? 0 Sep 29 04:01 Home Folders d--------- 15 Administ ???????? 0 Sep 29 05:43 IT drwxrwxrwx+ 11 Administ ???????? 0 Sep 29 05:47 MTLlive-Backup drwxrwxrwt+ 5 Administ ???????? 0 Sep 29 05:48 Profile drwxrwxrwx+ 16 Administ ???????? 0 Sep 29 08:27 Regional Centres - Repli cated d---rwx--- 2 Administ SYSTEM 0 Sep 29 08:39 System Volume Informatio n drwxrwxrwx+ 4 Administ ???????? 0 Sep 29 08:34 VSR -rwxrwxrwx 1 Administ ???????? 837039 Apr 7 10:28 bootme.exe drwxrwxrwx+ 2 Administ ???????? 0 Sep 30 13:45 cwrsync drwxr-xr-x+ 4 Administ ???????? 0 Sep 29 05:44 msi-packs drwxrwxrwx+ 2 Administ ???????? 0 Sep 30 11:29 windows Administrator@hq-dr01 /cygdrive/v ######################################################################## ######### Can anyone give me any clue as to what's wrong? I'm fairly sure the permissions are ok: at a NT level I've set everyone full control on the writeable area to test it. -- This e-mail may contain confidential and/or privileged information. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), you must not use, distribute, copy or take any action in reliance on it, since to do so is strictly prohibited and may be unlawful. If you have received this e-mail in error, please return it to the sender immediately and delete it from your system. E-mail messages are not secure and attachments may contain software viruses which may damage your system. Whilst we have taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. Any views or opinions expressed in this e-mail are solely those of the author and do not represent those of the NASUWT unless otherwise stated.
Hi, If you use cwRsync as a server, make sure that you set CYGWIN=nontsec as a system environment variable and restart the RsyncServer service. Check FAQ at http://www.itefix.no/phpws/index.php?module=faq&FAQ_op=view&FAQ_id=12. In addition, cwrsync service account must have full access to uploadable directories. If you don't do this, then cygwin manipulates windows ACLs causing unexpectible results. Mapping between unix permissions and windows ACLs is not a simple task. cwRsync (both server and client mode) on windows 2003 works just fine. I recently installed cwRsync 1.2.6 Server (rsync 2.6.3 + cygwin 1.5.11 + openssh 3.9p1) on a 2003 std.edition server and cwrsync client on an XP PC. They work just fine (initial run: 580 MB, 4 000 files, 5 MB/sec throughput). As long as you follow instructions above, cwRsync should work for all drives accessible by cygwin. Rgrds Tev cwRsync maintainer> I'm having prolems with cwRsync on server 2003. I'm getting pretty much > identical results to this from the archive: > > http://lists.samba.org/archive/rsync/2004-April/009187.html, and as far > as I can see the only suggestion there was to check permissions. > > I have one further complication too- I'm trying to sync a remote server > on to a vmware virtual disk that I've mounted using the tools at > http://chitchat.at.infoseek.co.jp/vmware/vdk.html. > > I've got the package installed and set the upload directory during the > install to the virtual disk (V: under windows), and I've checked that > the disk is writeable. > > I've got the service started and here's the config file: > **************************************************************** > use chroot = false > strict modes = false > hosts allow = * > log file = rsyncd.log > pid file = rsyncd.pid > > # Module definitions > # Make sure that writable modules are implemented as subdirectories of > <cwRsync installation # directory>\data. That would ensure propagation > of correct ownership for files/directories. # > [test] path = /cygdrive/c/cwrsync/data > read only = false > transfer logging = yes > [files] > path = /cygdrive/v > read only = false > transfer logging = yes > > ************************************************************* > > So I then go to another PC and (either with cwrsync or rsync under > manually installed cygwin, or rsync on linux) do the following: > > > ------------------------------------------------------------ > $ rsync /some/directory hq-dr01::files > @ERROR: chdir failed > rsync: connection unexpectedly closed (33 bytes read so far) rsync > error: error in rsync protocol data stream (code 12) at > /home/lapo/packagi > ng/tmp/rsync-2.6.0/io.c(189) > ------------------------------------------------------------ > > And looked in the logfile on the server: > > 2004/09/30 13:52:28 [500] rsyncd version 2.6.2 starting, listening on > port 873 2004/09/30 13:52:52 [176] chdir /cygdrive/v failed > : No such file or directory > > > BUT, if I start a cygwin shell on the server machine, I get this: > > > ####################################################################### > $ cd /cygdrive/ > > Administrator@hq-dr01 /cygdrive > $ ls -al > total 0 > dr-xr-xr-x 11 0 root 0 Jan 1 1970 . > drwxrwx---+ 9 Administ mkgroup- 0 Sep 30 11:18 .. > drwxrwxr-x+ 17 Administ root 0 Sep 28 12:30 c > drwxrwxr-x+ 13 Administ SYSTEM 0 Sep 29 11:30 d > drwxrwxr-x+ 9 Administ SYSTEM 0 Sep 29 08:41 e > drwxrwxr-x+ 9 Administ SYSTEM 0 Sep 27 15:49 f > drwxrwxrwx+ 15 Administ root 0 Sep 30 11:41 v > drwxr-xr-x 1 Administ mkgroup- 0 Sep 20 11:41 w > drwxrwxr-x+ 4 Administ SYSTEM 0 Aug 6 12:20 y > > Administrator@hq-dr01 /cygdrive > $ cd v > > Administrator@hq-dr01 /cygdrive/v > $ ls -al > total 818 > drwxrwxrwx+ 15 Administ root 0 Sep 30 11:41 . > dr-xr-xr-x 11 0 root 0 Jan 1 1970 .. > drwxrwxrwx+ 5 Administ ???????? 0 Jun 11 10:13 Audit > drwxrwxrwx+ 7 Administ ???????? 0 Sep 15 12:12 CTXHOME > d--------- 25 Administ ???????? 0 Sep 29 10:43 Departments > d--------- 114 Administ ???????? 0 Sep 29 04:01 Home Folders > d--------- 15 Administ ???????? 0 Sep 29 05:43 IT > drwxrwxrwx+ 11 Administ ???????? 0 Sep 29 05:47 MTLlive-Backup > drwxrwxrwt+ 5 Administ ???????? 0 Sep 29 05:48 Profile > drwxrwxrwx+ 16 Administ ???????? 0 Sep 29 08:27 Regional Centres > - Repli > cated > d---rwx--- 2 Administ SYSTEM 0 Sep 29 08:39 System Volume > Informatio > n > drwxrwxrwx+ 4 Administ ???????? 0 Sep 29 08:34 VSR > -rwxrwxrwx 1 Administ ???????? 837039 Apr 7 10:28 bootme.exe > drwxrwxrwx+ 2 Administ ???????? 0 Sep 30 13:45 cwrsync > drwxr-xr-x+ 4 Administ ???????? 0 Sep 29 05:44 msi-packs > drwxrwxrwx+ 2 Administ ???????? 0 Sep 30 11:29 windows > > Administrator@hq-dr01 /cygdrive/v > > ######################################################################## > ######### > > Can anyone give me any clue as to what's wrong? I'm fairly sure the > permissions are ok: at a NT level I've set everyone full control on the > writeable area to test it. > > -- > > This e-mail may contain confidential and/or privileged information. It is > for the exclusive use of the intended recipient(s). If you are not the > intended recipient(s), you must not use, distribute, copy or take any > action in reliance on it, since to do so is strictly prohibited and may be > unlawful. If you have received this e-mail in error, please return it to > the sender immediately and delete it from your system. E-mail messages are > not secure and attachments may contain software viruses which may damage > your system. Whilst we have taken every reasonable precaution to minimise > this risk, we cannot accept any liability for any damage which you sustain > as a result of these factors. You are advised to carry out your own virus > checks before opening any attachment. Any views or opinions expressed in > this e-mail are solely those of the author and do not represent those of > the NASUWT unless otherwise stated. > > -- > To unsubscribe or change options: > http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html >
Hi Tev, Thanks for the reply. That didn't help straight away, but I do have rsych half working now, and thought this might be useful/interesting. It seems there's something odd about mounted vmware disks, umless there's something I'm missing- they don't seem to always be available properly outside of the command prompt that mounted them- this seems the same with the vmware tools or the ones at Ken Kato's pages (http://chitchat.at.infoseek.co.jp/vmware/vdk.html). What I did was this: Stop the cwRsync service in admin tools. Start a command prompt running as the cwrsync service account by using RunAs. Mount the vmware drive from this command prompt. Run cygwin and check the drive is visible *from in this command prompt* Manually run the rsync server- 'rsync --config rsyncd.conf --daemon --no-detach'. When I do this it works fine. Unless anyone can suggest anything better I'll create a script to mount the drive and then start the server rather than using the supplied srvany solution, but if anyone can suggest any alternatives I'd appreciate it. Once again, thanks for the response. Much appreciated :-) Regards Chris Bartram -----Original Message----- From: tevfik@itefix.no [mailto:tevfik@itefix.no] Sent: Monday, October 04, 2004 1:04 PM To: Chris Bartram [IT Department] Cc: rsync@lists.samba.org Subject: Re: cwRsync- chdir failed, server 2003 Hi, If you use cwRsync as a server, make sure that you set CYGWIN=nontsec as a system environment variable and restart the RsyncServer service. Check FAQ at http://www.itefix.no/phpws/index.php?module=faq&FAQ_op=view&FAQ_id=12. [snip] [snip]> I have one further complication too- I'm trying to sync a remote > server on to a vmware virtual disk that I've mounted using the tools > at http://chitchat.at.infoseek.co.jp/vmware/vdk.html. >-- This e-mail may contain confidential and/or privileged information. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), you must not use, distribute, copy or take any action in reliance on it, since to do so is strictly prohibited and may be unlawful. If you have received this e-mail in error, please return it to the sender immediately and delete it from your system. E-mail messages are not secure and attachments may contain software viruses which may damage your system. Whilst we have taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. Any views or opinions expressed in this e-mail are solely those of the author and do not represent those of the NASUWT unless otherwise stated.