On Wed, Aug 13, 2014 at 7:22 PM, Paul Tiseo <[email protected]> wrote: > That did it. > > I compared and some WAL had transferred to S3, but at one point, the rest > did not. I know early on, I had put in a bad S3 prefix but corrected it. > Presumably, that put the system in a bad state. > > And, so, I cleared archive_status of all files, and the rest started > transferring at the next cycle. I ran a backup-push, and it did not get > stuck. backup-list shows one file now, because I finally ended up with a > JSON file. > > Looks like we're good now. Thanks all for the help.
Glad to help out! This the first report I've seen of archive_status desynchronization. If it shows up for other reporters (or you) I'll look a bit more for a bug. Also sucky that there's an ugly stack trace that occurs in this case, but maybe I'll wait for more complainants (or a contributed patch) before expending the complexity given the rarity so far. -- 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/d/optout.
