| From: | Avihai Shoham <avihai(dot)shoham(at)gmail(dot)com> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PG_Basebackup create bad base.tar file |
| Date: | 2022-02-13 03:24:42 |
| Message-ID: | CA+=0EReTech8M+jZqxZrLKYieAvQ+tnpck+AwbPZs54MsPasJA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(at)gmail(dot)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.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2022-02-13 06:24:53 | Re: PG_Basebackup create bad base.tar file |
| Previous Message | Noah | 2022-02-13 02:02:29 | Re: setting up postgres replication FATAL: database system identifier differs between the primary and standby |