Hello, I go the famous "aborted by signal=PIPE" error with a BackupPC 2.1 host last night. I had started a full backup (forced) because I had the previous 2 attempts fail with the same error, and it happened again. The server connects using ssh, it successfully backs-up for more than 100 minutes (133 was my max in those attempts) and then I get the error. The server only had one backup in progress, and I'm on a 100Mb network, and the network load is just the backup (thus one server, one client). I've make the timeout limit higher (because I also backup a host several thousand kilometers away (without any problems, but the quantity to backup is small (config files)) so it's not that, could it be an ssh connection timeout or max connection time thing? Any ideas?
Thanks, Gabriel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
