On Ubuntu 14, I have a strange feeling that something is a little off, after following the instructions on the Github site and the Opbeat blog.
postgres does not seem to want to run the archive command properly. If I manually run envdir /etc/wal-e.d/env wal-e wal-push /var/lib/postgresql/9.3/main/pg_xlog/00000001000000000000001A, it seems to work. If I manually run envdir /etc/wal-e.d/env wal-e wal-push pg_xlog/00000001000000000000001A while in/var/lib/postgresql/9.3/main, it seems to work. But, my archive_command, 'envdir /etc/wal-e.d/env wal-e wal-push %p', seems to error out. Also, envdir /etc/wal-e.d/env wal-e backup-push /var/lib/postgresql/9.3/main does backup to S3 (I do end up with a file in S3), but gets stuck with "NOTICE: pg_stop_backup cleanup done, waiting for required WAL segments to be archived" errors. I also end up with a .backup file in pg_xlog. I'm assuming that whatever is jamming wal-push in the archive_command is hitting an ending step of backup-push? Any suggestions? PS: Not to confuse the issue, but it may be the same root problem. The command envdir /etc/wal-e.d/env wal-e backup-list shows nothing but headers, even though I have files in WAL and base directories. -- 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.
