On Wed, Aug 13, 2014 at 12:34 AM, Stuart Bishop <[email protected]> wrote: > On 13 August 2014 07:55, Paul Tiseo <[email protected]> wrote: >> Under the postgres user manually, and when added in archive_command, type >> returns /usr/local/bin/wal-e, which is correct. The log (not the csv) also >> says "envdir: fatal: unable to run wal-e: file does not exist". > > /usr/local/bin is likely not in the $PATH being used by the postgres > process. This is likely different to the path you are manually testing > with, as that session will be a login shell. > > As others have stated, putting the full path to the wal-e binary in > your archive_command will likely fix WAL archiving > (archive_command='envdir /etc/wal-e.d/env /usr/local/bin/wal-e > wal-push %p', which I don't think you tried yet). > > First get WAL archiving working, so you are no longer getting those > 111 errors spit out in your postgresql log file. Only then will your > backups have a hope.
This response came out of order because of the spam filter. Hopefully it has learned you now. Sorry I was slow at plucking it out of the filter. -- 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.
