From: David Steele <david@pgmasters.net>
To: singh.bpratap766@gmail.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form <noreply@postgresql.org>
Subject: Re: BUG #16408: We are facing issue while taking the backup using pgbackrest 2.22 version
Date: Fri, 1 May 2020 17:21:16 -0400
Message-ID: <3a25807b-9b1b-4638-d260-b840b17a175a@pgmasters.net> (raw)
In-Reply-To: <16408-0c3438a784ec2966@postgresql.org>
References: <16408-0c3438a784ec2966@postgresql.org>
On 5/1/20 4:27 PM, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16408
> Logged by: Brajendra Pratap Singh
> Email address: singh.bpratap766@gmail.com
> PostgreSQL version: 10.11
> Operating system: CentOS 6.9
> Description:
>
> We are facing the below error in pgbackrest backup log while the backup
> failed :
>
> ERROR: [074]: raised from local-11 protocol: unable to move
> '/apayrman/pgbackrest/backup/odbserver/20200430-055502F/pg_tblspc/58339/PG_10_201707211/58347/82334143.gz.pgbackrest.tmp'
> to
> '/apayrman/pgbackrest/backup/odbserver/20200430-055502F/pg_tblspc/58339/PG_10_201707211/58347/82334143.gz':
> [2] No such file or directory .
>
> INFO: backup command end: aborted with exception [074] .
>
> During the same time we saw the below mentioned error in postgresql log.
>
> WARNING: aborting backup due to backend exiting before pg_stop_backup was
> called .
>
> Postgresql version : 10.11
> Pgbackrest version : 2.22
>
> Please let me know if any further detail required it will be my pleasure.
You have now reported this issue three times without paying any
attention to my responses the first two times you reported it.
This is most assuredly not a PostgreSQL issue. The error you see in the
logs is because pgBackRest closes the connection that is running the
backup once is encounters the problem. PostgreSQL is merely reporting
that the backup never completed, which is true.
Please follow the advice at
https://github.com/pgbackrest/pgbackrest/issues/1019 and respond there
if you are still seeing the issue.
Regards,
--
-David
david@pgmasters.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: david@pgmasters.net, noreply@postgresql.org
Subject: Re: BUG #16408: We are facing issue while taking the backup using pgbackrest 2.22 version
In-Reply-To: <3a25807b-9b1b-4638-d260-b840b17a175a@pgmasters.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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