pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Problems starting slave
Date: Tue, 3 Oct 2023 08:33:12 -0500
Message-ID: <07295fb2-aaef-8d3c-18ef-ffd8cdb1de11@gmail.com> (raw)
In-Reply-To: <1263466497.931257.1696257526649@mail.yahoo.com>
References: <1263466497.931257.1696257526649.ref@mail.yahoo.com>
	<1263466497.931257.1696257526649@mail.yahoo.com>

On 10/2/23 09:38, Douglas Reed wrote:
> Hi guys
>
> The servers are virtual running on Nutanix
>
> We are running Pg version 12 (12.10)
>
> On Linux km-data1.rs.fsbtech.com 5.4.191-1.el7.elrepo.x86_64 #1 SMP Tue 
> Apr 26 12:14:16 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux
>
> 48G/16 x CPU (Master and slave)
>
> Timeline
>
> System had a number of issues due to kafka and slots, would not always 
> shut down correctly. Several incidents where it had to be forced.
> Found corruption on a number of indexes and tables. Decided to recover 
> from a backup (barman). Due to missing wal file restored data up
> to about three hours prior to expectation but it's working.
>
> Attempts to build a slave;
>
> On the slave at first we got error messages from pg_basebackup stating 
> that the target directory was not empty;
>
>     pg_basebackup: error: directory "/var/lib/pgsql/12/data" exists but is 
> not empty
>
> Although the directory /var/lib/pgsql/12/data was empty (using rm -r 
> ....). Finally deleted the data directory and re-created ensuring that
> perms were same. Restore started successfully and completed with error=0.
>

What was the full pg_basebackup command, including all options?

-- 
Born in Arizona, moved to Babylonia.

view thread (4+ messages)  latest in thread

Message-ID: <07295fb2-aaef-8d3c-18ef-ffd8cdb1de11@gmail.com>
Permalink:  ../07295fb2-aaef-8d3c-18ef-ffd8cdb1de11@gmail.com/
Also on:    postgresql.org/message-id/07295fb2-aaef-8d3c-18ef-ffd8cdb1de11@gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: Problems starting slave
  In-Reply-To: <07295fb2-aaef-8d3c-18ef-ffd8cdb1de11@gmail.com>
  References: <1263466497.931257.1696257526649.ref@mail.yahoo.com> <1263466497.931257.1696257526649@mail.yahoo.com> <07295fb2-aaef-8d3c-18ef-ffd8cdb1de11@gmail.com>

* 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