I also experienced this issue first-hand and can confirm that the proposed workaround of manually encrypting and pushing the history file back up was able to allow recovery to continue.
On Wednesday, July 27, 2016 at 12:18:32 PM UTC-7, [email protected] wrote: > > Yes, exactly this. My thoughts are that the only way to fix at this point, > I will need to grab the history files, manually encrypt them with GPG, and > overwrite them. > > On Wednesday, July 27, 2016 at 2:16:30 PM UTC-5, Daniel Farina wrote: >> >> On Wed, Jul 27, 2016 at 11:04 AM <[email protected]> wrote: >> >>> The history file is definitely not encrypted. According to S3, the >>> 00000009.history.lzo file has not been modified since March. I do have wal >>> segments in that same bucket/directory that are definitely encrypted though. >>> >> >> Oh, I see, I bet you had things unencrypted and then turned on >> encryption? Unlike all the other backup files that tend to disappear >> through rotation, history files can last indefinitely. >> > -- 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.
