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.
> 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.
--
-- rouilj
John Rouillard
System Administrator
Renesys Corporation
603-244-9084 (cell)
603-643-9300 x 111
------------------------------------------------------------------------------
_______________________________________________
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/
