|
Hello, I have also been working to fix this error in my setup. I am running BackupPC version 3.3.1, and using rsyncd as the transfer method. In my case the fix was to increase the timeout value in the rsyncd.conf file to 2400. The files I am backing up are VM disk image files and range in size up to 50 GBytes. In the BackupPC configuration under the Xfer panel for the Rsyncd method, there is the RsyncArgs parameter, you can add the parameter --timeout=<TIMESECS> and this may be helpful also. For me I did need to use it. I don't know anything about the internals of BackupPC but based on my tracing and logging of the issue, the problem seems to be caused by a timeout of a read by the rsyncd daemon. I think there is a PIPE open between a BackupPC process and the rsyncd daemon. Rsyncd read times out and causes the writer to get a SIGPIPE. This seems to be much more likely to happen on very large files. I have another thread open here as: Re: [BackupPC-users] BackupPC fails with aborted by signal=PIPE, Can't write to socket I'm not an expert on BackupPC and this is just my experience. Good Luck, John On 01/23/2017 1:50 AM, absolutely_f...@libero.it wrote: Hi, -- John Spitzer johned9...@comcast.net H - 503-590-7434 C - 408-234-2988 |
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ 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/
