From: Achilleas Mantzios - cloud <a.mantzios@cloud.gatewaynet.com>
To: KK CHN <kkchn.in@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: pgBackRest on old installation
Date: Tue, 21 Nov 2023 13:59:09 +0200
Message-ID: <c903caf3-25ff-b92b-c480-60fdd806425b@cloud.gatewaynet.com> (raw)
In-Reply-To: <CAKgGyB9z_yDWnXG7Hc8wyicLOTnAGe=tyKCX7KcbhQBh4eS-eQ@mail.gmail.com>
References: <CAKgGyB_cZeZRPogfZkjz5eWYhkO_bCi8uw4YqyHuLwGwL_csPg@mail.gmail.com>
<f4e3ed82-327e-7529-cbe4-f66125d6a6b3@cloud.gatewaynet.com>
<CAKgGyB9z_yDWnXG7Hc8wyicLOTnAGe=tyKCX7KcbhQBh4eS-eQ@mail.gmail.com>
On 11/21/23 08:36, KK CHN wrote:
> Thank you. Its worked out well. But a basic doubt ? is storing the DB
> superuser password in .pgpass is advisable ? What other options do we
> have ?
> #su postgres
> bash-4.2$ cd
>
> bash-4.2$ cat .pgpass
> *:*:*:postgres:your_password
> bash-4.2$
root has access to any file, but if you give password on the command
line or env variable then you give this info to all users in the system.
>
>
> On Mon, Nov 20, 2023 at 4:16 PM Achilleas Mantzios - cloud
> <a.mantzios@cloud.gatewaynet.com> wrote:
>
>
> On 11/20/23 12:31, KK CHN wrote:
>> list,
>>
>> I am trying pgBackRest on an RHEL 7.6 and old EDB 10 database
>> cluster( a legacy application.)
>>
>> I have installed pgbackrest through package install on RHEL7.6
>> But unable to get the basic stanza-creation working It throws an
>> error.
>>
>>
>> * /etc/pgbackrest.conf as follows..*
>> ################################################
>> [demo]
>> pg1-path=/app/edb/as10/data
>> pg1-port = 5444
>> pg1-socket-path=/tmp
>>
>> [global]
>> repo1-cipher-pass=sUAeceWoDffSz9Q/d8sWREHe+wte3uOO9lggn5/5mTkQEempvBxQk5UbxsrDzHbw
>>
>> repo1-cipher-type=aes-256-cbc
>> repo1-path=/var/lib/pgbackrest
>> repo1-retention-full=2
>> backup-user=postgres
>>
>>
>> [global:archive-push]
>> compress-level=3
>> #####################################################
>>
>>
>>
>> [root@dbs ~]# pgbackrest version
>> pgBackRest 2.48
>> [root@dbs ~]#
>> #####################################################
>>
>> *Postgres conf as follows... *
>>
>> listen_addresses = '*'
>> port = 5444
>> unix_socket_directories = '/tmp'
>>
>> archive_command = 'pgbackrest --stanza=demo archive-push %p'
>> archive_mode = on
>> log_filename = 'postgresql.log'
>> max_wal_senders = 3
>> wal_level = replica
>>
>> #############################################
>>
>>
>> *ERROR Getting as follows .. What went wrong here ??*
>>
>>
>> [root@dbs ~]# sudo -u postgres pgbackrest
>> --stanza=demo --log-level-console=info stanza-create
>> 2023-11-20 21:04:05.223 P00 INFO: stanza-create command begin
>> 2.48: --exec-id=29527-bf5e2f80 --log-level-console=info
>> --pg1-path=/app/edb/as10/data --pg1-port=5444
>> --pg1-socket-path=/tmp --repo1-cipher-pass=<redacted>
>> --repo1-cipher-type=aes-256-cbc --repo1-path=/var/lib/pgbackrest
>> --stanza=demo
>> WARN: unable to check pg1: [DbConnectError] unable to connect to
>> 'dbname='postgres' port=5444 host='/tmp'': connection to server
>> on socket "/tmp/.s.PGSQL.5444" failed: fe_sendauth: no password
>> supplied
>> ERROR: [056]: unable to find primary cluster - cannot proceed
>> HINT: are all available clusters in recovery?
>> 2023-11-20 21:04:05.224 P00 INFO: stanza-create command end:
>> aborted with exception [056]
>> [root@dbs ~]#
>>
>> It complains about the password. I followed the below tutorial
>> link, but no mention of password (Where to supply password, what
>> parameter where ?) setting here ==>
>> https://pgbackrest.org/user-guide-rhel.html
>
> This is about the user connecting to the db, in general,
> pgbackrest has to connect like any other app/user. So, change your
> .pgpass to contain smth like the below on the top of the file :
>
> /tmp:5444:*:postgres:your_whatever_pgsql_password
>
> and retry
>
>>
>>
>> Any hints welcome.. What am I missing here ??
>>
>> Best,
>> Krishane
>>
>>
>>
>>
>>
>>
>>
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: a.mantzios@cloud.gatewaynet.com, kkchn.in@gmail.com
Subject: Re: pgBackRest on old installation
In-Reply-To: <c903caf3-25ff-b92b-c480-60fdd806425b@cloud.gatewaynet.com>
References: <CAKgGyB_cZeZRPogfZkjz5eWYhkO_bCi8uw4YqyHuLwGwL_csPg@mail.gmail.com> <f4e3ed82-327e-7529-cbe4-f66125d6a6b3@cloud.gatewaynet.com> <CAKgGyB9z_yDWnXG7Hc8wyicLOTnAGe=tyKCX7KcbhQBh4eS-eQ@mail.gmail.com> <c903caf3-25ff-b92b-c480-60fdd806425b@cloud.gatewaynet.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