Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I run BackupPc on a Debian Squeeze server. It backups other Debian Squeeze machines on my LAN succesfully. I've setup it to backup another Debian Squeeze machine on Wan, but the backup always fails with the error message:

Aborting backup up after signal PIPE
Got fatal error during xfer (aborted by signal=PIPE)

The backup is executed via ssh, and the configuration of this backup client is:

$Conf{RsyncArgs} = [
        # Do not edit these!
        # If you are using a patched client rsync that supports the
        # --checksum-seed option (see,
        # then uncomment this to enabled rsync checksum cachcing
        # Add additional arguments here
$Conf{FullPeriod} = 6.97;
$Conf{IncrPeriod} = 0.49;
$Conf{FullKeepCnt} = 4;
$Conf{IncrKeepCnt} = 93;
$Conf{XferMethod} = 'rsync';
$Conf{RsyncShareName} = '/';
$Conf{BackupFilesExclude} = [
$Conf{XferLogLevel} = 1;
$Conf{CompressLevel} = 9;
$Conf{PingMaxMsec} = 200;
$Conf{ClientTimeout} = 3600*8;          # 6 Hours!!

I tried a local tar backup to see if there is some issue woth the filesystem, and everything gone fine.

Any suggestions on how to debug ?

share|improve this question
more info needed. Like, how are you backing up ? I'm assuming over ssh ? – Sirex Jan 11 '12 at 14:24
An excerpt of the config would probably be very helpful for us. – Tim Jan 11 '12 at 14:38
I've edited the original question. Yes, rsync over ssh. The config file is now in the question. Thank you ! – GabrieleV Jan 11 '12 at 15:12
up vote 8 down vote accepted

I've invesitgate on the meaning of sigpipe. As described in SIGPIPE - Wikipedia, the free encyclopedia:

On POSIX-compliant platforms, SIGPIPE is the signal sent to a process when it attempts to write to a pipe without a process connected to the other end. ...

So I suspected that the trouble was with the ssh transport that gets disconnected.

I've setup a longer timeout to ssh using the option -o ServerAliveInterval=300, adding to the config

$Conf{RsyncClientCmd} = '$sshPath -o ServerAliveInterval=300 -q -x -l root $host
 $rsyncPath $argList+';

Now the backup has complete succesfully !

share|improve this answer
I had a similar error and I googled and came this page. I also use rsync method and in configuration file I do not have $Conf{RsyncClientCmd} variable. Where(main conf file or client conf file) should I provide the above statement? – Subhransu Mishra Dec 3 '12 at 12:05
In client conf file if you want to apply this modification only to a specific client. In main conf, if you want this behavior applied globally. – GabrieleV Dec 4 '12 at 19:12
It doesn't work on my installation. BackupPC 3.3.0 – Jesper Grann Laursen Jun 28 '13 at 12:44

Just in case this is useful to others, we were getting both "aborted by signal=PIPE" and "Child exited prematurely" on some backups (only incrementals as it happens). Adjusting the $Conf(RsyncClientCmd) didn't work for our installation of BackupPc 3.1 on Centos 5 (soon to be upgraded), as it broke the attempt to connect in the first place. We are using Rsync over ssh.

As the machine was dedicated to doing backups and we were concerned about others using ssh access, we simply set ClientAliveInterval=300 in /etc/ssh/sshd_conf on the client machines (not the BackupPc server), but this could have been done for the individual login instead.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.