pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedOn Replica - History issue
7+ messages / 2 participants
[nested] [flat]
* On Replica - History issue
@ 2023-10-27 10:36 SOzcn <selahattinozcnma@gmail.com>
0 siblings, 1 reply; 7+ messages in thread
From: SOzcn @ 2023-10-27 10:36 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hello I need some advice about the issue in the bellow. Because of
datacenter I has to create my replica's from zero. On a cluster I get a
error, it's look like about pgbackrest issue, but also this one has no
backup for now. Before it has. Is there anything I should do Manuel?
Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: sh: 1:
pgbackrest: not found
Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: 2023-10-27
13:33:26.808 +03 [316957] FATAL: could not restore file "00000003.history"
from archive: command not found
Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: 2023-10-27
13:33:26.810 +03 [316956] LOG: startup process (PID 316957) exited with
exit code 1
Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: 2023-10-27
13:33:26.810 +03 [316956] LOG: aborting startup due to startup process
failure
Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: 2023-10-27
13:33:26.811 +03 [316956] LOG: database system is shut down
Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: pg_ctl:
could not start server
Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: Examine the
log output.
Oct 27 13:33:26 se-prd-db02 systemd[1]: postgresql@13-clustername.service:
Can't open PID file /run/postgresql/13-clustername.pid (yet?) after start:
Operation not permitted
Oct 27 13:33:26 se-prd-db02 systemd[1]: postgresql@13-clustername.service:
Failed with result 'protocol'.
Oct 27 13:33:26 se-prd-db02 systemd[1]: Failed to start PostgreSQL Cluster
13-clustername.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: On Replica - History issue
@ 2023-10-27 12:29 Laurenz Albe <laurenz.albe@cybertec.at>
parent: SOzcn <selahattinozcnma@gmail.com>
0 siblings, 1 reply; 7+ messages in thread
From: Laurenz Albe @ 2023-10-27 12:29 UTC (permalink / raw)
To: SOzcn <selahattinozcnma@gmail.com>; pgsql-admin@lists.postgresql.org
On Fri, 2023-10-27 at 13:36 +0300, SOzcn wrote:
> Hello I need some advice about the issue in the bellow. Because of datacenter I has
> to create my replica's from zero. On a cluster I get a error, it's look like about
> pgbackrest issue, but also this one has no backup for now. Before it has. Is there
> anything I should do Manuel?
>
> Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: sh: 1: pgbackrest: not found
> Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: 2023-10-27 13:33:26.808 +03 [316957] FATAL: could not restore file "00000003.history" 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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: On Replica - History issue
@ 2023-10-30 10:48 SOzcn <selahattinozcnma@gmail.com>
parent: Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 2 replies; 7+ messages in thread
From: SOzcn @ 2023-10-30 10:48 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: pgsql-admin@lists.postgresql.org
Hello,
"restore_command" is default .
my archive command is ;
archive_command = 'pgbackrest --stanza=cluster_stanza archive-push %p'
with this way I setup my backup procedure without problem, is there might
be another problem I cannot see?
Laurenz Albe <laurenz.albe@cybertec.at>, 27 Eki 2023 Cum, 15:30 tarihinde
şunu yazdı:
> On Fri, 2023-10-27 at 13:36 +0300, SOzcn wrote:
> > Hello I need some advice about the issue in the bellow. Because of
> datacenter I has
> > to create my replica's from zero. On a cluster I get a error, it's look
> like about
> > pgbackrest issue, but also this one has no backup for now. Before it
> has. Is there
> > anything I should do Manuel?
> >
> > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: sh: 1:
> pgbackrest: not found
> > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]:
> 2023-10-27 13:33:26.808 +03 [316957] FATAL: could not restore file
> "00000003.history" 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
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: On Replica - History issue
@ 2023-10-30 11:00 SOzcn <selahattinozcnma@gmail.com>
parent: SOzcn <selahattinozcnma@gmail.com>
1 sibling, 0 replies; 7+ messages in thread
From: SOzcn @ 2023-10-30 11:00 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: pgsql-admin@lists.postgresql.org
I also checked my prod cluster wal file, there has no that file either. I
missing something I don't see.
SOzcn <selahattinozcnma@gmail.com>, 30 Eki 2023 Pzt, 13:48 tarihinde şunu
yazdı:
> Hello,
>
> "restore_command" is default .
> my archive command is ;
> archive_command = 'pgbackrest --stanza=cluster_stanza archive-push %p'
>
> with this way I setup my backup procedure without problem, is there might
> be another problem I cannot see?
>
> Laurenz Albe <laurenz.albe@cybertec.at>, 27 Eki 2023 Cum, 15:30 tarihinde
> şunu yazdı:
>
>> On Fri, 2023-10-27 at 13:36 +0300, SOzcn wrote:
>> > Hello I need some advice about the issue in the bellow. Because of
>> datacenter I has
>> > to create my replica's from zero. On a cluster I get a error, it's look
>> like about
>> > pgbackrest issue, but also this one has no backup for now. Before it
>> has. Is there
>> > anything I should do Manuel?
>> >
>> > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: sh: 1:
>> pgbackrest: not found
>> > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]:
>> 2023-10-27 13:33:26.808 +03 [316957] FATAL: could not restore file
>> "00000003.history" 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
>>
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: On Replica - History issue
@ 2023-10-30 12:29 Laurenz Albe <laurenz.albe@cybertec.at>
parent: SOzcn <selahattinozcnma@gmail.com>
1 sibling, 1 reply; 7+ messages in thread
From: Laurenz Albe @ 2023-10-30 12:29 UTC (permalink / raw)
To: SOzcn <selahattinozcnma@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org
On Mon, 2023-10-30 at 13:48 +0300, SOzcn wrote:
> > > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: 2023-10-27 13:33:26.808 +03 [316957] FATAL: could not restore file "00000003.history" from archive: command not found
> > > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: sh: 1: pgbackrest: not found
> >
> > You should use the absolute path to "pgbackrest" in the "restore_command".
>
> "restore_command" is default .
> my archive command is ;
> archive_command = 'pgbackrest --stanza=cluster_stanza archive-push %p'
>
> with this way I setup my backup procedure without problem, is there might be another problem I cannot see?
You get a fatal error restoring a file from the archive, because the restore command is not found.
What is unclear about the error message? Why don't you try the absolute path?
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: On Replica - History issue
@ 2023-10-30 13:27 SOzcn <selahattinozcnma@gmail.com>
parent: Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 1 reply; 7+ messages in thread
From: SOzcn @ 2023-10-30 13:27 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: pgsql-admin@lists.postgresql.org
I do with absolute path already, that's the problem.
Laurenz Albe <laurenz.albe@cybertec.at>, 30 Eki 2023 Pzt, 15:29 tarihinde
şunu yazdı:
> On Mon, 2023-10-30 at 13:48 +0300, SOzcn wrote:
> > > > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]:
> 2023-10-27 13:33:26.808 +03 [316957] FATAL: could not restore file
> "00000003.history" from archive: command not found
> > > > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: sh:
> 1: pgbackrest: not found
> > >
> > > You should use the absolute path to "pgbackrest" in the
> "restore_command".
> >
> > "restore_command" is default .
> > my archive command is ;
> > archive_command = 'pgbackrest --stanza=cluster_stanza archive-push %p'
> >
> > with this way I setup my backup procedure without problem, is there
> might be another problem I cannot see?
>
> You get a fatal error restoring a file from the archive, because the
> restore command is not found.
>
> What is unclear about the error message? Why don't you try the absolute
> path?
>
> Yours,
> Laurenz Albe
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: On Replica - History issue
@ 2023-10-30 13:34 SOzcn <selahattinozcnma@gmail.com>
parent: SOzcn <selahattinozcnma@gmail.com>
0 siblings, 0 replies; 7+ messages in thread
From: SOzcn @ 2023-10-30 13:34 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: pgsql-admin@lists.postgresql.org
Can you give me more details please? I've been created more than 20 cluster
replica without problem, on a cluster I get this and unfortunately I can't
figure it out like as I say on top.
SOzcn <selahattinozcnma@gmail.com>, 30 Eki 2023 Pzt, 16:27 tarihinde şunu
yazdı:
> I do with absolute path already, that's the problem.
>
>
> Laurenz Albe <laurenz.albe@cybertec.at>, 30 Eki 2023 Pzt, 15:29 tarihinde
> şunu yazdı:
>
>> On Mon, 2023-10-30 at 13:48 +0300, SOzcn wrote:
>> > > > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]:
>> 2023-10-27 13:33:26.808 +03 [316957] FATAL: could not restore file
>> "00000003.history" from archive: command not found
>> > > > Oct 27 13:33:26 se-prd-db02 postgresql@13-clustername[316944]: sh:
>> 1: pgbackrest: not found
>> > >
>> > > You should use the absolute path to "pgbackrest" in the
>> "restore_command".
>> >
>> > "restore_command" is default .
>> > my archive command is ;
>> > archive_command = 'pgbackrest --stanza=cluster_stanza archive-push %p'
>> >
>> > with this way I setup my backup procedure without problem, is there
>> might be another problem I cannot see?
>>
>> You get a fatal error restoring a file from the archive, because the
>> restore command is not found.
>>
>> What is unclear about the error message? Why don't you try the absolute
>> path?
>>
>> Yours,
>> Laurenz Albe
>>
>
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2023-10-30 13:34 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-10-27 10:36 On Replica - History issue SOzcn <selahattinozcnma@gmail.com>
2023-10-27 12:29 ` Laurenz Albe <laurenz.albe@cybertec.at>
2023-10-30 10:48 ` SOzcn <selahattinozcnma@gmail.com>
2023-10-30 11:00 ` SOzcn <selahattinozcnma@gmail.com>
2023-10-30 12:29 ` Laurenz Albe <laurenz.albe@cybertec.at>
2023-10-30 13:27 ` SOzcn <selahattinozcnma@gmail.com>
2023-10-30 13:34 ` SOzcn <selahattinozcnma@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox