John Rouillard wrote:

> On Thu, Feb 12, 2009 at 05:44:33PM +0100, Matthias Meyer wrote:
>> Sometimes my backups abort with different failures.
>> Anybody know the meaning of/reason for the following failures?
>> 1) Aborting backup up after signal ALRM
> 
> The backup is taking longer than your $Conf{ClientTimeout}
> setting. Once you hit $Conf{ClientTimeout} seconds a sigalarm is sent
> to the process, which causes it to exit.

Did this occur also if data wil be transmitted between client and server or
only if no data received until $Conf{ClientTimeout} seconds?

> 
>> 2) Backup aborted (Child exited prematurely)
> 
> Could be a number of things. IIRC this also shows up when it fails
> during the initial startup. If you also see a message similar to
> "can't transfer 4 bytes" and you are using the ssh transport mechanism
> there is something causing bogus output in the .login or other startup
> files for the shell (or ssh config files).
> 
>> 3) Aborting backup up after signal INT
> 
> Usully I see this when I stop the backup using the web interface.
> 
>> 4) Aborting backup up after signal PIPE
> 
> I see this as well, not sure what the cause is. Something failed in
> the interprocess communication between the processes backuppc spawns.
> What failed who knows.
> 
> 
Thanks
-- 
Don't Panic


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/