The trick in getting to the bottom of an issue is to isolate it. This is a process where you gradually circle in closer and closer to what is triggering the bug and try not to let your preconceptions get in the way. It could be that your network only interferes with long-lived SSL connections, etc. It could be a rare Amazon S3 bug.
The main evidence for my hypothesis that it's a problem with your network is that we've never seen this happen before. So exactly the same software stack works elsewhere and doesn't work for you. What's different?
A couple of ideas:
1) Try restoring backup #1 from an Amazon EC2 instance you launch via the Hub. If that doesn't work then excellent because then we can easily reproduce the problem by using your backup as a test case (with your permission of course).
2) Try re-initializing tklbam to create a new backup:
tklbam-init --force YOUR-API-KEY
tklbam-backup
If the problem persists with a new backup it's unlikely to be a rare bug on Amazon's end.
3) Edit /etc/tklbam/conf to reduce the volume size (e.g., to 1MB) and try again. If long-lived connections on your network are the problem maybe this will get around it.
A few more ideas
The main evidence for my hypothesis that it's a problem with your network is that we've never seen this happen before. So exactly the same software stack works elsewhere and doesn't work for you. What's different?
A couple of ideas:
1) Try restoring backup #1 from an Amazon EC2 instance you launch via the Hub. If that doesn't work then excellent because then we can easily reproduce the problem by using your backup as a test case (with your permission of course).
2) Try re-initializing tklbam to create a new backup:
If the problem persists with a new backup it's unlikely to be a rare bug on Amazon's end.3) Edit /etc/tklbam/conf to reduce the volume size (e.g., to 1MB) and try again. If long-lived connections on your network are the problem maybe this will get around it.