We've been using wal-e in production for over a year, with Postgres 9.3 and S3. We recently moved from Centos 6.5 to 7, and I can't do a restore now, because it times out.
We have a hot failover, so our master is set with 'wal_level = hot_standby' and 'archive_mode = yes'. We do a nightly backup-push. I don't think we have a particularly write-heavy database. When I attempt a recovery, the 'systemctl start postgres-9.3' command times out after 300 seconds. The syslog is full of 'MSG: could no longer locate object while performing wal restore' messages. So it appears to be working, it's just taking too long. I did try a recovery right after doing a backup-push on the master, and that made no difference. I am by no means a Postgres expert. Any thoughts on what might be the problem? Do we have the configuration wrong? Thanks, Mark -- 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.
