From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Fazreil Amreen Abdul Jalil <fazreilamreen(dot)abduljalil(at)openet(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: getting error could not open file "pg_xlog" |
Date: | 2017-08-01 17:14:38 |
Message-ID: | CAB7nPqQPU_+7C2bG49=9+tf7h_P7XexEuQ6+oFneyJR1SGzHzw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Aug 1, 2017 at 5:15 PM, Fazreil Amreen Abdul Jalil
<fazreilamreen(dot)abduljalil(at)openet(dot)com> wrote:
> I am working on setting up postgresql with replication using ansible. I came
> to a point where I perform pg_basebackup and try to start the replication
> node. The startup failed with the following error:
>
> cp: cannot stat ‘mnt/server/archivedir/000000010000000000000014’: No such
> file or directory
I suspect that you forgot the first slash character '/' on your
restore_command in recovery.conf, to use /mnt/server/archivedir/ as
archive path. Note that Postgres backend processes are started from
PGDATA by default, so this is looking for archives within the data
folder of the server.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-08-01 20:28:31 | Re: BUG #14758: Segfault with logical replication on a function index |
Previous Message | Fazreil Amreen Abdul Jalil | 2017-08-01 15:15:17 | getting error could not open file "pg_xlog" |