10:15:10.543684 IP backupserver.com.59297 > remote-server.com.99: F82592624:82592624(0) ack 39621297 win 10064 <nop,nop,timestamp 11531046912127151431> 10:15:10.583398 IP remote-server.com.99 > backupserver.com.59297: F39621297:39621297(0) ack 82592625 win 16568 <nop,nop,timestamp 21271514721153104691>10:15:10.585154 IP backupserver.com.59297 > remote-server.com. 99: . ack39621298 win 10064 <nop,nop,timestamp 1153104732 2127151472>huh... ok the backupserver sent the first FIN... that's not what i expected. i hope i didn't waste your time with the straces. here's something i should have asked for at the very beginning: run rdiff-backup with -v9 option (actually i think -v5 is good enough, but it's been some time since i've done this). hopefully there'll be something more illuminating in the output than the default traceback gives.
Attached is the last 99 lines of the v9 log, after it failed 2 hours and 39 minutes after initiation. I don't really see anything wrong in this log - it was busy creating a hard link when it failed?
- Jes
rdiff-v9.log
Description: Binary data
_______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
