Hi John,
sorry for my delay.
I have this configuration on my "failing" host:
# cat someserver.company.it.pl
$Conf{RsyncShareName} = [
'etc',
'home',
'mysql',
'apache',
'rpm',
'backup'
];
$Conf{XferMethod} = 'rsyncd';
$Conf{PingCmd} = '/bin/true';
$Conf{RsyncdPasswd} = 'xxxxxxxxxxxxxxx';
$Conf{RsyncdUserName} = 'someserver';
$Conf{ClientTimeout} = '944000';
but I get same error.
Anyway, there is a FW between host and BackupPC server.
Probably there is some timeout issue .. I will raise timeout on FW, and I let
you know.
Thank you
----Messaggio originale----
Da: "John Spitzer" <johned9...@comcast.net>
Data: 24/01/2017 21.02
A: "absolutely_f...@libero.it"<absolutely_f...@libero.it>, "General list for
user discussion, questions and support"<backuppc-users@lists.sourceforge.net>
Ogg: Re: [BackupPC-users] Can't write 32786 bytes to socket
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, I got this mail every day:
The following hosts had an error that is probably caused by a
misconfiguration. Please fix these hosts: - server1 (aborted by
signal=PIPE) - server2 (aborted by signal=PIPE)
I tried to run those backup with CLI, and I get this:
Can't write 32786 bytes to socket Read EOF: Tried again: got 0 bytes Can't
write 32816 bytes to socket Child is aborting Done: 1353926 files, 194996363724
bytes Got fatal error during xfer (aborted by signal=PIPE) Backup aborted by
user signal Saving this as a partial backup dump failed: aborted by
signal=PIPE
I am using BackupPC 3.2.1-4 (official Debian Package)
Can you help me to solve this ? Thank you very much
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's mostengaging tech
sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________BackupPC-users mailing
listBackupPC-users@lists.sourceforge.netList: https://lists.sourceforge.
net/lists/listinfo/backuppc-usersWiki: http://backuppc.wiki.sourceforge.
netProject: http://backuppc.sourceforge.net/
-- John spitzerjohned9...@comcast.neth - 503-590-7434C - 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/
