From: Craig B. <cba...@us...> - 2006-11-02 01:41:23
|
PJ writes: > I currently have backuppc 2.1.2pl2 installed on a FC4 machine. It has b= een > happily backing up 2 XP machines and 2 Linux boxes for ~2 years now. A= ll > the clients have various versions rsync running in daemon mode (not ove= r > ssh). >=20 > About 2 weeks ago backups to one of the XP machines started to fail. >=20 > Rsync on the client that is failing is version 2.6.6 from the most rece= nt > cygwin distribution and it's installed as a service. >=20 > backuppc can still connect to the machine, and the backup proceded norm= ally > for about 3 hours. Then it just hangs: BackupPC_dump is idle but st= ill > connected to the client. Rsync on the client is idle and still connect= ed to > the server. There is a zombie BackupPC_dump process sitting there. >=20 > Backupps to all other machines work fine. >=20 > I have the timeout set to 10+ hours so its not that. > I have tried older versions of rsync on the client (2.3.3) and see the s= ame > problem. > This stared with backuppc version 2.1.1. I upgrade to to 2.1.2pl2 to= see > if that would fix it. >=20 > Failure of the backups coincide with a couple of LARGE software package= s > getting installed on the XP box (an increase of about ~20GB total) plus= an > update to cygwin. >=20 > Running 'BackupPC_dump -v -f ack-xp' manually, and after about 100MB of= > output the process segfaults. (I have $Conf{XferLogLevel} =3D 9;) The= > background process appears to be continuing to run as its eating CPU an= d a > ls -alR in the "new" directory shows continued progress. There's just= no > more logging output. >=20 > After a couple of hours of trolling around the location that the backup= > fails (/cygwin/lib/pkgconfig/blah..) I notice 2 COPIES of the terminfo > symlink in c:/cygwin/lib. Both symlinks have the same date, time, name= , > permisions and target. Removing one of them FIXES my problem. >=20 > I cannot recreate the problem because cygwin won't let me create 2 syml= inks > with the same name (as it shouldn't), leaving me with no way to actuall= y > figure out what is wrong in the Rsync/Backuppc. I have no idea how the= > extra link got there in the first place. >=20 > The ISSUE is: backuppc is failing VERY silently when this happens. > Something somewhere isn't dealing with 2 files in the same directory, w= ith > the same name, gracefully. >=20 > Just my $0.02. I want to get this in the archive in case someone else s= ees > the same problem... I could save them several hours trying to diagnose t= he > problem. Thanks to Mark Weaver this problem has been fixed. I hope to release File-RsyncP-0.66 this weekend with his fixes plus a couple of others. Craig |