RE: Rsync transfer getting interrupted

> -----Original Message-----
> From: backuppc-users-admin@xxxxxxxxxxxxxxxxxxxxx 
> [mailto:backuppc-users-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Darryl Cording
> Sent: Tuesday, February 22, 2005 3:26 PM
> To: backuppc-users@xxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [BackupPC-users] Rsync transfer getting interrupted
> 
> Hi,
> Ty Christensen wrote:
> > On one of my hosts, I'm having constant problems trying to 
> complete a 
> > full or incremental backup run.  I always get these 
> messages in the log:
> >  
> First up, I'm new to backuppc, which I think is a great piece 
> of software btw, so I hope I don't lead you astray.
> 

I'll watch my step.  :^)

> I had a similar problem recently. One of the backups just 
> kept erroring out at the same spot. It was a filename problem 
> in the end.
> I ran it from the command line to get a feel for what it was doing.
> 
> eg:  Backuppc_Dump -fv hostname
> 

The results of this are exactly what the logs show...the backup just stops
at random places...for no apparent reason.  It's like there's a complete
network interruption that makes the open socket hang.

> > 2005-02-22 06:05:38 Got fatal error during xfer (Child exited 
> > prematurely)
> > 2005-02-22 06:05:43 Backup aborted (Child exited prematurely)
> >  
> > More detail of the same event:
> >  
> > Xfer PIDs are now 9721
> > [ skipped 167 lines ]
> > Can't write 16 bytes to socket
> > Read EOF: 
> > Tried again: got 0 bytes
> > finish: removing in-process file Administration/Employee Files 
> > (non-employment)/GEORGE/GLJ Hard Drive Backup/ GLJ Files & 
> > Projects/Cuba/Saved Mail
> 
> Mine was dieing on a file with a similar name. It contained 
> spaces and ampersands like yours. For the life of me I could 
> not figure out how to escape the special characters 
> correctly. I tried many, many differing combinations and in 
> the end I just organised for the Directory name to be renamed 
> without the spaces and & in the name.
> 
> All backups for that host have run to completion, without 
> errors ever since. :-)
> 

I'd say that was the problem too...but files with spaces and ampersands have
been backed up and are already in the pool.  Not just a few files,
either...like hundreds of them.

smime.p7s
Description: S/MIME cryptographic signature