Mark Phillips wrote:
>
> BTW, rsync version is 3.0.7 protocol version 30.
>
> I ran the backup again, and got these rsync errors on the machine being
> backed up:
>
> 2010/02/03 14:15:21 [17390] <f????????? home/mark/Desktop/A Still Life
> with Iris/dvd/VIDEO_TS/VTS_01_3.VOB
> 2010/02/03 14:18:50 [17390] <f????????? home/mark/Desktop/A Still Life
> with Iris/dvd/VIDEO_TS/VTS_01_4.VOB
> 2010/02/03 14:28:40 [17390] <f????????? home/mark/Desktop/A Still Life
> with Iris/movie.iso
> 2010/02/03 14:28:41 [17390] rsync: writefd_unbuffered failed to write
> 4092 bytes to socket [sender]: Broken pipe (32)
The client side thinks the network is broken.
> 2010/02/03 14:28:41 [17390] rsync error: errors with program diagnostics
> (code 13) at log.c(237) [sender=3.0.7]
>
> Anyone have an idea as to what is causing this? What other tests can I
> perform?
What's between the client and server? Can you get them on the same switch at
least long enough to see if it stays connected that way? You can run tcpdump
on
both ends, but all you will be able to tell is which end sent the last packet
or
if something sent a RST.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
