>> Base backup and subsequent log archival go well. I'm also able to restore >> the base backup onto a slave. When I then place a recovery.conf in the >> slave's cluster data directory and start the server, it starts fetching WAL >> from the archive using WAL-E but then terminates with a message like this: > > I am tracking a problem with backup-fetch that is rather scary. Can > you send to me -- privately, or on list -- a redacted transcript of > your backup-fetch logs? > > So far the bug has been extremely rare in practice, even though it's > been latent for years. I committed what I think is a fix, but haven't > released it yet because I haven't been able to get a neat and tidy > reproduction under simulation.
Sure - I'll send them to you privately. Give me a few minutes, we can continue the discussion on the list. Thanks, Dan -- Dan Fairs | [email protected] | @danfairs | 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.
