Timothy J. Massey wrote:
>
> Another failure. And here's the log:
>
> 2007-01-29 13:41:49 full backup started for directory ROOT
> 2007-01-29 14:19:55 Got fatal error during xfer (Child exited prematurely)
> 2007-01-29 14:20:00 Backup aborted (Child exited prematurely)
> 2007-01-29 14:20:00 Saved partial dump 0
>
> Here's the log from the host:
>
> # cat rsyncd.log
> 2007/01/29 12:56:15 [8021] name lookup failed for 192.168.1.32: Name or
> service not known
> 2007/01/29 12:56:15 [8021] rsync on . from [EMAIL PROTECTED] (192.168.1.32)
> 2007/01/29 13:34:09 [8021] rsync: writefd_unbuffered failed to write
> 4096 bytes: phase "unknown" [sender]: Connection timed out (110)
> 2007/01/29 13:34:09 [8021] rsync error: error in rsync protocol data
> stream (code 12) at io.c(909)
Does this aways happen on the same file? It looks like what used to
happen when rsync had a 2 gig file size limit, but I don't think any
versions you've mentioned would have that. How about disk space for a
tmp copy of whatever you've hit back on the backuppc server. I've seen
errors approximately like that with stock rsync copies when the receiver
runs out of disk space. Or as a final guess, what about
disk/filesystem problems? Does 'dmesg' show any problems when this happens?
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
