Re: PG_Basebackup create bad base.tar file - Mailing list pgsql-admin

From Ron
Subject Re: PG_Basebackup create bad base.tar file
Date
Msg-id 12e948b6-5c1c-ea24-48c8-c7034683e1d0@gmail.com
Whole thread Raw
In response to Re: PG_Basebackup create bad base.tar file  (Avihai Shoham <avihai.shoham@gmail.com>)
List pgsql-admin
Redirect stdout and stderr to a log file next time you run pg_basebackup.

On 2/12/22 9:24 PM, Avihai Shoham wrote:
Thank you Ron , 

Disk is not full.
Do you mean to run pg_basebackup with stdout and stderr ? i'm newbie in postgres. 

Thank you
Avihai

On Fri, Feb 11, 2022 at 3:49 AM Ron <ronljohnsonjr@gmail.com> wrote:
On 2/10/22 12:08 PM, Avihai Shoham wrote:
Hi All , 

lately i'm getting  this error when open base.tar.
Any idea why pg_basebackup created bad tar file? and how to fix it?

Thanks!
Avihai

tar xOf base.tar > /dev/null
tar: Unexpected EOF in archive
tar: rmtlseek not stopped at a record boundary
tar: Error is not recoverable: exiting now

Disk full?

Next time, capture stdout and stderr in a log file, and also the return code.

--
Angular momentum makes the world go 'round.

--
Angular momentum makes the world go 'round.

pgsql-admin by date:

Previous
From: Avihai Shoham
Date:
Subject: Re: PG_Basebackup create bad base.tar file
Next
From: Gaurav Anand
Date:
Subject: PG10 Attach-Detach Partition in Declarative vs Inheritance