Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nJ8KL-0002Mb-MP for pgsql-admin@arkaria.postgresql.org; Sun, 13 Feb 2022 06:25:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nJ8Jn-0008Og-4N for pgsql-admin@arkaria.postgresql.org; Sun, 13 Feb 2022 06:25:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nJ8Jm-0008OX-NH for pgsql-admin@lists.postgresql.org; Sun, 13 Feb 2022 06:25:06 +0000 Received: from mail-ot1-x32a.google.com ([2607:f8b0:4864:20::32a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nJ8Ji-0003Z7-0o for pgsql-admin@lists.postgresql.org; Sun, 13 Feb 2022 06:25:06 +0000 Received: by mail-ot1-x32a.google.com with SMTP id p3-20020a0568301d4300b005a7a702f921so9374239oth.9 for ; Sat, 12 Feb 2022 22:25:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=x614WiEUAEI9lzF/qFayYcrb6ME+19TKyOA+rtNQzsE=; b=oKukQYhQFqLuwWye1RNW+MVuXM4/O+MLyOM8PvvrO70d8rIeiIENBJRjHPVwO8hJTN oyrjIGUXpKsTCoGrqOgj/BK1+MnUlwB6gvV5DjZdM56JwFIB+jzliKEFZ7mxYtO1bY3a TpvXo1R0VqFcEOQIMaU6jerG19wSIBlRSkO993DDi/Ql0zgjjR9LUGErWdUab7Ujqq0c DEKaSWkrljsWCBzj98vx2kb3IayAGh7MzHHksVEFVNGjU8Z9Vztx8ggOIwqRRVPw/QtQ QENcbqjJjV4UMeugEo2bLb0Jb/oHKkWQqko7dIDOFPn+1irm+8PVn7lUaHML2DbutQFW +KFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=x614WiEUAEI9lzF/qFayYcrb6ME+19TKyOA+rtNQzsE=; b=cToulPDVP1jtyp3lLVtf+LR70rZ2zEL+Hyhl+tzk1vQq5IWG1MPsx1Qx5r6FE3wqMo +b4EK/7sPiq+2oUrMAeqNrubBlsLnsUJewLSf26/Nw8lr1OzIw5xfFeJMQBHB+qRzSsP Nlc8rbytpGPWlS9Dr+TEbd+n0QHHNRkOUt8x9mjiH84IaI7omIcsAzmga2hxh4Ql9H92 mLaTBo3zmnP4U5ahzKXwcIo+vEyGNJWf+3ik0y6+8ICvSByqrzCi5iJ5dzXZJbbGZlEe 2TgcJsEiLuLywUVu2USZLAwHgAktuVnd8cAhiqf9vTyllKoiJwfIc7Z1QMIU5VP9rAGX SPYA== X-Gm-Message-State: AOAM530T3G+MTxFm4J7n/lq7t7PYioZaCayySqyaGc5AZcy7yJymJK6V EyNH5RAJWikUrB2bI8GPnMhblHYKOdo= X-Google-Smtp-Source: ABdhPJyuPJgaZtYB1p9wgOdcI+++nxn78UIKe5u9+6stZD9KYF8w3EpYYKQUwrKapqeDHLQ7rgzkMw== X-Received: by 2002:a9d:604e:: with SMTP id v14mr3194315otj.218.1644733499457; Sat, 12 Feb 2022 22:24:59 -0800 (PST) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id q41sm11197280ooh.38.2022.02.12.22.24.54 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 12 Feb 2022 22:24:58 -0800 (PST) Subject: Re: PG_Basebackup create bad base.tar file To: pgsql-admin@lists.postgresql.org References: <6665f348-a001-8830-f7f1-ba7632dfd155@gmail.com> From: Ron Message-ID: <12e948b6-5c1c-ea24-48c8-c7034683e1d0@gmail.com> Date: Sun, 13 Feb 2022 00:24:53 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------621D33E7B850EF7A5B050CDC" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------621D33E7B850EF7A5B050CDC Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 > 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. --------------621D33E7B850EF7A5B050CDC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit 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.
--------------621D33E7B850EF7A5B050CDC--