Just to add something to the mix, I noticed this same issue when running WAL-E on a t1.micro instance backing up to S3 in the same region - it looks like the network performance is just too low.
When running the same setup on an m3.large instance it worked just fine, first try. Patrick. On Tuesday, February 4, 2014 10:07:58 AM UTC-8, Dan Fairs wrote: > > >> I'll give it a couple of hours and try again. > > > > Heh, is that how it manifests? Good to know... > > > > Does your WAL-E complain about your bucket name when it starts up? > > I'm wondering if this could be an IAM/Region issue, but I'm pretty > > much guessing now. > > > > Nope - no obvious problems apart from the timeout. I'll give S3 some time > to get its house in order and just try it again. > > Cheers, > Dan > -- > Dan Fairs | @danfairs | Technical Director | secondsync.com > > -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
