I do have a recovery.conf setup and it looks correct. It is included below. Postgres has access to read the file as well.
standby_mode = 'on' # enables stand-by (readonly) mode # Connect to the master postgres server using the replicator user we created. primary_conninfo = 'host=<host> port=<port> user=<user> password=<password>' # Specifies a trigger file whose presence should cause streaming replication to # end (i.e., failover). trigger_file = '/tmp/pg_failover_trigger' # Shell command to execute an archived segment of WAL file series. # Required for archive recovery if streaming replication falls behind too far. restore_command = '/usr/bin/envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-fetch "%f" "%p"' archive_cleanup_command = 'pg_archivecleanup /var/lib/postgresql/9.3/archive/ %r' On Wed, Feb 12, 2014 at 11:47 AM, Daniel Farina <[email protected]> wrote: > On Wed, Feb 12, 2014 at 9:39 AM, Kevin Harriss <[email protected]> > wrote: > > > >> > >> > On the slave would do the following steps: > >> > 1 stop postgres > >> > 2 delete the $PG_DATA > >> > 3 envdir /etc/wal-e.d/env wal-e backup-fetch $PGDATA LATEST > >> > 4 start up postgres and watch the recovery > >> > >> Yeah. > > > > I did those steps above and now the postgres slave won't startup and it > > doesn't log any errors about it failing either. > > Did you set up recovery.conf? > -- 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.
