Message-ID: <fc13c6aa5c7ed403cae375ec437d80d5ed86c619.camel@cybertec.at>
Subject: Re: On Replica - History issue
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: SOzcn <selahattinozcnma@gmail.com>, pgsql-admin@lists.postgresql.org
Date: Fri, 27 Oct 2023 14:29:58 +0200
In-Reply-To: 
 <CAJyV5AbGPAyqnpHcBkuENdmbm=+7S0Gh4rkj0ZmYTBB2-vjkmg@mail.gmail.com>
References: 
	<CAJyV5AbGPAyqnpHcBkuENdmbm=+7S0Gh4rkj0ZmYTBB2-vjkmg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/fc13c6aa5c7ed403cae375ec437d80d5ed86c619.camel%40cybertec.at>
Precedence: bulk

On Fri, 2023-10-27 at 13:36 +0300, SOzcn wrote:
> Hello I need some advice about the issue in the bellow. Because of datace=
nter I has
> to create my replica's from zero. On a cluster I get a error, it's look l=
ike about
> pgbackrest issue, but also this one has no backup for now. Before it has.=
 Is there
> anything I should do Manuel?
>=20
> Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: sh: 1: pgb=
ackrest: not found
> Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: 2023-10-27=
 13:33:26.808 +03 [316957] FATAL: =C2=A0could not restore file "00000003.hi=
story" from archive: command not found

I don't think Manuel is at fault.

You should use the absolute path to "pgbackrest" in the "restore_command".

Yours,
Laurenz Albe