From: Pepe TD Vo <pepevo@yahoo.com>
To: Ekaterina Amez <ekaterina.amez@zunibal.com>
To: Pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: backup script error with could not connect to database
Date: Fri, 20 Dec 2019 13:13:49 +0000 (UTC)
Message-ID: <177879592.1149046.1576847629635@mail.yahoo.com> (raw)
In-Reply-To: <2c818ef8-e555-6dea-a5e8-cd059a3c9ebd@zunibal.com>
References: <280013024.631417.1576695326572.ref@mail.yahoo.com>
<280013024.631417.1576695326572@mail.yahoo.com>
<CAKqYf_+FLs4ai+Ltz150Ti80=f8VQX8uq33xAx6F7NoJ5jwLUQ@mail.gmail.com>
<700937906.892189.1576773893896@mail.yahoo.com>
<2c818ef8-e555-6dea-a5e8-cd059a3c9ebd@zunibal.com>
the script worked for my single node postgres database server with the first line in pg_hba.conf host all all 127.0.0.1/32 indent
not work at all on the replication servers. I tried to resolve it for two days and finally, I put "trust" on the 1st line, the script works.
Bach-Nga
No one in this world is pure and perfect. If you avoid people for their mistakes you will be alone. So judge less, love and forgive more.To call him a dog hardly seems to do him justice though in as much as he had four legs, a tail, and barked, I admit he was, to all outward appearances. But to those who knew him well, he was a perfect gentleman (Hermione Gingold)
**Live simply **Love generously **Care deeply **Speak kindly.*** Genuinely rich *** Faithful talent *** Sharing success
On Friday, December 20, 2019, 04:59:27 AM EST, Ekaterina Amez <ekaterina.amez@zunibal.com> wrote:
El 19/12/19 a las 17:44, Pepe TD Vo escribió:
I made it work. I changed all in pg_hba.conf to trust and backup scripts run fine.
When Postgres searches for the matching line in pg_hba.conf, the first line that matches current connection wins. This means that if you have:
host all all 127.0.0.1/32 indent
host replication all 127.0.0.1/32 trust
The first line wins and indent is applied instead of trust.
thank you so much.
Bach-Nga
No one in this world is pure and perfect. If you avoid people for their mistakes you will be alone. So judge less, love and forgive more. To call him a dog hardly seems to do him justice though in as much as he had four legs, a tail, and barked, I admit he was, to all outward appearances. But to those who knew him well, he was a perfect gentleman (Hermione Gingold)
**Live simply **Love generously **Care deeply **Speak kindly. *** Genuinely rich *** Faithful talent *** Sharing success
On Thursday, December 19, 2019, 07:12:54 AM EST, bw <bwakkie@gmail.com> wrote:
Did you try
root su -c postgres pg_dumpall > postgresdump.sql
On Wed, 18 Dec 2019 at 19:55, Pepe TD Vo <pepevo@yahoo.com> wrote:
>
> hello expert,
>
> I had to do a backup on replication master-slave servers. I also have asked this question before, but I don't understand why I followed the information and same scripting to run on the replication servers and didn't work. I can run pg_dumpall successful but not with the script. Would you please tell me what's wrong and what need to correct the error?
>
> my replication server (master) pg_hba.conf
>
> # "local" is for Unix domain socket connections only
> local all all peer
> host all all 192.168.2.0/24 trust
> # IPv4 local connections:
> host all all 127.0.0.1/32 indent
> local all postgres trust
> host all power_user 0.0.0.0/0 md5
> host all other_user 0.0.0.0/0 md5
> host all storageLoader 0.0.0.0/0 md5
> # IPv6 local connections:
> host all all ::1/128 indent
> #allow replication connections from localhost, by a user with the replication priviledge
> local replication all trust
> host replication all 127.0.0.1/32 trust
> host replicaiton all ::1/128 trust
> host replication replicauser masterIP/32 trust
> host replicaiton replicauser slaveIP/32 trust
>
> from the postgres prompt I can connect to each database
>
> #psql -d template0 -U postgres
> template0-#
> #psql -d template1 -U postgres
> template1-#
>
> #psql -d pscidr -U postgres
> pscidr-#
> #psql -d postgres -U postgres
> postgres-#
>
>
> when I run the script as postgres os, I don't see the error but the only global.sql backup but nothing in it, 0 byte (blank) sql script.
>
> when I run as root su -c postgres /path/pg_backup.sh > pgbackup.log, I get below:
>
> Performing globals backup:
> Globals backup
> pg_dumpall: could not connect to database "template1":FATAL: Ident authentication failed for user "postgres" fro globals backup.
>
> Performing schema-only backup:
> psql:FATAL: Ident authentication failed for user "postgres"
> the following databases were matched for schema-only backup:
>
> performing full backup:
> psql:FATAL: Ident authentication failed for user "postgres"
>
>
> I can run pg_dumpall > postgresdump.sql as postgres user os fine will all the databases backup
>
> pg_backup.sh and pg_backup.config attachment.
>
> v/r,
>
> Bach-Nga
>
> No one in this world is pure and perfect. If you avoid people for their mistakes you will be alone. So judge less, love and forgive more.
> To call him a dog hardly seems to do him justice though in as much as he had four legs, a tail, and barked, I admit he was, to all outward appearances. But to those who knew him well, he was a perfect gentleman (Hermione Gingold)
>
> **Live simply **Love generously **Care deeply **Speak kindly.
> *** Genuinely rich *** Faithful talent *** Sharing success
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pepevo@yahoo.com, ekaterina.amez@zunibal.com
Subject: Re: backup script error with could not connect to database
In-Reply-To: <177879592.1149046.1576847629635@mail.yahoo.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