From: Kris B. <Kri...@sc...> - 2004-10-26 22:25:17
|
To answer my own question, it had something to do with a cygwin-related symlink on the Win2k host. Running rsyncd on the source machine using: C:\PROGRA~1\RSync>rsync --config=c:/progra~1/rsync/rsyncd.conf --daemon --no-detach -vvv and then tailing rsyncd.log showed: .... 2004/10/26 11:11:45 [2032] send UNKNOWN [192.168.16.220] cDrive (UUU) cygwin/usr/doc/swig-1.3.19/NEW 8848 2004/10/26 11:11:45 [2032] send UNKNOWN [192.168.16.220] cDrive (UUU) cygwin/usr/doc/swig-1.3.19/README 11623 2004/10/26 11:11:45 [2032] send UNKNOWN [192.168.16.220] cDrive (UUU) cygwin/usr/doc/swig-1.3.19/TODO 14088 2004/10/26 11:11:45 [2032] send UNKNOWN [192.168.16.220] cDrive (UUU) cygwin/usr/doc/swig-1.3.19/swig-1.3.19-1.README 3235 2004/10/26 11:11:45 [2032] send UNKNOWN [192.168.16.220] cDrive (UUU) cygwin/usr/include/Dbg.h 1678 2004/10/26 11:11:45 [2032] send UNKNOWN [192.168.16.220] cDrive (UUU) cygwin/usr/include/FlexLexer.h 5822 {ctrl-c of rsyncd after a long period of no activity...} 2004/10/26 11:14:21 [2032] rsync: connection unexpectedly closed (471430 bytes received so far) [sender] 2004/10/26 11:14:21 [2032] rsync error: error in rsync protocol data stream (code 12) at io.c(359) 2004/10/26 11:14:21 [2032] rsync: writefd_unbuffered failed to write 76 bytes: phase "unknown" [sender]: Software caused connection abort (113) 2004/10/26 11:14:21 [2032] rsync error: error in rsync protocol data stream (code 12) at io.c(909) 2004/10/26 11:25:22 [328] rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(231) 2004/10/26 11:25:22 [328] _exit_cleanup(code=20, file=rsync.c, line=231): about to call exit(20) Every time it was tried the transfer would always get stuck at the same point. Looking in that directory on the source with Cygwins 'ls -la' showed: ... -rw-r--r-- 1 Administ None 1678 Jan 28 2003 Dbg.h -rw-r--r-- 1 Administ None 5822 Sep 25 2003 FlexLexer.h lrwxrwxrwx 1 Administ None 20 Oct 23 16:12 X11 -> ../X11R6/include/X11 lrwxrwxrwx 1 Administ None 20 Oct 23 16:12 X11 -> ../X11R6/include/X11 ... Which is very odd to say the least. Removing 'X11' (on a hunch) produced: C:\cygwin\usr\include>rm X11 C:\cygwin\usr\include>ls -la | grep ">" lrwxrwxrwx 1 Administ None 22 Jan 21 2004 X11 -> /usr/X11R6/include/X11 Stranger still. Removing it again: C:\cygwin\usr\include>rm X11 C:\cygwin\usr\include>ls -la | grep ">" C:\cygwin\usr\include> After which the backup was tried again and all worked just fine. For what it's worth the Win2k volume in question passed a chkdisk with flying colours even before the offensive symlink was removed. Hope this helps someone in the future... > -----Original Message----- > From: Kris Boutilier [mailto:Kri...@sc...] > Sent: October 25, 2004 4:08 PM > To: bac...@li... > Subject: [BackupPC-users] Backuppc 2.1.0-5 silently hangs > backing up one > particular server using rsync? > > > I have recently installed backuppc on Debian using their bundled apt > package. It has been working fine for me backing up a mixture > of Windows and > Linux hosts. I recently added an additional server to the mix > and it just > silently dies after about 1.5hrs. Checking the processes I see: > > asterix:/mnt/md0/var/lib/backuppc/pc/morpheus.secure.scrd.bc.c > a# ps auxf | > grep back > backuppc 194 0.0 0.0 7332 5572 ? S 12:15 > 0:01 /usr/bin/perl > /usr/share/backuppc/bin/BackupPC -d > backuppc 197 0.2 0.0 6384 4580 ? S 12:15 0:29 \_ > /usr/bin/perl /usr/share/backuppc/bin/BackupPC_trashClean > backuppc 687 0.5 0.0 0 0 ? Z 14:45 0:19 \_ > [BackupPC_dump] <defunct> > backuppc 697 17.0 0.4 35548 33624 ? S 14:53 > 9:06 /usr/bin/perl > /usr/share/backuppc/bin/BackupPC_dump -f morpheus.secure.scrd.bc.ca > > I'm a little concerned about the zombied process, but it > doesn't seem to be > related directly to the rsync process... The percentage CPU > time seems to > suggest work is being done on the server, but the client > shows no work being > done by the process on that side. I'm using cygwin/rsync-2.6.3 on the > client side and am running the exact same rsync executable > successfully on > other Win2k hosts that are backing up fine. To test the rsync > processes I > have successfully run a native rsync-client backup from the > server using: > {clip} |