pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_dumpall: could not connect to database: FATAL
24+ messages / 5 participants
[nested] [flat]
* pg_dumpall: could not connect to database: FATAL
@ 2019-02-25 16:50 Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 16:54 ` Re: [MASSMAIL]pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
2019-02-25 17:28 ` Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
0 siblings, 2 replies; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-25 16:50 UTC (permalink / raw)
To: pgsql-admin
good morning Expert DBAs,
I created a script to do backup and I have faced the error of
Performing globals backup:pg_dumpall: could not connect to database "template1":FATAL: Ident authentication failed for user "postgres" fro globals backup. As same as performing schema-only backups and full 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 but couldn't run from script even the script declared BACKUP_USER=postgres
If I take the syntax, -h "$HOSTNAME" -U "$USERNAME" out and the backup script working fine
# vi pg_backup.config##############################
## POSTGRESQL BACKUP CONFIG ##
##############################
# Optional system user to run backups as. If the user the script is running as doesn't match this
# the script terminates. Leave blank to skip check.
BACKUP_USER=
# Optional hostname to adhere to pg_hba policies. Will default to "localhost" if none specified.
HOSTNAME="hostname"
# Optional username to connect to database as. Will default to "postgres" if none specified.
USERNAME="postgres"
# This dir will be created if it doesn't exist. This must be writable by the user the script is
# running as.
BACKUP_DIR=/home/backups/database/postgresql/
# List of strings to match against in database name, separated by space or comma, for which we only
# wish to keep a backup of the schema, not the data. Any database names which contain any of these
# values will be considered candidates. (e.g. "system_log" will match "dev_system_log_2010-01")
SCHEMA_ONLY_LIST=""
# Will produce a custom-format backup if set to "yes"
ENABLE_CUSTOM_BACKUPS=yes
# Will produce a gzipped plain-format backup if set to "yes"
ENABLE_PLAIN_BACKUPS=yes
# Will produce gzipped sql file containing the cluster globals, like users and passwords, if set to "yes"
ENABLE_GLOBALS_BACKUPS=yes
#### SETTINGS FOR ROTATED BACKUPS ####
# Which day to take the weekly backup from (1-7 = Monday-Sunday)
DAY_OF_WEEK_TO_KEEP=5
# Number of days to keep daily backups
DAYS_TO_KEEP=7
# How many weeks to keep weekly backups
WEEKS_TO_KEEP=5
######################################
#vi pg_backup.sh#!/bin/bash###########################
####### LOAD CONFIG #######
###########################
while [ $# -gt 0 ]; do
case $1 in
-c)
if [ -r "$2" ]; then
source "$2"
shift 2
else
${ECHO} "Unreadable config file \"$2\"" 1>&2
exit 1
fi
;;
*)
${ECHO} "Unknown Option \"$1\"" 1>&2
exit 2
;;
esac
done
if [ $# = 0 ]; then
SCRIPTPATH=$(cd ${0%/*} && pwd -P)
source $SCRIPTPATH/pg_backup.config
fi;
###########################
#### PRE-BACKUP CHECKS ####
###########################
# Make sure we're running as the required backup user
if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
exit 1;
fi;
###########################
### INITIALISE DEFAULTS ###
###########################
if [ ! $HOSTNAME ]; then
HOSTNAME="localhost"
fi;
if [ ! $USERNAME ]; then
USERNAME="postgres"
fi;
###########################
#### START THE BACKUPS ####
###########################
FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
echo "Making backup directory in $FINAL_BACKUP_DIR"
if ! mkdir -p $FINAL_BACKUP_DIR; then
echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go and fix it!" 1>&2
exit 1;
fi;
#######################
### GLOBALS BACKUPS ###
#######################
echo -e "\n\nPerforming globals backup"
echo -e "--------------------------------------------\n"
if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
then
echo "Globals backup"
if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip > $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
echo "[!!ERROR!!] Failed to produce globals backup" 1>&2
else
mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress $FINAL_BACKUP_DIR"globals".sql.gz
fi
else
echo "None"
fi
###########################
### SCHEMA-ONLY BACKUPS ###
###########################
for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
do
SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~ '$SCHEMA_ONLY_DB'"
done
SCHEMA_ONLY_QUERY="select datname from pg_database where false $SCHEMA_ONLY_CLAUSE order by datname;"
echo -e "\n\nPerforming schema-only backups"
echo -e "--------------------------------------------\n"
SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c "$SCHEMA_ONLY_QUERY" postgres`
echo -e "The following databases were matched for schema-only backup:\n${SCHEMA_ONLY_DB_LIST}\n"
for DATABASE in $SCHEMA_ONLY_DB_LIST
do
echo "Schema-only backup of $DATABASE"
if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" | gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
echo "[!!ERROR!!] Failed to backup database schema of $DATABASE" 1>&2
else
mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
fi
done
###########################
###### FULL BACKUPS #######
###########################
for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
do
EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and datname !~ '$SCHEMA_ONLY_DB'"
done
FULL_BACKUP_QUERY="select datname from pg_database where not datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by datname;"
echo -e "\n\nPerforming full backups"
echo -e "--------------------------------------------\n"
for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c "$FULL_BACKUP_QUERY" postgres`
do
if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
then
echo "Plain backup of $DATABASE"
if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" | gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
echo "[!!ERROR!!] Failed to produce plain backup database $DATABASE" 1>&2
else
mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress $FINAL_BACKUP_DIR"$DATABASE".sql.gz
fi
fi
if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
then
echo "Custom backup of $DATABASE"
if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
echo "[!!ERROR!!] Failed to produce custom backup database $DATABASE" 1>&2
else
mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress $FINAL_BACKUP_DIR"$DATABASE".custom
fi
fi
done
echo -e "\nAll database backups complete!"
I'm appreciate if anyone know how to correct this?
thank you.
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
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]pg_dumpall: could not connect to database: FATAL
2019-02-25 16:50 pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-25 16:54 ` gilberto.castillo@etecsa.cu
1 sibling, 0 replies; 24+ messages in thread
From: gilberto.castillo@etecsa.cu @ 2019-02-25 16:54 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: pgsql-admin
Hi Pepe,
Is there a user postgres in your database?
Do you changer backup user?
El 2019-02-25 11:50, Pepe TD Vo escribió:
> good morning Expert DBAs,
>
> I created a script to do backup and I have faced the error of
>
>> Performing globals backup:
>> pg_dumpall: could not connect to database "template1":FATAL: Ident
>> authentication failed for user "postgres" fro globals backup. As
>> same as performing schema-only backups and full 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 but
> couldn't run from script even the script declared BACKUP_USER=postgres
>
> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the backup
> script working fine
>
> # VI PG_BACKUP.CONFIG
>
> ##############################
> ## POSTGRESQL BACKUP CONFIG ##
> ##############################
>
> # Optional system user to run backups as. If the user the script is
> running as doesn't match this
> # the script terminates. Leave blank to skip check.
> BACKUP_USER=
>
> # Optional hostname to adhere to pg_hba policies. Will default to
> "localhost" if none specified.
> HOSTNAME="hostname"
>
> # Optional username to connect to database as. Will default to
> "postgres" if none specified.
> USERNAME="postgres"
>
> # This dir will be created if it doesn't exist. This must be writable
> by the user the script is
> # running as.
> BACKUP_DIR=/home/backups/database/postgresql/
>
> # List of strings to match against in database name, separated by
> space or comma, for which we only
> # wish to keep a backup of the schema, not the data. Any database
> names which contain any of these
> # values will be considered candidates. (e.g. "system_log" will match
> "dev_system_log_2010-01")
> SCHEMA_ONLY_LIST=""
>
> # Will produce a custom-format backup if set to "yes"
> ENABLE_CUSTOM_BACKUPS=yes
>
> # Will produce a gzipped plain-format backup if set to "yes"
> ENABLE_PLAIN_BACKUPS=yes
>
> # Will produce gzipped sql file containing the cluster globals, like
> users and passwords, if set to "yes"
> ENABLE_GLOBALS_BACKUPS=yes
>
> #### SETTINGS FOR ROTATED BACKUPS ####
>
> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
> DAY_OF_WEEK_TO_KEEP=5
>
> # Number of days to keep daily backups
> DAYS_TO_KEEP=7
>
> # How many weeks to keep weekly backups
> WEEKS_TO_KEEP=5
>
> ######################################
>
> #VI PG_BACKUP.SH
>
> #!/bin/bash
>
> ###########################
> ####### LOAD CONFIG #######
> ###########################
>
> while [ $# -gt 0 ]; do
> case $1 in
> -c)
> if [ -r "$2" ]; then
> source "$2"
> shift 2
> else
> ${ECHO} "Unreadable config file
> \"$2\"" 1>&2
> exit 1
> fi
> ;;
> *)
> ${ECHO} "Unknown Option \"$1\"" 1>&2
> exit 2
> ;;
> esac
> done
>
> if [ $# = 0 ]; then
> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
> source $SCRIPTPATH/pg_backup.config
> fi;
>
> ###########################
> #### PRE-BACKUP CHECKS ####
> ###########################
>
> # Make sure we're running as the required backup user
> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
> exit 1;
> fi;
>
> ###########################
> ### INITIALISE DEFAULTS ###
> ###########################
>
> if [ ! $HOSTNAME ]; then
> HOSTNAME="localhost"
> fi;
>
> if [ ! $USERNAME ]; then
> USERNAME="postgres"
> fi;
>
> ###########################
> #### START THE BACKUPS ####
> ###########################
>
> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>
> echo "Making backup directory in $FINAL_BACKUP_DIR"
>
> if ! mkdir -p $FINAL_BACKUP_DIR; then
> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go and
> fix it!" 1>&2
> exit 1;
> fi;
>
> #######################
> ### GLOBALS BACKUPS ###
> #######################
>
> echo -e "\n\nPerforming globals backup"
> echo -e "--------------------------------------------\n"
>
> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
> then
> echo "Globals backup"
>
> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
> echo "[!!ERROR!!] Failed to produce globals backup"
> 1>&2
> else
> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
> $FINAL_BACKUP_DIR"globals".sql.gz
> fi
> else
> echo "None"
> fi
>
> ###########################
> ### SCHEMA-ONLY BACKUPS ###
> ###########################
>
> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> do
> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
> '$SCHEMA_ONLY_DB'"
> done
>
> SCHEMA_ONLY_QUERY="select datname from pg_database where false
> $SCHEMA_ONLY_CLAUSE order by datname;"
>
> echo -e "\n\nPerforming schema-only backups"
> echo -e "--------------------------------------------\n"
>
> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> "$SCHEMA_ONLY_QUERY" postgres`
>
> echo -e "The following databases were matched for schema-only
> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>
> for DATABASE in $SCHEMA_ONLY_DB_LIST
> do
> echo "Schema-only backup of $DATABASE"
>
> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
> echo "[!!ERROR!!] Failed to backup database schema of
> $DATABASE" 1>&2
> else
> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
> fi
> done
>
> ###########################
> ###### FULL BACKUPS #######
> ###########################
>
> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> do
> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
> datname !~ '$SCHEMA_ONLY_DB'"
> done
>
> FULL_BACKUP_QUERY="select datname from pg_database where not
> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
> datname;"
>
> echo -e "\n\nPerforming full backups"
> echo -e "--------------------------------------------\n"
>
> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> "$FULL_BACKUP_QUERY" postgres`
> do
> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
> then
> echo "Plain backup of $DATABASE"
>
> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
> echo "[!!ERROR!!] Failed to produce plain backup database
> $DATABASE" 1>&2
> else
> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
> fi
> fi
>
> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
> then
> echo "Custom backup of $DATABASE"
>
> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" -f
> $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
> echo "[!!ERROR!!] Failed to produce custom backup database
> $DATABASE" 1>&2
> else
> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
> $FINAL_BACKUP_DIR"$DATABASE".custom
> fi
> fi
>
> done
>
> echo -e "\nAll database backups complete!"
>
> I'm appreciate if anyone know how to correct this?
>
> thank you.
>
> 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
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: pg_dumpall: could not connect to database: FATAL
2019-02-25 16:50 pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-25 17:28 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-25 18:48 ` Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
1 sibling, 1 reply; 24+ messages in thread
From: Shreeyansh Dba @ 2019-02-25 17:28 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: pgsql-admin
Hi Pepe,
It seems your are using os user for taking the backup.
When you run command line commands against the postgres database and they
ask for the user and password that is the database user postgres
and its associated password, so when you do something like: psql -d
template1 -U postgres the password you will be prompted for is your_db_user
password
Now the above also depends on what is set in pg_hba.conf for the various
combinations of host, database, user and auth_method.
For more information see
https://www.postgresql.org/docs/9.5/static/client-authentication.html
Thanks & Regards,
*Shreeyansh DBA Team*
www.shreeyansh.com
On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
> good morning Expert DBAs,
>
> I created a script to do backup and I have faced the error of
>
> Performing globals backup:
> pg_dumpall: could not connect to database "template1":FATAL: Ident
> authentication failed for user "postgres" fro globals backup. As same as
> performing schema-only backups and full 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 but couldn't
> run from script even the script declared BACKUP_USER=postgres
>
>
> If I take the syntax, *-h "$HOSTNAME" -U "$USERNAME"* out and the backup
> script working fine
>
> *# vi pg_backup.config*
>
> ################################ POSTGRESQL BACKUP CONFIG ################################
> # Optional system user to run backups as. If the user the script is running as doesn't match this# the script terminates. Leave blank to skip check.BACKUP_USER=
> # Optional hostname to adhere to pg_hba policies. Will default to "localhost" if none specified.HOSTNAME="hostname"
> # Optional username to connect to database as. Will default to "postgres" if none specified.USERNAME="postgres"
> # This dir will be created if it doesn't exist. This must be writable by the user the script is# running as.BACKUP_DIR=/home/backups/database/postgresql/
> # List of strings to match against in database name, separated by space or comma, for which we only# wish to keep a backup of the schema, not the data. Any database names which contain any of these# values will be considered candidates. (e.g. "system_log" will match "dev_system_log_2010-01")SCHEMA_ONLY_LIST=""
> # Will produce a custom-format backup if set to "yes"ENABLE_CUSTOM_BACKUPS=yes
> # Will produce a gzipped plain-format backup if set to "yes"ENABLE_PLAIN_BACKUPS=yes
> # Will produce gzipped sql file containing the cluster globals, like users and passwords, if set to "yes"ENABLE_GLOBALS_BACKUPS=yes
>
> #### SETTINGS FOR ROTATED BACKUPS ####
> # Which day to take the weekly backup from (1-7 = Monday-Sunday)DAY_OF_WEEK_TO_KEEP=5
> # Number of days to keep daily backupsDAYS_TO_KEEP=7
> # How many weeks to keep weekly backupsWEEKS_TO_KEEP=5
> ######################################
>
>
> *#vi pg_backup.sh*
>
> #!/bin/bash
>
> ################################## LOAD CONFIG ##################################
> while [ $# -gt 0 ]; do
> case $1 in
> -c)
> if [ -r "$2" ]; then
> source "$2"
> shift 2
> else
> ${ECHO} "Unreadable config file \"$2\"" 1>&2
> exit 1
> fi
> ;;
> *)
> ${ECHO} "Unknown Option \"$1\"" 1>&2
> exit 2
> ;;
> esacdone
> if [ $# = 0 ]; then
> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
> source $SCRIPTPATH/pg_backup.configfi;
> ############################### PRE-BACKUP CHECKS ###############################
> # Make sure we're running as the required backup userif [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
> exit 1;fi;
>
> ############################## INITIALISE DEFAULTS ##############################
> if [ ! $HOSTNAME ]; then
> HOSTNAME="localhost"fi;
> if [ ! $USERNAME ]; then
> USERNAME="postgres"fi;
>
> ############################### START THE BACKUPS ###############################
>
> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
> echo "Making backup directory in $FINAL_BACKUP_DIR"
> if ! mkdir -p $FINAL_BACKUP_DIR; then
> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go and fix it!" 1>&2
> exit 1;fi;
>
> ########################## GLOBALS BACKUPS ##########################
> echo -e "\n\nPerforming globals backup"echo -e "--------------------------------------------\n"
> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]then
> echo "Globals backup"
>
> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip > $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
> echo "[!!ERROR!!] Failed to produce globals backup" 1>&2
> else
> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress $FINAL_BACKUP_DIR"globals".sql.gz
> fielse
> echo "None"fi
>
> ############################## SCHEMA-ONLY BACKUPS ##############################
> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }do
> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~ '$SCHEMA_ONLY_DB'"done
> SCHEMA_ONLY_QUERY="select datname from pg_database where false $SCHEMA_ONLY_CLAUSE order by datname;"
> echo -e "\n\nPerforming schema-only backups"echo -e "--------------------------------------------\n"
> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c "$SCHEMA_ONLY_QUERY" postgres`
> echo -e "The following databases were matched for schema-only backup:\n${SCHEMA_ONLY_DB_LIST}\n"
> for DATABASE in $SCHEMA_ONLY_DB_LISTdo
> echo "Schema-only backup of $DATABASE"
>
> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" | gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
> echo "[!!ERROR!!] Failed to backup database schema of $DATABASE" 1>&2
> else
> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
> fidone
>
> ################################# FULL BACKUPS ##################################
> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }do
> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and datname !~ '$SCHEMA_ONLY_DB'"done
> FULL_BACKUP_QUERY="select datname from pg_database where not datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by datname;"
> echo -e "\n\nPerforming full backups"echo -e "--------------------------------------------\n"
> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c "$FULL_BACKUP_QUERY" postgres`do
> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
> then
> echo "Plain backup of $DATABASE"
>
> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" | gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
> echo "[!!ERROR!!] Failed to produce plain backup database $DATABASE" 1>&2
> else
> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress $FINAL_BACKUP_DIR"$DATABASE".sql.gz
> fi
> fi
>
> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
> then
> echo "Custom backup of $DATABASE"
>
> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
> echo "[!!ERROR!!] Failed to produce custom backup database $DATABASE" 1>&2
> else
> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress $FINAL_BACKUP_DIR"$DATABASE".custom
> fi
> fi
> done
> echo -e "\nAll database backups complete!"
>
>
> I'm appreciate if anyone know how to correct this?
>
> thank you.
>
> 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
>
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: pg_dumpall: could not connect to database: FATAL
2019-02-25 16:50 pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 17:28 ` Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
@ 2019-02-25 18:48 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 18:58 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
0 siblings, 1 reply; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-25 18:48 UTC (permalink / raw)
To: Shreeyansh Dba <shreeyansh2014@gmail.com>; +Cc: pgsql-admin
Thank you for your information. I saw this document this morning and I did check my pg_hba.conf and for local host and tried to connect to the template1/0 and/or other database with postgres fine without prompting me for the password
#psql -d template0 -U postgrestemplate0-##psql -d template1 -U postgrestemplate1-##psql -d CIDR -U postgresCIDR-##psql -d postgres -U postgrespostgres-#
and a pg_hba.conf:
"
#TYPE DATABASE USER ADDRESS METHODlocal all all trusthost all all 127.0.0.1/32 trusthost all all ::1/128 trust
#allo replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127..0.1/32 trusthost replication all ::1/128 trust
the problem is I'm not sure I need to reconfigure pg_hba.conf with database with user postgres or not?
When I'm connecting into the each database and the "show pg_hba.conf" show nothing.
postgres-# show pg_hba.confpostgres-#
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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
Hi Pepe,
It seems your are using os user for taking the backup.
When you run command line commands against the postgres database and they ask for the user and password that is the database user postgres
and its associated password, so when you do something like: psql -d template1 -U postgres the password you will be prompted for is your_db_user password
Now the above also depends on what is set in pg_hba.conf for the various combinations of host, database, user and auth_method.
For more information see https://www.postgresql.org/docs/9.5/static/client-authentication.html
Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com
On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
good morning Expert DBAs,
I created a script to do backup and I have faced the error of
Performing globals backup:pg_dumpall: could not connect to database "template1":FATAL: Ident authentication failed for user "postgres" fro globals backup. As same as performing schema-only backups and full 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 but couldn't run from script even the script declared BACKUP_USER=postgres
If I take the syntax, -h "$HOSTNAME" -U "$USERNAME" out and the backup script working fine
# vi pg_backup.config##############################
## POSTGRESQL BACKUP CONFIG ##
##############################
# Optional system user to run backups as. If the user the script is running as doesn't match this
# the script terminates. Leave blank to skip check.
BACKUP_USER=
# Optional hostname to adhere to pg_hba policies. Will default to "localhost" if none specified.
HOSTNAME="hostname"
# Optional username to connect to database as. Will default to "postgres" if none specified.
USERNAME="postgres"
# This dir will be created if it doesn't exist. This must be writable by the user the script is
# running as.
BACKUP_DIR=/home/backups/database/postgresql/
# List of strings to match against in database name, separated by space or comma, for which we only
# wish to keep a backup of the schema, not the data. Any database names which contain any of these
# values will be considered candidates. (e.g. "system_log" will match "dev_system_log_2010-01")
SCHEMA_ONLY_LIST=""
# Will produce a custom-format backup if set to "yes"
ENABLE_CUSTOM_BACKUPS=yes
# Will produce a gzipped plain-format backup if set to "yes"
ENABLE_PLAIN_BACKUPS=yes
# Will produce gzipped sql file containing the cluster globals, like users and passwords, if set to "yes"
ENABLE_GLOBALS_BACKUPS=yes
#### SETTINGS FOR ROTATED BACKUPS ####
# Which day to take the weekly backup from (1-7 = Monday-Sunday)
DAY_OF_WEEK_TO_KEEP=5
# Number of days to keep daily backups
DAYS_TO_KEEP=7
# How many weeks to keep weekly backups
WEEKS_TO_KEEP=5
######################################
#vi pg_backup.sh#!/bin/bash###########################
####### LOAD CONFIG #######
###########################
while [ $# -gt 0 ]; do
case $1 in
-c)
if [ -r "$2" ]; then
source "$2"
shift 2
else
${ECHO} "Unreadable config file \"$2\"" 1>&2
exit 1
fi
;;
*)
${ECHO} "Unknown Option \"$1\"" 1>&2
exit 2
;;
esac
done
if [ $# = 0 ]; then
SCRIPTPATH=$(cd ${0%/*} && pwd -P)
source $SCRIPTPATH/pg_backup.config
fi;
###########################
#### PRE-BACKUP CHECKS ####
###########################
# Make sure we're running as the required backup user
if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
exit 1;
fi;
###########################
### INITIALISE DEFAULTS ###
###########################
if [ ! $HOSTNAME ]; then
HOSTNAME="localhost"
fi;
if [ ! $USERNAME ]; then
USERNAME="postgres"
fi;
###########################
#### START THE BACKUPS ####
###########################
FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
echo "Making backup directory in $FINAL_BACKUP_DIR"
if ! mkdir -p $FINAL_BACKUP_DIR; then
echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go and fix it!" 1>&2
exit 1;
fi;
#######################
### GLOBALS BACKUPS ###
#######################
echo -e "\n\nPerforming globals backup"
echo -e "--------------------------------------------\n"
if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
then
echo "Globals backup"
if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip > $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
echo "[!!ERROR!!] Failed to produce globals backup" 1>&2
else
mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress $FINAL_BACKUP_DIR"globals".sql.gz
fi
else
echo "None"
fi
###########################
### SCHEMA-ONLY BACKUPS ###
###########################
for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
do
SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~ '$SCHEMA_ONLY_DB'"
done
SCHEMA_ONLY_QUERY="select datname from pg_database where false $SCHEMA_ONLY_CLAUSE order by datname;"
echo -e "\n\nPerforming schema-only backups"
echo -e "--------------------------------------------\n"
SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c "$SCHEMA_ONLY_QUERY" postgres`
echo -e "The following databases were matched for schema-only backup:\n${SCHEMA_ONLY_DB_LIST}\n"
for DATABASE in $SCHEMA_ONLY_DB_LIST
do
echo "Schema-only backup of $DATABASE"
if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" | gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
echo "[!!ERROR!!] Failed to backup database schema of $DATABASE" 1>&2
else
mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
fi
done
###########################
###### FULL BACKUPS #######
###########################
for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
do
EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and datname !~ '$SCHEMA_ONLY_DB'"
done
FULL_BACKUP_QUERY="select datname from pg_database where not datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by datname;"
echo -e "\n\nPerforming full backups"
echo -e "--------------------------------------------\n"
for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c "$FULL_BACKUP_QUERY" postgres`
do
if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
then
echo "Plain backup of $DATABASE"
if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" | gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
echo "[!!ERROR!!] Failed to produce plain backup database $DATABASE" 1>&2
else
mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress $FINAL_BACKUP_DIR"$DATABASE".sql.gz
fi
fi
if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
then
echo "Custom backup of $DATABASE"
if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
echo "[!!ERROR!!] Failed to produce custom backup database $DATABASE" 1>&2
else
mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress $FINAL_BACKUP_DIR"$DATABASE".custom
fi
fi
done
echo -e "\nAll database backups complete!"
I'm appreciate if anyone know how to correct this?
thank you.
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
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-25 16:50 pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 17:28 ` Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-25 18:48 ` Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-25 18:58 ` gilberto.castillo@etecsa.cu
2019-02-26 14:11 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
0 siblings, 1 reply; 24+ messages in thread
From: gilberto.castillo@etecsa.cu @ 2019-02-25 18:58 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>; pgsql-admin
El 2019-02-25 13:48, Pepe TD Vo escribió:
> Thank you for your information.
> I saw this document this morning and I did check my pg_hba.conf and
> for local host and tried to connect to the template1/0 and/or other
> database with postgres fine without prompting me for the password
>
> #psql -d template0 -U postgres
> template0-#
> #psql -d template1 -U postgres
> template1-#
>
> #psql -d CIDR -U postgres
> CIDR-#
> #psql -d postgres -U postgres
> postgres-#
>
> and a pg_hba.conf:
>
> "
>
> #TYPE DATABASE USER ADDRESS METHOD
> local all all trust
> host all all 127.0.0.1/32 trust
> host all all ::1/128 trust
Look here the IP only connect to localhost. From where Are your running
the script?
> #allo replication connections from localhost, by a user with the
> replication privilege
> local replication all trust
> host replication all 127..0.1/32 trust
> host replication all ::1/128 trust
>
> the problem is I'm not sure I need to reconfigure pg_hba.conf with
> database with user postgres or not?
>
> When I'm connecting into the each database and the "show pg_hba.conf"
> show nothing.
>
> postgres-# show pg_hba.conf
> postgres-#
>
> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
> <shreeyansh2014@gmail.com> wrote:
>
> Hi Pepe,
>
> It seems your are using os user for taking the backup.
>
> When you run command line commands against the postgres database and
> they ask for the user and password that is the database user postgres
> and its associated password, so when you do something like: psql -d
> template1 -U postgres the password you will be prompted for is
> your_db_user password
>
> Now the above also depends on what is set in pg_hba.conf for the
> various combinations of host, database, user and auth_method.
>
> For more information see
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>
> Thanks & Regards,
> SHREEYANSH DBA TEAM
> www.shreeyansh.com [1]
>
> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
>
>> good morning Expert DBAs,
>>
>> I created a script to do backup and I have faced the error of
>>
>>> Performing globals backup:
>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
>>> authentication failed for user "postgres" fro globals backup. As
>>> same as performing schema-only backups and full 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 but
>> couldn't run from script even the script declared
>> BACKUP_USER=postgres
>>
>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>> backup script working fine
>>
>> # VI PG_BACKUP.CONFIG
>>
>> ##############################
>> ## POSTGRESQL BACKUP CONFIG ##
>> ##############################
>>
>> # Optional system user to run backups as. If the user the script is
>> running as doesn't match this
>> # the script terminates. Leave blank to skip check.
>> BACKUP_USER=
>>
>> # Optional hostname to adhere to pg_hba policies. Will default to
>> "localhost" if none specified.
>> HOSTNAME="hostname"
>>
>> # Optional username to connect to database as. Will default to
>> "postgres" if none specified.
>> USERNAME="postgres"
>>
>> # This dir will be created if it doesn't exist. This must be
>> writable by the user the script is
>> # running as.
>> BACKUP_DIR=/home/backups/database/postgresql/
>>
>> # List of strings to match against in database name, separated by
>> space or comma, for which we only
>> # wish to keep a backup of the schema, not the data. Any database
>> names which contain any of these
>> # values will be considered candidates. (e.g. "system_log" will
>> match "dev_system_log_2010-01")
>> SCHEMA_ONLY_LIST=""
>>
>> # Will produce a custom-format backup if set to "yes"
>> ENABLE_CUSTOM_BACKUPS=yes
>>
>> # Will produce a gzipped plain-format backup if set to "yes"
>> ENABLE_PLAIN_BACKUPS=yes
>>
>> # Will produce gzipped sql file containing the cluster globals, like
>> users and passwords, if set to "yes"
>> ENABLE_GLOBALS_BACKUPS=yes
>>
>> #### SETTINGS FOR ROTATED BACKUPS ####
>>
>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>> DAY_OF_WEEK_TO_KEEP=5
>>
>> # Number of days to keep daily backups
>> DAYS_TO_KEEP=7
>>
>> # How many weeks to keep weekly backups
>> WEEKS_TO_KEEP=5
>>
>> ######################################
>>
>> #VI PG_BACKUP.SH
>>
>> #!/bin/bash
>>
>> ###########################
>> ####### LOAD CONFIG #######
>> ###########################
>>
>> while [ $# -gt 0 ]; do
>> case $1 in
>> -c)
>> if [ -r "$2" ]; then
>> source "$2"
>> shift 2
>> else
>> ${ECHO} "Unreadable config file
>> \"$2\"" 1>&2
>> exit 1
>> fi
>> ;;
>> *)
>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>> exit 2
>> ;;
>> esac
>> done
>>
>> if [ $# = 0 ]; then
>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>> source $SCRIPTPATH/pg_backup.config
>> fi;
>>
>> ###########################
>> #### PRE-BACKUP CHECKS ####
>> ###########################
>>
>> # Make sure we're running as the required backup user
>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>> exit 1;
>> fi;
>>
>> ###########################
>> ### INITIALISE DEFAULTS ###
>> ###########################
>>
>> if [ ! $HOSTNAME ]; then
>> HOSTNAME="localhost"
>> fi;
>>
>> if [ ! $USERNAME ]; then
>> USERNAME="postgres"
>> fi;
>>
>> ###########################
>> #### START THE BACKUPS ####
>> ###########################
>>
>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>>
>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>>
>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>> and fix it!" 1>&2
>> exit 1;
>> fi;
>>
>> #######################
>> ### GLOBALS BACKUPS ###
>> #######################
>>
>> echo -e "\n\nPerforming globals backup"
>> echo -e "--------------------------------------------\n"
>>
>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>> then
>> echo "Globals backup"
>>
>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>> echo "[!!ERROR!!] Failed to produce globals backup"
>> 1>&2
>> else
>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>> $FINAL_BACKUP_DIR"globals".sql.gz
>> fi
>> else
>> echo "None"
>> fi
>>
>> ###########################
>> ### SCHEMA-ONLY BACKUPS ###
>> ###########################
>>
>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>> do
>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>> '$SCHEMA_ONLY_DB'"
>> done
>>
>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>> $SCHEMA_ONLY_CLAUSE order by datname;"
>>
>> echo -e "\n\nPerforming schema-only backups"
>> echo -e "--------------------------------------------\n"
>>
>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>> "$SCHEMA_ONLY_QUERY" postgres`
>>
>> echo -e "The following databases were matched for schema-only
>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>>
>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>> do
>> echo "Schema-only backup of $DATABASE"
>>
>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
>> echo "[!!ERROR!!] Failed to backup database schema of
>> $DATABASE" 1>&2
>> else
>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>> fi
>> done
>>
>> ###########################
>> ###### FULL BACKUPS #######
>> ###########################
>>
>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>> do
>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>> datname !~ '$SCHEMA_ONLY_DB'"
>> done
>>
>> FULL_BACKUP_QUERY="select datname from pg_database where not
>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
>> datname;"
>>
>> echo -e "\n\nPerforming full backups"
>> echo -e "--------------------------------------------\n"
>>
>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>> "$FULL_BACKUP_QUERY" postgres`
>> do
>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>> then
>> echo "Plain backup of $DATABASE"
>>
>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>> echo "[!!ERROR!!] Failed to produce plain backup
>> database $DATABASE" 1>&2
>> else
>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>> fi
>> fi
>>
>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>> then
>> echo "Custom backup of $DATABASE"
>>
>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>> echo "[!!ERROR!!] Failed to produce custom backup
>> database $DATABASE" 1>&2
>> else
>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>> $FINAL_BACKUP_DIR"$DATABASE".custom
>> fi
>> fi
>>
>> done
>>
>> echo -e "\nAll database backups complete!"
>>
>> I'm appreciate if anyone know how to correct this?
>>
>> thank you.
>>
>> 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
>
>
>
> Links:
> ------
> [1] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-25 16:50 pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 17:28 ` Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-25 18:48 ` Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 18:58 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
@ 2019-02-26 14:11 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 14:52 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
0 siblings, 1 reply; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-26 14:11 UTC (permalink / raw)
To: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
No sir. I have tried what your suggestion and still failed.
as root:
# export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as same as postgres:
#su - postgres
export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as the postgres, I can run pgdump dbname > output.sql
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
On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <gilberto.castillo@etecsa.cu> wrote:
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
Please, Check this:
root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
USERNAME="postgres"; DATABASE="postgres"
root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
"$USERNAME" "$DATABASE" > /tmp/postresp.sql
Password:
pg_dump: [archiver (db)] connection to database "postgres" failed:
FATAL: password authentication failed for user "postgres"
FATAL: password authentication failed for user "postgres"
Other:
root@gilbertoc:/home/gilbertoc# sudo su - postgres
postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/postresp.sql
/tmp/postresp.sql: Permiso denegado
Fine:
postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/salvapostgres.backup
postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
/tmp/salvapostgres.backup
>
> 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> <gilberto.castillo@etecsa.cu> wrote:
>
> El 2019-02-25 13:48, Pepe TD Vo escribió:
>
>> Thank you for your information.
>
>> I saw this document this morning and I did check my pg_hba.conf and
>
>> for local host and tried to connect to the template1/0 and/or other
>
>> database with postgres fine without prompting me for the password
>
>>
>
>> #psql -d template0 -U postgres
>
>> template0-#
>
>> #psql -d template1 -U postgres
>
>> template1-#
>
>>
>
>> #psql -d CIDR -U postgres
>
>> CIDR-#
>
>> #psql -d postgres -U postgres
>
>> postgres-#
>
>>
>
>> and a pg_hba.conf:
>
>>
>
>> "
>
>>
>
>> #TYPE DATABASE USER ADDRESS METHOD
>
>> local all all trust
>
>> host all all 127.0.0.1/32 trust
>
>> host all all ::1/128 trust
>
> Look here the IP only connect to localhost. From where Are your
> running
>
> the script?
>
>> #allo replication connections from localhost, by a user with the
>
>> replication privilege
>
>> local replication all trust
>
>> host replication all 127..0.1/32 trust
>
>> host replication all ::1/128 trust
>
>>
>
>> the problem is I'm not sure I need to reconfigure pg_hba.conf with
>
>> database with user postgres or not?
>
>>
>
>> When I'm connecting into the each database and the "show
> pg_hba.conf"
>
>> show nothing.
>
>>
>
>> postgres-# show pg_hba.conf
>
>> postgres-#
>
>>
>
>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>
>> <shreeyansh2014@gmail.com> wrote:
>
>>
>
>> Hi Pepe,
>
>>
>
>> It seems your are using os user for taking the backup.
>
>>
>
>> When you run command line commands against the postgres database and
>
>> they ask for the user and password that is the database user
> postgres
>
>> and its associated password, so when you do something like: psql -d
>
>> template1 -U postgres the password you will be prompted for is
>
>> your_db_user password
>
>>
>
>> Now the above also depends on what is set in pg_hba.conf for the
>
>> various combinations of host, database, user and auth_method.
>
>>
>
>> For more information see
>
>>
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>
>>
>
>> Thanks & Regards,
>
>> SHREEYANSH DBA TEAM
>
>> www.shreeyansh.com [1]
>
>>
>
>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> wrote:
>
>>
>
>>> good morning Expert DBAs,
>
>>>
>
>>> I created a script to do backup and I have faced the error of
>
>>>
>
>>>> Performing globals backup:
>
>>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
>
>>>> authentication failed for user "postgres" fro globals backup. As
>
>>>> same as performing schema-only backups and full 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 but
>
>>> couldn't run from script even the script declared
>
>>> BACKUP_USER=postgres
>
>>>
>
>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>
>>> backup script working fine
>
>>>
>
>>> # VI PG_BACKUP.CONFIG
>
>>>
>
>>> ##############################
>
>>> ## POSTGRESQL BACKUP CONFIG ##
>
>>> ##############################
>
>>>
>
>>> # Optional system user to run backups as. If the user the script
> is
>
>>> running as doesn't match this
>
>>> # the script terminates. Leave blank to skip check.
>
>>> BACKUP_USER=
>
>>>
>
>>> # Optional hostname to adhere to pg_hba policies. Will default to
>
>>> "localhost" if none specified.
>
>>> HOSTNAME="hostname"
>
>>>
>
>>> # Optional username to connect to database as. Will default to
>
>>> "postgres" if none specified.
>
>>> USERNAME="postgres"
>
>>>
>
>>> # This dir will be created if it doesn't exist. This must be
>
>>> writable by the user the script is
>
>>> # running as.
>
>>> BACKUP_DIR=/home/backups/database/postgresql/
>
>>>
>
>>> # List of strings to match against in database name, separated by
>
>>> space or comma, for which we only
>
>>> # wish to keep a backup of the schema, not the data. Any database
>
>>> names which contain any of these
>
>>> # values will be considered candidates. (e.g. "system_log" will
>
>>> match "dev_system_log_2010-01")
>
>>> SCHEMA_ONLY_LIST=""
>
>>>
>
>>> # Will produce a custom-format backup if set to "yes"
>
>>> ENABLE_CUSTOM_BACKUPS=yes
>
>>>
>
>>> # Will produce a gzipped plain-format backup if set to "yes"
>
>>> ENABLE_PLAIN_BACKUPS=yes
>
>>>
>
>>> # Will produce gzipped sql file containing the cluster globals,
> like
>
>>> users and passwords, if set to "yes"
>
>>> ENABLE_GLOBALS_BACKUPS=yes
>
>>>
>
>>> #### SETTINGS FOR ROTATED BACKUPS ####
>
>>>
>
>>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>
>>> DAY_OF_WEEK_TO_KEEP=5
>
>>>
>
>>> # Number of days to keep daily backups
>
>>> DAYS_TO_KEEP=7
>
>>>
>
>>> # How many weeks to keep weekly backups
>
>>> WEEKS_TO_KEEP=5
>
>>>
>
>>> ######################################
>
>>>
>
>>> #VI PG_BACKUP.SH
>
>>>
>
>>> #!/bin/bash
>
>>>
>
>>> ###########################
>
>>> ####### LOAD CONFIG #######
>
>>> ###########################
>
>>>
>
>>> while [ $# -gt 0 ]; do
>
>>> case $1 in
>
>>> -c)
>
>>> if [ -r "$2" ]; then
>
>>> source "$2"
>
>>> shift 2
>
>>> else
>
>>> ${ECHO} "Unreadable config file
>
>>> \"$2\"" 1>&2
>
>>> exit 1
>
>>> fi
>
>>> ;;
>
>>> *)
>
>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>
>>> exit 2
>
>>> ;;
>
>>> esac
>
>>> done
>
>>>
>
>>> if [ $# = 0 ]; then
>
>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>
>>> source $SCRIPTPATH/pg_backup.config
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### PRE-BACKUP CHECKS ####
>
>>> ###########################
>
>>>
>
>>> # Make sure we're running as the required backup user
>
>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
>
>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> ### INITIALISE DEFAULTS ###
>
>>> ###########################
>
>>>
>
>>> if [ ! $HOSTNAME ]; then
>
>>> HOSTNAME="localhost"
>
>>> fi;
>
>>>
>
>>> if [ ! $USERNAME ]; then
>
>>> USERNAME="postgres"
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### START THE BACKUPS ####
>
>>> ###########################
>
>>>
>
>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>
>>>
>
>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>
>>>
>
>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>
>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>
>>> and fix it!" 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> #######################
>
>>> ### GLOBALS BACKUPS ###
>
>>> #######################
>
>>>
>
>>> echo -e "\n\nPerforming globals backup"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Globals backup"
>
>>>
>
>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce globals backup"
>
>>> 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz
>
>>> fi
>
>>> else
>
>>> echo "None"
>
>>> fi
>
>>>
>
>>> ###########################
>
>>> ### SCHEMA-ONLY BACKUPS ###
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>
>>> '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>
>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>
>>>
>
>>> echo -e "\n\nPerforming schema-only backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$SCHEMA_ONLY_QUERY" postgres`
>
>>>
>
>>> echo -e "The following databases were matched for schema-only
>
>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>
>>>
>
>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>
>>> do
>
>>> echo "Schema-only backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to backup database schema of
>
>>> $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>
>>> fi
>
>>> done
>
>>>
>
>>> ###########################
>
>>> ###### FULL BACKUPS #######
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>
>>> datname !~ '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>
>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
>
>>> datname;"
>
>>>
>
>>> echo -e "\n\nPerforming full backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$FULL_BACKUP_QUERY" postgres`
>
>>> do
>
>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Plain backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce plain backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>
>>> fi
>
>>> fi
>
>>>
>
>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Custom backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>
>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce custom backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>
>>> fi
>
>>> fi
>
>>>
>
>>> done
>
>>>
>
>>> echo -e "\nAll database backups complete!"
>
>>>
>
>>> I'm appreciate if anyone know how to correct this?
>
>>>
>
>>> thank you.
>
>>>
>
>>> 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
>
>>
>
>>
>
>>
>
>> Links:
>
>> ------
>
>> [1] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-25 16:50 pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 17:28 ` Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-25 18:48 ` Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 18:58 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
2019-02-26 14:11 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-26 14:52 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 15:19 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
0 siblings, 1 reply; 24+ messages in thread
From: Shreeyansh Dba @ 2019-02-26 14:52 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
The error message says the authentication method used isn't trust. Can you
please share your pg_hba.conf file entries.
Thanks & Regards,
*Shreeyansh DBA Team*
www.shr Hi Pepe eeyansh.com <http://www.shreeyansh.com;
On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
> No sir. I have tried what your suggestion and still failed.
>
> as root:
>
> # export HOSTNAME="localhost"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
> # export HOSTNAME="127.0.0.1"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
>
> as same as postgres:
>
> #su - postgres
>
> export HOSTNAME="localhost"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
> # export HOSTNAME="127.0.0.1"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
>
> as the postgres, I can run pgdump dbname > output.sql
>
> 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
>
>
> On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <
> gilberto.castillo@etecsa.cu> wrote:
>
>
> El 2019-02-25 14:16, Pepe TD Vo escribió:
> > I am running script in local host (same db server)
>
> El 2019-02-25 14:16, Pepe TD Vo escribió:
> > I am running script in local host (same db server)
>
>
> Please, Check this:
>
> root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
> USERNAME="postgres"; DATABASE="postgres"
>
> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
> Password:
> pg_dump: [archiver (db)] connection to database "postgres" failed:
> FATAL: password authentication failed for user "postgres"
> FATAL: password authentication failed for user "postgres"
>
>
> Other:
>
> root@gilbertoc:/home/gilbertoc# sudo su - postgres
>
> postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
> DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/postresp.sql
> /tmp/postresp.sql: Permiso denegado
>
>
> Fine:
>
> postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
> DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/salvapostgres.backup
> postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
> /tmp/salvapostgres.backup
>
>
> >
> > 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> > <gilberto.castillo@etecsa.cu> wrote:
> >
> > El 2019-02-25 13:48, Pepe TD Vo escribió:
> >
> >> Thank you for your information.
> >
> >> I saw this document this morning and I did check my pg_hba.conf and
> >
> >> for local host and tried to connect to the template1/0 and/or other
> >
> >> database with postgres fine without prompting me for the password
> >
> >>
> >
> >> #psql -d template0 -U postgres
> >
> >> template0-#
> >
> >> #psql -d template1 -U postgres
> >
> >> template1-#
> >
> >>
> >
> >> #psql -d CIDR -U postgres
> >
> >> CIDR-#
> >
> >> #psql -d postgres -U postgres
> >
> >> postgres-#
> >
> >>
> >
> >> and a pg_hba.conf:
> >
> >>
> >
> >> "
> >
> >>
> >
> >> #TYPE DATABASE USER ADDRESS METHOD
> >
> >> local all all trust
> >
> >> host all all 127.0.0.1/32 trust
> >
> >> host all all ::1/128 trust
> >
> > Look here the IP only connect to localhost. From where Are your
> > running
> >
> > the script?
> >
> >> #allo replication connections from localhost, by a user with the
> >
> >> replication privilege
> >
> >> local replication all trust
> >
> >> host replication all 127..0.1/32 trust
> >
> >> host replication all ::1/128 trust
> >
> >>
> >
> >> the problem is I'm not sure I need to reconfigure pg_hba.conf with
> >
> >> database with user postgres or not?
> >
> >>
> >
> >> When I'm connecting into the each database and the "show
> > pg_hba.conf"
> >
> >> show nothing.
> >
> >>
> >
> >> postgres-# show pg_hba.conf
> >
> >> postgres-#
> >
> >>
> >
> >> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
> >
> >> <shreeyansh2014@gmail.com> wrote:
> >
> >>
> >
> >> Hi Pepe,
> >
> >>
> >
> >> It seems your are using os user for taking the backup.
> >
> >>
> >
> >> When you run command line commands against the postgres database and
> >
> >> they ask for the user and password that is the database user
> > postgres
> >
> >> and its associated password, so when you do something like: psql -d
> >
> >> template1 -U postgres the password you will be prompted for is
> >
> >> your_db_user password
> >
> >>
> >
> >> Now the above also depends on what is set in pg_hba.conf for the
> >
> >> various combinations of host, database, user and auth_method.
> >
> >>
> >
> >> For more information see
> >
> >>
> > https://www.postgresql.org/docs/9.5/static/client-authentication.html
> >
> >>
> >
> >> Thanks & Regards,
> >
> >> SHREEYANSH DBA TEAM
> >
> >> www.shreeyansh.com [1]
> >
> >>
> >
> >> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> > wrote:
> >
> >>
> >
> >>> good morning Expert DBAs,
> >
> >>>
> >
> >>> I created a script to do backup and I have faced the error of
> >
> >>>
> >
> >>>> Performing globals backup:
> >
> >>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
> >
> >>>> authentication failed for user "postgres" fro globals backup. As
> >
> >>>> same as performing schema-only backups and full 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 but
> >
> >>> couldn't run from script even the script declared
> >
> >>> BACKUP_USER=postgres
> >
> >>>
> >
> >>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
> >
> >>> backup script working fine
> >
> >>>
> >
> >>> # VI PG_BACKUP.CONFIG
> >
> >>>
> >
> >>> ##############################
> >
> >>> ## POSTGRESQL BACKUP CONFIG ##
> >
> >>> ##############################
> >
> >>>
> >
> >>> # Optional system user to run backups as. If the user the script
> > is
> >
> >>> running as doesn't match this
> >
> >>> # the script terminates. Leave blank to skip check.
> >
> >>> BACKUP_USER=
> >
> >>>
> >
> >>> # Optional hostname to adhere to pg_hba policies. Will default to
> >
> >>> "localhost" if none specified.
> >
> >>> HOSTNAME="hostname"
> >
> >>>
> >
> >>> # Optional username to connect to database as. Will default to
> >
> >>> "postgres" if none specified.
> >
> >>> USERNAME="postgres"
> >
> >>>
> >
> >>> # This dir will be created if it doesn't exist. This must be
> >
> >>> writable by the user the script is
> >
> >>> # running as.
> >
> >>> BACKUP_DIR=/home/backups/database/postgresql/
> >
> >>>
> >
> >>> # List of strings to match against in database name, separated by
> >
> >>> space or comma, for which we only
> >
> >>> # wish to keep a backup of the schema, not the data. Any database
> >
> >>> names which contain any of these
> >
> >>> # values will be considered candidates. (e.g. "system_log" will
> >
> >>> match "dev_system_log_2010-01")
> >
> >>> SCHEMA_ONLY_LIST=""
> >
> >>>
> >
> >>> # Will produce a custom-format backup if set to "yes"
> >
> >>> ENABLE_CUSTOM_BACKUPS=yes
> >
> >>>
> >
> >>> # Will produce a gzipped plain-format backup if set to "yes"
> >
> >>> ENABLE_PLAIN_BACKUPS=yes
> >
> >>>
> >
> >>> # Will produce gzipped sql file containing the cluster globals,
> > like
> >
> >>> users and passwords, if set to "yes"
> >
> >>> ENABLE_GLOBALS_BACKUPS=yes
> >
> >>>
> >
> >>> #### SETTINGS FOR ROTATED BACKUPS ####
> >
> >>>
> >
> >>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
> >
> >>> DAY_OF_WEEK_TO_KEEP=5
> >
> >>>
> >
> >>> # Number of days to keep daily backups
> >
> >>> DAYS_TO_KEEP=7
> >
> >>>
> >
> >>> # How many weeks to keep weekly backups
> >
> >>> WEEKS_TO_KEEP=5
> >
> >>>
> >
> >>> ######################################
> >
> >>>
> >
> >>> #VI PG_BACKUP.SH
> >
> >>>
> >
> >>> #!/bin/bash
> >
> >>>
> >
> >>> ###########################
> >
> >>> ####### LOAD CONFIG #######
> >
> >>> ###########################
> >
> >>>
> >
> >>> while [ $# -gt 0 ]; do
> >
> >>> case $1 in
> >
> >>> -c)
> >
> >>> if [ -r "$2" ]; then
> >
> >>> source "$2"
> >
> >>> shift 2
> >
> >>> else
> >
> >>> ${ECHO} "Unreadable config file
> >
> >>> \"$2\"" 1>&2
> >
> >>> exit 1
> >
> >>> fi
> >
> >>> ;;
> >
> >>> *)
> >
> >>> ${ECHO} "Unknown Option \"$1\"" 1>&2
> >
> >>> exit 2
> >
> >>> ;;
> >
> >>> esac
> >
> >>> done
> >
> >>>
> >
> >>> if [ $# = 0 ]; then
> >
> >>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
> >
> >>> source $SCRIPTPATH/pg_backup.config
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> #### PRE-BACKUP CHECKS ####
> >
> >>> ###########################
> >
> >>>
> >
> >>> # Make sure we're running as the required backup user
> >
> >>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
> >
> >>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
> >
> >>> exit 1;
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> ### INITIALISE DEFAULTS ###
> >
> >>> ###########################
> >
> >>>
> >
> >>> if [ ! $HOSTNAME ]; then
> >
> >>> HOSTNAME="localhost"
> >
> >>> fi;
> >
> >>>
> >
> >>> if [ ! $USERNAME ]; then
> >
> >>> USERNAME="postgres"
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> #### START THE BACKUPS ####
> >
> >>> ###########################
> >
> >>>
> >
> >>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
> >
> >>>
> >
> >>> echo "Making backup directory in $FINAL_BACKUP_DIR"
> >
> >>>
> >
> >>> if ! mkdir -p $FINAL_BACKUP_DIR; then
> >
> >>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
> >
> >>> and fix it!" 1>&2
> >
> >>> exit 1;
> >
> >>> fi;
> >
> >>>
> >
> >>> #######################
> >
> >>> ### GLOBALS BACKUPS ###
> >
> >>> #######################
> >
> >>>
> >
> >>> echo -e "\n\nPerforming globals backup"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Globals backup"
> >
> >>>
> >
> >>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
> >
> >>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce globals backup"
> >
> >>> 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"globals".sql.gz
> >
> >>> fi
> >
> >>> else
> >
> >>> echo "None"
> >
> >>> fi
> >
> >>>
> >
> >>> ###########################
> >
> >>> ### SCHEMA-ONLY BACKUPS ###
> >
> >>> ###########################
> >
> >>>
> >
> >>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> >
> >>> do
> >
> >>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
> >
> >>> '$SCHEMA_ONLY_DB'"
> >
> >>> done
> >
> >>>
> >
> >>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
> >
> >>> $SCHEMA_ONLY_CLAUSE order by datname;"
> >
> >>>
> >
> >>> echo -e "\n\nPerforming schema-only backups"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> >
> >>> "$SCHEMA_ONLY_QUERY" postgres`
> >
> >>>
> >
> >>> echo -e "The following databases were matched for schema-only
> >
> >>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
> >
> >>>
> >
> >>> for DATABASE in $SCHEMA_ONLY_DB_LIST
> >
> >>> do
> >
> >>> echo "Schema-only backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> >
> >>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to backup database schema of
> >
> >>> $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
> >
> >>> fi
> >
> >>> done
> >
> >>>
> >
> >>> ###########################
> >
> >>> ###### FULL BACKUPS #######
> >
> >>> ###########################
> >
> >>>
> >
> >>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> >
> >>> do
> >
> >>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
> >
> >>> datname !~ '$SCHEMA_ONLY_DB'"
> >
> >>> done
> >
> >>>
> >
> >>> FULL_BACKUP_QUERY="select datname from pg_database where not
> >
> >>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
> >
> >>> datname;"
> >
> >>>
> >
> >>> echo -e "\n\nPerforming full backups"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> >
> >>> "$FULL_BACKUP_QUERY" postgres`
> >
> >>> do
> >
> >>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Plain backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> >
> >>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce plain backup
> >
> >>> database $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
> >
> >>> fi
> >
> >>> fi
> >
> >>>
> >
> >>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Custom backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
> >
> >>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce custom backup
> >
> >>> database $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE".custom
> >
> >>> fi
> >
> >>> fi
> >
> >>>
> >
> >>> done
> >
> >>>
> >
> >>> echo -e "\nAll database backups complete!"
> >
> >>>
> >
> >>> I'm appreciate if anyone know how to correct this?
> >
> >>>
> >
> >>> thank you.
> >
> >>>
> >
> >>> 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
> >
> >>
> >
> >>
> >
> >>
> >
> >> Links:
> >
> >> ------
> >
> >> [1] http://www.shreeyansh.com/
>
>
>
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-25 16:50 pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 17:28 ` Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-25 18:48 ` Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 18:58 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
2019-02-26 14:11 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 14:52 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
@ 2019-02-26 15:19 ` gilberto.castillo@etecsa.cu
0 siblings, 0 replies; 24+ messages in thread
From: gilberto.castillo@etecsa.cu @ 2019-02-26 15:19 UTC (permalink / raw)
To: Shreeyansh Dba <shreeyansh2014@gmail.com>; +Cc: Pepe TD Vo <pepevo@yahoo.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Hello Pepe,
Please, Show we, Your pg_hba.
El 2019-02-26 09:52, Shreeyansh Dba escribió:
> The error message says the authentication method used isn't trust. Can
> you please share your pg_hba.conf file entries.
>
> Thanks & Regards,
> SHREEYANSH DBA TEAM
> www.shr Hi Pepe eeyansh.com [2]
>
> On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
>
>> No sir. I have tried what your suggestion and still failed.
>>
>> as root:
>>
>> # export HOSTNAME="localhost"
>> # export USERNAME="postgres"
>> # export DATABASE="postgres"
>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>> /tmp/postresp.sql
>>
>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>> FATAL: Ident authentication failed for user "postgres"
>>
>> # export HOSTNAME="127.0.0.1"
>> # export USERNAME="postgres"
>> # export DATABASE="postgres"
>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>> /tmp/postresp.sql
>>
>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>> FATAL: Ident authentication failed for user "postgres"
>>
>> as same as postgres:
>>
>> #su - postgres
>>
>> export HOSTNAME="localhost"
>> # export USERNAME="postgres"
>> # export DATABASE="postgres"
>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>> /tmp/postresp.sql
>>
>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>> FATAL: Ident authentication failed for user "postgres"
>>
>> # export HOSTNAME="127.0.0.1"
>> # export USERNAME="postgres"
>> # export DATABASE="postgres"
>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>> /tmp/postresp.sql
>>
>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>> FATAL: Ident authentication failed for user "postgres"
>>
>> as the postgres, I can run pgdump dbname > output.sql
>>
>> 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
>>
>> On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu"
>> <gilberto.castillo@etecsa.cu> wrote:
>>
>> El 2019-02-25 14:16, Pepe TD Vo escribió:
>>
>>> I am running script in local host (same db server)
>>
>> El 2019-02-25 14:16, Pepe TD Vo escribió:
>>
>>> I am running script in local host (same db server)
>>
>> Please, Check this:
>>
>> root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
>>
>> USERNAME="postgres"; DATABASE="postgres"
>>
>> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
>>
>> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>>
>> Password:
>>
>> pg_dump: [archiver (db)] connection to database "postgres" failed:
>>
>> FATAL: password authentication failed for user "postgres"
>>
>> FATAL: password authentication failed for user "postgres"
>>
>> Other:
>>
>> root@gilbertoc:/home/gilbertoc# sudo su - postgres
>>
>> postgres@gilbertoc:~$ export HOSTNAME="localhost";
>> USERNAME="postgres";
>>
>> DATABASE="postgres"
>>
>> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
>>
>> "$DATABASE" > /tmp/postresp.sql
>>
>> /tmp/postresp.sql: Permiso denegado
>>
>> Fine:
>>
>> postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1";
>> USERNAME="postgres";
>>
>> DATABASE="postgres"
>>
>> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
>>
>> "$DATABASE" > /tmp/salvapostgres.backup
>>
>> postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
>>
>> /tmp/salvapostgres.backup
>>
>>>
>>
>>> 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 Monday, February 25, 2019 1:58 PM,
>> "gilberto.castillo@etecsa.cu"
>>
>>> <gilberto.castillo@etecsa.cu> wrote:
>>
>>>
>>
>>> El 2019-02-25 13:48, Pepe TD Vo escribió:
>>
>>>
>>
>>>> Thank you for your information.
>>
>>>
>>
>>>> I saw this document this morning and I did check my pg_hba.conf
>> and
>>
>>>
>>
>>>> for local host and tried to connect to the template1/0 and/or
>> other
>>
>>>
>>
>>>> database with postgres fine without prompting me for the password
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> #psql -d template0 -U postgres
>>
>>>
>>
>>>> template0-#
>>
>>>
>>
>>>> #psql -d template1 -U postgres
>>
>>>
>>
>>>> template1-#
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> #psql -d CIDR -U postgres
>>
>>>
>>
>>>> CIDR-#
>>
>>>
>>
>>>> #psql -d postgres -U postgres
>>
>>>
>>
>>>> postgres-#
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> and a pg_hba.conf:
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> "
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> #TYPE DATABASE USER ADDRESS METHOD
>>
>>>
>>
>>>> local all all trust
>>
>>>
>>
>>>> host all all 127.0.0.1/32 [1] trust
>>
>>>
>>
>>>> host all all ::1/128 trust
>>
>>>
>>
>>> Look here the IP only connect to localhost. From where Are your
>>
>>> running
>>
>>>
>>
>>> the script?
>>
>>>
>>
>>>> #allo replication connections from localhost, by a user with the
>>
>>>
>>
>>>> replication privilege
>>
>>>
>>
>>>> local replication all trust
>>
>>>
>>
>>>> host replication all 127..0.1/32 trust
>>
>>>
>>
>>>> host replication all ::1/128 trust
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> the problem is I'm not sure I need to reconfigure pg_hba.conf
>> with
>>
>>>
>>
>>>> database with user postgres or not?
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> When I'm connecting into the each database and the "show
>>
>>> pg_hba.conf"
>>
>>>
>>
>>>> show nothing.
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> postgres-# show pg_hba.conf
>>
>>>
>>
>>>> postgres-#
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>>
>>>
>>
>>>> <shreeyansh2014@gmail.com> wrote:
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> Hi Pepe,
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> It seems your are using os user for taking the backup.
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> When you run command line commands against the postgres database
>> and
>>
>>>
>>
>>>> they ask for the user and password that is the database user
>>
>>> postgres
>>
>>>
>>
>>>> and its associated password, so when you do something like: psql
>> -d
>>
>>>
>>
>>>> template1 -U postgres the password you will be prompted for is
>>
>>>
>>
>>>> your_db_user password
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> Now the above also depends on what is set in pg_hba.conf for the
>>
>>>
>>
>>>> various combinations of host, database, user and auth_method.
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> For more information see
>>
>>>
>>
>>>>
>>
>>>
>>
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> Thanks & Regards,
>>
>>>
>>
>>>> SHREEYANSH DBA TEAM
>>
>>>
>>
>>>> www.shreeyansh.com [2] [1]
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
>>
>>> wrote:
>>
>>>
>>
>>>>
>>
>>>
>>
>>>>> good morning Expert DBAs,
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> I created a script to do backup and I have faced the error of
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>>> Performing globals backup:
>>
>>>
>>
>>>>>> pg_dumpall: could not connect to database "template1":FATAL:
>> Ident
>>
>>>
>>
>>>>>> authentication failed for user "postgres" fro globals backup.
>> As
>>
>>>
>>
>>>>>> same as performing schema-only backups and full 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 but
>>
>>>
>>
>>>>> couldn't run from script even the script declared
>>
>>>
>>
>>>>> BACKUP_USER=postgres
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>>
>>>
>>
>>>>> backup script working fine
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # VI PG_BACKUP.CONFIG
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ##############################
>>
>>>
>>
>>>>> ## POSTGRESQL BACKUP CONFIG ##
>>
>>>
>>
>>>>> ##############################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Optional system user to run backups as. If the user the
>> script
>>
>>> is
>>
>>>
>>
>>>>> running as doesn't match this
>>
>>>
>>
>>>>> # the script terminates. Leave blank to skip check.
>>
>>>
>>
>>>>> BACKUP_USER=
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Optional hostname to adhere to pg_hba policies. Will default
>> to
>>
>>>
>>
>>>>> "localhost" if none specified.
>>
>>>
>>
>>>>> HOSTNAME="hostname"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Optional username to connect to database as. Will default to
>>
>>>
>>
>>>>> "postgres" if none specified.
>>
>>>
>>
>>>>> USERNAME="postgres"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # This dir will be created if it doesn't exist. This must be
>>
>>>
>>
>>>>> writable by the user the script is
>>
>>>
>>
>>>>> # running as.
>>
>>>
>>
>>>>> BACKUP_DIR=/home/backups/database/postgresql/
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # List of strings to match against in database name, separated
>> by
>>
>>>
>>
>>>>> space or comma, for which we only
>>
>>>
>>
>>>>> # wish to keep a backup of the schema, not the data. Any
>> database
>>
>>>
>>
>>>>> names which contain any of these
>>
>>>
>>
>>>>> # values will be considered candidates. (e.g. "system_log" will
>>
>>>
>>
>>>>> match "dev_system_log_2010-01")
>>
>>>
>>
>>>>> SCHEMA_ONLY_LIST=""
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Will produce a custom-format backup if set to "yes"
>>
>>>
>>
>>>>> ENABLE_CUSTOM_BACKUPS=yes
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Will produce a gzipped plain-format backup if set to "yes"
>>
>>>
>>
>>>>> ENABLE_PLAIN_BACKUPS=yes
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Will produce gzipped sql file containing the cluster globals,
>>
>>> like
>>
>>>
>>
>>>>> users and passwords, if set to "yes"
>>
>>>
>>
>>>>> ENABLE_GLOBALS_BACKUPS=yes
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> #### SETTINGS FOR ROTATED BACKUPS ####
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>>
>>>
>>
>>>>> DAY_OF_WEEK_TO_KEEP=5
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Number of days to keep daily backups
>>
>>>
>>
>>>>> DAYS_TO_KEEP=7
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # How many weeks to keep weekly backups
>>
>>>
>>
>>>>> WEEKS_TO_KEEP=5
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ######################################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> #VI PG_BACKUP.SH
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> #!/bin/bash
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> ####### LOAD CONFIG #######
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> while [ $# -gt 0 ]; do
>>
>>>
>>
>>>>> case $1 in
>>
>>>
>>
>>>>> -c)
>>
>>>
>>
>>>>> if [ -r "$2" ]; then
>>
>>>
>>
>>>>> source "$2"
>>
>>>
>>
>>>>> shift 2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> ${ECHO} "Unreadable config file
>>
>>>
>>
>>>>> \"$2\"" 1>&2
>>
>>>
>>
>>>>> exit 1
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> ;;
>>
>>>
>>
>>>>> *)
>>
>>>
>>
>>>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>>
>>>
>>
>>>>> exit 2
>>
>>>
>>
>>>>> ;;
>>
>>>
>>
>>>>> esac
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ $# = 0 ]; then
>>
>>>
>>
>>>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>>
>>>
>>
>>>>> source $SCRIPTPATH/pg_backup.config
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> #### PRE-BACKUP CHECKS ####
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Make sure we're running as the required backup user
>>
>>>
>>
>>>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ];
>> then
>>
>>>
>>
>>>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>>
>>>
>>
>>>>> exit 1;
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> ### INITIALISE DEFAULTS ###
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ ! $HOSTNAME ]; then
>>
>>>
>>
>>>>> HOSTNAME="localhost"
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ ! $USERNAME ]; then
>>
>>>
>>
>>>>> USERNAME="postgres"
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> #### START THE BACKUPS ####
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>>
>>>
>>
>>>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>>
>>>
>>
>>>>> and fix it!" 1>&2
>>
>>>
>>
>>>>> exit 1;
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> #######################
>>
>>>
>>
>>>>> ### GLOBALS BACKUPS ###
>>
>>>
>>
>>>>> #######################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "\n\nPerforming globals backup"
>>
>>>
>>
>>>>> echo -e "--------------------------------------------\n"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>>
>>>
>>
>>>>> then
>>
>>>
>>
>>>>> echo "Globals backup"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>>
>>>
>>
>>>>> echo "[!!ERROR!!] Failed to produce globals backup"
>>
>>>
>>
>>>>> 1>&2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"globals".sql.gz
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> echo "None"
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> ### SCHEMA-ONLY BACKUPS ###
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>>
>>>
>>
>>>>> do
>>
>>>
>>
>>>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>>
>>>
>>
>>>>> '$SCHEMA_ONLY_DB'"
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>>
>>>
>>
>>>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "\n\nPerforming schema-only backups"
>>
>>>
>>
>>>>> echo -e "--------------------------------------------\n"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>>
>>>
>>
>>>>> "$SCHEMA_ONLY_QUERY" postgres`
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "The following databases were matched for schema-only
>>
>>>
>>
>>>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>>
>>>
>>
>>>>> do
>>
>>>
>>
>>>>> echo "Schema-only backup of $DATABASE"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>>
>>>
>>
>>>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress;
>> then
>>
>>>
>>
>>>>> echo "[!!ERROR!!] Failed to backup database schema of
>>
>>>
>>
>>>>> $DATABASE" 1>&2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> ###### FULL BACKUPS #######
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>>
>>>
>>
>>>>> do
>>
>>>
>>
>>>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>>
>>>
>>
>>>>> datname !~ '$SCHEMA_ONLY_DB'"
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>>
>>>
>>
>>>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order
>> by
>>
>>>
>>
>>>>> datname;"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "\n\nPerforming full backups"
>>
>>>
>>
>>>>> echo -e "--------------------------------------------\n"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>>
>>>
>>
>>>>> "$FULL_BACKUP_QUERY" postgres`
>>
>>>
>>
>>>>> do
>>
>>>
>>
>>>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>>
>>>
>>
>>>>> then
>>
>>>
>>
>>>>> echo "Plain backup of $DATABASE"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>>
>>>
>>
>>>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>>
>>>
>>
>>>>> echo "[!!ERROR!!] Failed to produce plain backup
>>
>>>
>>
>>>>> database $DATABASE" 1>&2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>>
>>>
>>
>>>>> then
>>
>>>
>>
>>>>> echo "Custom backup of $DATABASE"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>>
>>>
>>
>>>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>>
>>>
>>
>>>>> echo "[!!ERROR!!] Failed to produce custom backup
>>
>>>
>>
>>>>> database $DATABASE" 1>&2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "\nAll database backups complete!"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> I'm appreciate if anyone know how to correct this?
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> thank you.
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> 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
>>
>>>
>>
>>>>
>>
>>>
>>
>>>>
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> Links:
>>
>>>
>>
>>>> ------
>>
>>>
>>
>>>> [1] http://www.shreeyansh.com/
>
>
> Links:
> ------
> [1] http://127.0.0.1/32
> [2] http://www.shreeyansh.com
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
@ 2019-02-26 15:36 Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 15:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
0 siblings, 2 replies; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-26 15:36 UTC (permalink / raw)
To: Shreeyansh Dba <shreeyansh2014@gmail.com>; +Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
yes mam'm/sir. I already posted it
here it is again.
#vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 trusthost replication all ::1/128 trust
I also found pg_hba.conf on both folders /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the script is not working even run from the command prompt.
#vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
host all power_user 0.0.0.0/0 md5host all other_user 0.0.0.0/0 md5host all storageLoader 0.0.0.0/0 md5
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 rusthost replication all ::1/128 trust
why do I have 3 pg_hba.conf? which one should use?
thank you for looking into it.
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
On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
The error message says the authentication method used isn't trust. Can you please share your pg_hba.conf file entries.
Thanks & Regards,
Shreeyansh DBA Team
www.shr Hi Pepe eeyansh.com
On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
No sir. I have tried what your suggestion and still failed.
as root:
# export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as same as postgres:
#su - postgres
export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as the postgres, I can run pgdump dbname > output.sql
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
On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <gilberto.castillo@etecsa.cu> wrote:
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
Please, Check this:
root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
USERNAME="postgres"; DATABASE="postgres"
root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
"$USERNAME" "$DATABASE" > /tmp/postresp.sql
Password:
pg_dump: [archiver (db)] connection to database "postgres" failed:
FATAL: password authentication failed for user "postgres"
FATAL: password authentication failed for user "postgres"
Other:
root@gilbertoc:/home/gilbertoc# sudo su - postgres
postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/postresp.sql
/tmp/postresp.sql: Permiso denegado
Fine:
postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/salvapostgres.backup
postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
/tmp/salvapostgres.backup
>
> 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> <gilberto.castillo@etecsa.cu> wrote:
>
> El 2019-02-25 13:48, Pepe TD Vo escribió:
>
>> Thank you for your information.
>
>> I saw this document this morning and I did check my pg_hba.conf and
>
>> for local host and tried to connect to the template1/0 and/or other
>
>> database with postgres fine without prompting me for the password
>
>>
>
>> #psql -d template0 -U postgres
>
>> template0-#
>
>> #psql -d template1 -U postgres
>
>> template1-#
>
>>
>
>> #psql -d CIDR -U postgres
>
>> CIDR-#
>
>> #psql -d postgres -U postgres
>
>> postgres-#
>
>>
>
>> and a pg_hba.conf:
>
>>
>
>> "
>
>>
>
>> #TYPE DATABASE USER ADDRESS METHOD
>
>> local all all trust
>
>> host all all 127.0.0.1/32 trust
>
>> host all all ::1/128 trust
>
> Look here the IP only connect to localhost. From where Are your
> running
>
> the script?
>
>> #allo replication connections from localhost, by a user with the
>
>> replication privilege
>
>> local replication all trust
>
>> host replication all 127..0.1/32 trust
>
>> host replication all ::1/128 trust
>
>>
>
>> the problem is I'm not sure I need to reconfigure pg_hba.conf with
>
>> database with user postgres or not?
>
>>
>
>> When I'm connecting into the each database and the "show
> pg_hba.conf"
>
>> show nothing.
>
>>
>
>> postgres-# show pg_hba.conf
>
>> postgres-#
>
>>
>
>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>
>> <shreeyansh2014@gmail.com> wrote:
>
>>
>
>> Hi Pepe,
>
>>
>
>> It seems your are using os user for taking the backup.
>
>>
>
>> When you run command line commands against the postgres database and
>
>> they ask for the user and password that is the database user
> postgres
>
>> and its associated password, so when you do something like: psql -d
>
>> template1 -U postgres the password you will be prompted for is
>
>> your_db_user password
>
>>
>
>> Now the above also depends on what is set in pg_hba.conf for the
>
>> various combinations of host, database, user and auth_method.
>
>>
>
>> For more information see
>
>>
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>
>>
>
>> Thanks & Regards,
>
>> SHREEYANSH DBA TEAM
>
>> www.shreeyansh.com [1]
>
>>
>
>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> wrote:
>
>>
>
>>> good morning Expert DBAs,
>
>>>
>
>>> I created a script to do backup and I have faced the error of
>
>>>
>
>>>> Performing globals backup:
>
>>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
>
>>>> authentication failed for user "postgres" fro globals backup. As
>
>>>> same as performing schema-only backups and full 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 but
>
>>> couldn't run from script even the script declared
>
>>> BACKUP_USER=postgres
>
>>>
>
>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>
>>> backup script working fine
>
>>>
>
>>> # VI PG_BACKUP.CONFIG
>
>>>
>
>>> ##############################
>
>>> ## POSTGRESQL BACKUP CONFIG ##
>
>>> ##############################
>
>>>
>
>>> # Optional system user to run backups as. If the user the script
> is
>
>>> running as doesn't match this
>
>>> # the script terminates. Leave blank to skip check.
>
>>> BACKUP_USER=
>
>>>
>
>>> # Optional hostname to adhere to pg_hba policies. Will default to
>
>>> "localhost" if none specified.
>
>>> HOSTNAME="hostname"
>
>>>
>
>>> # Optional username to connect to database as. Will default to
>
>>> "postgres" if none specified.
>
>>> USERNAME="postgres"
>
>>>
>
>>> # This dir will be created if it doesn't exist. This must be
>
>>> writable by the user the script is
>
>>> # running as.
>
>>> BACKUP_DIR=/home/backups/database/postgresql/
>
>>>
>
>>> # List of strings to match against in database name, separated by
>
>>> space or comma, for which we only
>
>>> # wish to keep a backup of the schema, not the data. Any database
>
>>> names which contain any of these
>
>>> # values will be considered candidates. (e.g. "system_log" will
>
>>> match "dev_system_log_2010-01")
>
>>> SCHEMA_ONLY_LIST=""
>
>>>
>
>>> # Will produce a custom-format backup if set to "yes"
>
>>> ENABLE_CUSTOM_BACKUPS=yes
>
>>>
>
>>> # Will produce a gzipped plain-format backup if set to "yes"
>
>>> ENABLE_PLAIN_BACKUPS=yes
>
>>>
>
>>> # Will produce gzipped sql file containing the cluster globals,
> like
>
>>> users and passwords, if set to "yes"
>
>>> ENABLE_GLOBALS_BACKUPS=yes
>
>>>
>
>>> #### SETTINGS FOR ROTATED BACKUPS ####
>
>>>
>
>>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>
>>> DAY_OF_WEEK_TO_KEEP=5
>
>>>
>
>>> # Number of days to keep daily backups
>
>>> DAYS_TO_KEEP=7
>
>>>
>
>>> # How many weeks to keep weekly backups
>
>>> WEEKS_TO_KEEP=5
>
>>>
>
>>> ######################################
>
>>>
>
>>> #VI PG_BACKUP.SH
>
>>>
>
>>> #!/bin/bash
>
>>>
>
>>> ###########################
>
>>> ####### LOAD CONFIG #######
>
>>> ###########################
>
>>>
>
>>> while [ $# -gt 0 ]; do
>
>>> case $1 in
>
>>> -c)
>
>>> if [ -r "$2" ]; then
>
>>> source "$2"
>
>>> shift 2
>
>>> else
>
>>> ${ECHO} "Unreadable config file
>
>>> \"$2\"" 1>&2
>
>>> exit 1
>
>>> fi
>
>>> ;;
>
>>> *)
>
>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>
>>> exit 2
>
>>> ;;
>
>>> esac
>
>>> done
>
>>>
>
>>> if [ $# = 0 ]; then
>
>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>
>>> source $SCRIPTPATH/pg_backup.config
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### PRE-BACKUP CHECKS ####
>
>>> ###########################
>
>>>
>
>>> # Make sure we're running as the required backup user
>
>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
>
>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> ### INITIALISE DEFAULTS ###
>
>>> ###########################
>
>>>
>
>>> if [ ! $HOSTNAME ]; then
>
>>> HOSTNAME="localhost"
>
>>> fi;
>
>>>
>
>>> if [ ! $USERNAME ]; then
>
>>> USERNAME="postgres"
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### START THE BACKUPS ####
>
>>> ###########################
>
>>>
>
>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>
>>>
>
>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>
>>>
>
>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>
>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>
>>> and fix it!" 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> #######################
>
>>> ### GLOBALS BACKUPS ###
>
>>> #######################
>
>>>
>
>>> echo -e "\n\nPerforming globals backup"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Globals backup"
>
>>>
>
>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce globals backup"
>
>>> 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz
>
>>> fi
>
>>> else
>
>>> echo "None"
>
>>> fi
>
>>>
>
>>> ###########################
>
>>> ### SCHEMA-ONLY BACKUPS ###
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>
>>> '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>
>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>
>>>
>
>>> echo -e "\n\nPerforming schema-only backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$SCHEMA_ONLY_QUERY" postgres`
>
>>>
>
>>> echo -e "The following databases were matched for schema-only
>
>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>
>>>
>
>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>
>>> do
>
>>> echo "Schema-only backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to backup database schema of
>
>>> $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>
>>> fi
>
>>> done
>
>>>
>
>>> ###########################
>
>>> ###### FULL BACKUPS #######
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>
>>> datname !~ '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>
>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
>
>>> datname;"
>
>>>
>
>>> echo -e "\n\nPerforming full backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$FULL_BACKUP_QUERY" postgres`
>
>>> do
>
>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Plain backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce plain backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>
>>> fi
>
>>> fi
>
>>>
>
>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Custom backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>
>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce custom backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>
>>> fi
>
>>> fi
>
>>>
>
>>> done
>
>>>
>
>>> echo -e "\nAll database backups complete!"
>
>>>
>
>>> I'm appreciate if anyone know how to correct this?
>
>>>
>
>>> thank you.
>
>>>
>
>>> 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
>
>>
>
>>
>
>>
>
>> Links:
>
>> ------
>
>> [1] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-26 15:46 ` gilberto.castillo@etecsa.cu
2019-02-26 15:48 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
1 sibling, 1 reply; 24+ messages in thread
From: gilberto.castillo@etecsa.cu @ 2019-02-26 15:46 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Hi
You look your system Path but choose pg_hba
Remember:
-----------Begin------------
root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
USERNAME="postgres"; DATABASE="postgres"
root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
"$USERNAME" "$DATABASE" > /tmp/postresp.sql
root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
"$USERNAME" "$DATABASE" > /tmp/postresp.sql
Password:
pg_dump: [archiver (db)] connection to database "postgres" failed:
FATAL: password authentication failed for user "postgres"
FATAL: password authentication failed for user "postgres"
root@gilbertoc:/home/gilbertoc# sudo su - postgres
postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/postresp.sql
-su: /tmp/postresp.sql: Permiso denegado
postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/salvapostgres.backup
postgres@gilbertoc:~$
postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
/tmp/salvapostgres.backup
-----End-------------------------
El 2019-02-26 10:36, Pepe TD Vo escribió:
> yes mam'm/sir. I already posted it
>
> here it is again.
>
> #vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
>
> #TYPE DATABASE USER ADDRESS METHOD
> # "local" is for Unix domain socket connectiosn only
>
> local all all trust
>
> # IPv4 local connections:
>
> host all all 127.0.0.1/32 trust
>
> # IPv6 local connections:
>
> host all all ::1/128 trust
>
> # allow all replication connections from localhost, by a user with the
> replication privilege
> local replication all trust
> host replication all 127.0.0.1/32 trust
> host replication all ::1/128 trust
>
> I also found pg_hba.conf on both folders
> /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf).
> I modified it as above and the script is not working even run from
> the command prompt.
>
> #vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf &
> /var/lib/pgsql/data/pg_hba.conf)
>
> #TYPE DATABASE USER ADDRESS METHOD
> # "local" is for Unix domain socket connectiosn only
>
> local all all trust
>
> # IPv4 local connections:
>
> host all all 127.0.0.1/32 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 trust
>
> # allow all replication connections from localhost, by a user with the
> replication privilege
> local replication all trust
> host replication all 127.0.0.1/32 rust
> host replication all ::1/128 trust
>
> why do I have 3 pg_hba.conf? which one should use?
>
> thank you for looking into it.
>
> 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
>
> On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba
> <shreeyansh2014@gmail.com> wrote:
>
> The error message says the authentication method used isn't trust. Can
> you please share your pg_hba.conf file entries.
>
> Thanks & Regards,
> SHREEYANSH DBA TEAM
> www.shr Hi Pepe eeyansh.com [2]
>
> On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
>
>> No sir. I have tried what your suggestion and still failed.
>>
>> as root:
>>
>> # export HOSTNAME="localhost"
>> # export USERNAME="postgres"
>> # export DATABASE="postgres"
>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>> /tmp/postresp.sql
>>
>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>> FATAL: Ident authentication failed for user "postgres"
>>
>> # export HOSTNAME="127.0.0.1"
>> # export USERNAME="postgres"
>> # export DATABASE="postgres"
>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>> /tmp/postresp.sql
>>
>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>> FATAL: Ident authentication failed for user "postgres"
>>
>> as same as postgres:
>>
>> #su - postgres
>>
>> export HOSTNAME="localhost"
>> # export USERNAME="postgres"
>> # export DATABASE="postgres"
>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>> /tmp/postresp.sql
>>
>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>> FATAL: Ident authentication failed for user "postgres"
>>
>> # export HOSTNAME="127.0.0.1"
>> # export USERNAME="postgres"
>> # export DATABASE="postgres"
>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>> /tmp/postresp.sql
>>
>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>> FATAL: Ident authentication failed for user "postgres"
>>
>> as the postgres, I can run pgdump dbname > output.sql
>>
>> 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
>>
>> On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu"
>> <gilberto.castillo@etecsa.cu> wrote:
>>
>> El 2019-02-25 14:16, Pepe TD Vo escribió:
>>
>>> I am running script in local host (same db server)
>>
>> El 2019-02-25 14:16, Pepe TD Vo escribió:
>>
>>> I am running script in local host (same db server)
>>
>> Please, Check this:
>>
>> root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
>>
>> USERNAME="postgres"; DATABASE="postgres"
>>
>> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
>>
>> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>>
>> Password:
>>
>> pg_dump: [archiver (db)] connection to database "postgres" failed:
>>
>> FATAL: password authentication failed for user "postgres"
>>
>> FATAL: password authentication failed for user "postgres"
>>
>> Other:
>>
>> root@gilbertoc:/home/gilbertoc# sudo su - postgres
>>
>> postgres@gilbertoc:~$ export HOSTNAME="localhost";
>> USERNAME="postgres";
>>
>> DATABASE="postgres"
>>
>> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
>>
>> "$DATABASE" > /tmp/postresp.sql
>>
>> /tmp/postresp.sql: Permiso denegado
>>
>> Fine:
>>
>> postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1";
>> USERNAME="postgres";
>>
>> DATABASE="postgres"
>>
>> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
>>
>> "$DATABASE" > /tmp/salvapostgres.backup
>>
>> postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
>>
>> /tmp/salvapostgres.backup
>>
>>>
>>
>>> 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 Monday, February 25, 2019 1:58 PM,
>> "gilberto.castillo@etecsa.cu"
>>
>>> <gilberto.castillo@etecsa.cu> wrote:
>>
>>>
>>
>>> El 2019-02-25 13:48, Pepe TD Vo escribió:
>>
>>>
>>
>>>> Thank you for your information.
>>
>>>
>>
>>>> I saw this document this morning and I did check my pg_hba.conf
>> and
>>
>>>
>>
>>>> for local host and tried to connect to the template1/0 and/or
>> other
>>
>>>
>>
>>>> database with postgres fine without prompting me for the password
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> #psql -d template0 -U postgres
>>
>>>
>>
>>>> template0-#
>>
>>>
>>
>>>> #psql -d template1 -U postgres
>>
>>>
>>
>>>> template1-#
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> #psql -d CIDR -U postgres
>>
>>>
>>
>>>> CIDR-#
>>
>>>
>>
>>>> #psql -d postgres -U postgres
>>
>>>
>>
>>>> postgres-#
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> and a pg_hba.conf:
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> "
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> #TYPE DATABASE USER ADDRESS METHOD
>>
>>>
>>
>>>> local all all trust
>>
>>>
>>
>>>> host all all 127.0.0.1/32 [1] trust
>>
>>>
>>
>>>> host all all ::1/128 trust
>>
>>>
>>
>>> Look here the IP only connect to localhost. From where Are your
>>
>>> running
>>
>>>
>>
>>> the script?
>>
>>>
>>
>>>> #allo replication connections from localhost, by a user with the
>>
>>>
>>
>>>> replication privilege
>>
>>>
>>
>>>> local replication all trust
>>
>>>
>>
>>>> host replication all 127..0.1/32 trust
>>
>>>
>>
>>>> host replication all ::1/128 trust
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> the problem is I'm not sure I need to reconfigure pg_hba.conf
>> with
>>
>>>
>>
>>>> database with user postgres or not?
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> When I'm connecting into the each database and the "show
>>
>>> pg_hba.conf"
>>
>>>
>>
>>>> show nothing.
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> postgres-# show pg_hba.conf
>>
>>>
>>
>>>> postgres-#
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>>
>>>
>>
>>>> <shreeyansh2014@gmail.com> wrote:
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> Hi Pepe,
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> It seems your are using os user for taking the backup.
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> When you run command line commands against the postgres database
>> and
>>
>>>
>>
>>>> they ask for the user and password that is the database user
>>
>>> postgres
>>
>>>
>>
>>>> and its associated password, so when you do something like: psql
>> -d
>>
>>>
>>
>>>> template1 -U postgres the password you will be prompted for is
>>
>>>
>>
>>>> your_db_user password
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> Now the above also depends on what is set in pg_hba.conf for the
>>
>>>
>>
>>>> various combinations of host, database, user and auth_method.
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> For more information see
>>
>>>
>>
>>>>
>>
>>>
>>
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> Thanks & Regards,
>>
>>>
>>
>>>> SHREEYANSH DBA TEAM
>>
>>>
>>
>>>> www.shreeyansh.com [2] [1]
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
>>
>>> wrote:
>>
>>>
>>
>>>>
>>
>>>
>>
>>>>> good morning Expert DBAs,
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> I created a script to do backup and I have faced the error of
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>>> Performing globals backup:
>>
>>>
>>
>>>>>> pg_dumpall: could not connect to database "template1":FATAL:
>> Ident
>>
>>>
>>
>>>>>> authentication failed for user "postgres" fro globals backup.
>> As
>>
>>>
>>
>>>>>> same as performing schema-only backups and full 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 but
>>
>>>
>>
>>>>> couldn't run from script even the script declared
>>
>>>
>>
>>>>> BACKUP_USER=postgres
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>>
>>>
>>
>>>>> backup script working fine
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # VI PG_BACKUP.CONFIG
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ##############################
>>
>>>
>>
>>>>> ## POSTGRESQL BACKUP CONFIG ##
>>
>>>
>>
>>>>> ##############################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Optional system user to run backups as. If the user the
>> script
>>
>>> is
>>
>>>
>>
>>>>> running as doesn't match this
>>
>>>
>>
>>>>> # the script terminates. Leave blank to skip check.
>>
>>>
>>
>>>>> BACKUP_USER=
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Optional hostname to adhere to pg_hba policies. Will default
>> to
>>
>>>
>>
>>>>> "localhost" if none specified.
>>
>>>
>>
>>>>> HOSTNAME="hostname"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Optional username to connect to database as. Will default to
>>
>>>
>>
>>>>> "postgres" if none specified.
>>
>>>
>>
>>>>> USERNAME="postgres"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # This dir will be created if it doesn't exist. This must be
>>
>>>
>>
>>>>> writable by the user the script is
>>
>>>
>>
>>>>> # running as.
>>
>>>
>>
>>>>> BACKUP_DIR=/home/backups/database/postgresql/
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # List of strings to match against in database name, separated
>> by
>>
>>>
>>
>>>>> space or comma, for which we only
>>
>>>
>>
>>>>> # wish to keep a backup of the schema, not the data. Any
>> database
>>
>>>
>>
>>>>> names which contain any of these
>>
>>>
>>
>>>>> # values will be considered candidates. (e.g. "system_log" will
>>
>>>
>>
>>>>> match "dev_system_log_2010-01")
>>
>>>
>>
>>>>> SCHEMA_ONLY_LIST=""
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Will produce a custom-format backup if set to "yes"
>>
>>>
>>
>>>>> ENABLE_CUSTOM_BACKUPS=yes
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Will produce a gzipped plain-format backup if set to "yes"
>>
>>>
>>
>>>>> ENABLE_PLAIN_BACKUPS=yes
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Will produce gzipped sql file containing the cluster globals,
>>
>>> like
>>
>>>
>>
>>>>> users and passwords, if set to "yes"
>>
>>>
>>
>>>>> ENABLE_GLOBALS_BACKUPS=yes
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> #### SETTINGS FOR ROTATED BACKUPS ####
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>>
>>>
>>
>>>>> DAY_OF_WEEK_TO_KEEP=5
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Number of days to keep daily backups
>>
>>>
>>
>>>>> DAYS_TO_KEEP=7
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # How many weeks to keep weekly backups
>>
>>>
>>
>>>>> WEEKS_TO_KEEP=5
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ######################################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> #VI PG_BACKUP.SH
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> #!/bin/bash
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> ####### LOAD CONFIG #######
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> while [ $# -gt 0 ]; do
>>
>>>
>>
>>>>> case $1 in
>>
>>>
>>
>>>>> -c)
>>
>>>
>>
>>>>> if [ -r "$2" ]; then
>>
>>>
>>
>>>>> source "$2"
>>
>>>
>>
>>>>> shift 2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> ${ECHO} "Unreadable config file
>>
>>>
>>
>>>>> \"$2\"" 1>&2
>>
>>>
>>
>>>>> exit 1
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> ;;
>>
>>>
>>
>>>>> *)
>>
>>>
>>
>>>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>>
>>>
>>
>>>>> exit 2
>>
>>>
>>
>>>>> ;;
>>
>>>
>>
>>>>> esac
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ $# = 0 ]; then
>>
>>>
>>
>>>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>>
>>>
>>
>>>>> source $SCRIPTPATH/pg_backup.config
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> #### PRE-BACKUP CHECKS ####
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> # Make sure we're running as the required backup user
>>
>>>
>>
>>>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ];
>> then
>>
>>>
>>
>>>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>>
>>>
>>
>>>>> exit 1;
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> ### INITIALISE DEFAULTS ###
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ ! $HOSTNAME ]; then
>>
>>>
>>
>>>>> HOSTNAME="localhost"
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ ! $USERNAME ]; then
>>
>>>
>>
>>>>> USERNAME="postgres"
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> #### START THE BACKUPS ####
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>>
>>>
>>
>>>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>>
>>>
>>
>>>>> and fix it!" 1>&2
>>
>>>
>>
>>>>> exit 1;
>>
>>>
>>
>>>>> fi;
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> #######################
>>
>>>
>>
>>>>> ### GLOBALS BACKUPS ###
>>
>>>
>>
>>>>> #######################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "\n\nPerforming globals backup"
>>
>>>
>>
>>>>> echo -e "--------------------------------------------\n"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>>
>>>
>>
>>>>> then
>>
>>>
>>
>>>>> echo "Globals backup"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>>
>>>
>>
>>>>> echo "[!!ERROR!!] Failed to produce globals backup"
>>
>>>
>>
>>>>> 1>&2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"globals".sql.gz
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> echo "None"
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> ### SCHEMA-ONLY BACKUPS ###
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>>
>>>
>>
>>>>> do
>>
>>>
>>
>>>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>>
>>>
>>
>>>>> '$SCHEMA_ONLY_DB'"
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>>
>>>
>>
>>>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "\n\nPerforming schema-only backups"
>>
>>>
>>
>>>>> echo -e "--------------------------------------------\n"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>>
>>>
>>
>>>>> "$SCHEMA_ONLY_QUERY" postgres`
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "The following databases were matched for schema-only
>>
>>>
>>
>>>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>>
>>>
>>
>>>>> do
>>
>>>
>>
>>>>> echo "Schema-only backup of $DATABASE"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>>
>>>
>>
>>>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress;
>> then
>>
>>>
>>
>>>>> echo "[!!ERROR!!] Failed to backup database schema of
>>
>>>
>>
>>>>> $DATABASE" 1>&2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>> ###### FULL BACKUPS #######
>>
>>>
>>
>>>>> ###########################
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>>
>>>
>>
>>>>> do
>>
>>>
>>
>>>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>>
>>>
>>
>>>>> datname !~ '$SCHEMA_ONLY_DB'"
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>>
>>>
>>
>>>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order
>> by
>>
>>>
>>
>>>>> datname;"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "\n\nPerforming full backups"
>>
>>>
>>
>>>>> echo -e "--------------------------------------------\n"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>>
>>>
>>
>>>>> "$FULL_BACKUP_QUERY" postgres`
>>
>>>
>>
>>>>> do
>>
>>>
>>
>>>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>>
>>>
>>
>>>>> then
>>
>>>
>>
>>>>> echo "Plain backup of $DATABASE"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>>
>>>
>>
>>>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>>
>>>
>>
>>>>> echo "[!!ERROR!!] Failed to produce plain backup
>>
>>>
>>
>>>>> database $DATABASE" 1>&2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>>
>>>
>>
>>>>> then
>>
>>>
>>
>>>>> echo "Custom backup of $DATABASE"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>>
>>>
>>
>>>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>>
>>>
>>
>>>>> echo "[!!ERROR!!] Failed to produce custom backup
>>
>>>
>>
>>>>> database $DATABASE" 1>&2
>>
>>>
>>
>>>>> else
>>
>>>
>>
>>>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>>
>>>
>>
>>>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>> fi
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> done
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> echo -e "\nAll database backups complete!"
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> I'm appreciate if anyone know how to correct this?
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> thank you.
>>
>>>
>>
>>>>>
>>
>>>
>>
>>>>> 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
>>
>>>
>>
>>>>
>>
>>>
>>
>>>>
>>
>>>
>>
>>>>
>>
>>>
>>
>>>> Links:
>>
>>>
>>
>>>> ------
>>
>>>
>>
>>>> [1] http://www.shreeyansh.com/
>
>
>
> Links:
> ------
> [1] http://127.0.0.1/32
> [2] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 15:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
@ 2019-02-26 15:48 ` gilberto.castillo@etecsa.cu
0 siblings, 0 replies; 24+ messages in thread
From: gilberto.castillo@etecsa.cu @ 2019-02-26 15:48 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
El 2019-02-26 10:46, gilberto.castillo@etecsa.cu escribió:
> Hi
>
> You look your system Path but choose pg_hba
>
> Remember:
>
> -----------Begin------------
>
> root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
> USERNAME="postgres"; DATABASE="postgres"
>
> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
> Password:
> pg_dump: [archiver (db)] connection to database "postgres" failed:
> FATAL: password authentication failed for user "postgres"
> FATAL: password authentication failed for user "postgres"
>
> root@gilbertoc:/home/gilbertoc# sudo su - postgres
>
> postgres@gilbertoc:~$ export HOSTNAME="localhost";
> USERNAME="postgres"; DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/postresp.sql
> -su: /tmp/postresp.sql: Permiso denegado
>
> postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1";
> USERNAME="postgres"; DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/salvapostgres.backup
>
> postgres@gilbertoc:~$
>
> postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
> /tmp/salvapostgres.backup
>
> -----End-------------------------
>
>
> El 2019-02-26 10:36, Pepe TD Vo escribió:
>> yes mam'm/sir. I already posted it
>>
>> here it is again.
>>
>> #vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
>>
>> #TYPE DATABASE USER ADDRESS METHOD
>> # "local" is for Unix domain socket connectiosn only
>>
>> local all all trust
>>
>> # IPv4 local connections:
>>
>> host all all 127.0.0.1/32 trust
>>
>> # IPv6 local connections:
>>
>> host all all ::1/128 trust
>>
>> # allow all replication connections from localhost, by a user with the
>> replication privilege
>> local replication all trust
>> host replication all 127.0.0.1/32 trust
>> host replication all ::1/128 trust
>>
>> I also found pg_hba.conf on both folders
>> /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf).
>> I modified it as above and the script is not working even run from
>> the command prompt.
>>
>> #vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf &
>> /var/lib/pgsql/data/pg_hba.conf)
>>
>> #TYPE DATABASE USER ADDRESS METHOD
>> # "local" is for Unix domain socket connectiosn only
>>
>> local all all trust
>>
>> # IPv4 local connections:
>>
>> host all all 127.0.0.1/32 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 trust
>>
>> # allow all replication connections from localhost, by a user with the
>> replication privilege
>> local replication all trust
>> host replication all 127.0.0.1/32 rust
>> host replication all ::1/128 trust
>>
>> why do I have 3 pg_hba.conf? which one should use?
>>
>> thank you for looking into it.
>>
>> 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
>>
>> On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba
>> <shreeyansh2014@gmail.com> wrote:
>>
>> The error message says the authentication method used isn't trust. Can
>> you please share your pg_hba.conf file entries.
>>
>> Thanks & Regards,
>> SHREEYANSH DBA TEAM
>> www.shr Hi Pepe eeyansh.com [2]
>>
>> On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
>>
>>> No sir. I have tried what your suggestion and still failed.
>>>
>>> as root:
>>>
>>> # export HOSTNAME="localhost"
>>> # export USERNAME="postgres"
>>> # export DATABASE="postgres"
>>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>>> /tmp/postresp.sql
>>>
>>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>>> FATAL: Ident authentication failed for user "postgres"
>>>
>>> # export HOSTNAME="127.0.0.1"
>>> # export USERNAME="postgres"
>>> # export DATABASE="postgres"
>>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>>> /tmp/postresp.sql
>>>
>>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>>> FATAL: Ident authentication failed for user "postgres"
>>>
>>> as same as postgres:
>>>
>>> #su - postgres
>>>
>>> export HOSTNAME="localhost"
>>> # export USERNAME="postgres"
>>> # export DATABASE="postgres"
>>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>>> /tmp/postresp.sql
>>>
>>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>>> FATAL: Ident authentication failed for user "postgres"
>>>
>>> # export HOSTNAME="127.0.0.1"
>>> # export USERNAME="postgres"
>>> # export DATABASE="postgres"
>>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>>> /tmp/postresp.sql
>>>
>>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>>> FATAL: Ident authentication failed for user "postgres"
>>>
>>> as the postgres, I can run pgdump dbname > output.sql
>>>
>>> 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
>>>
>>> On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu"
>>> <gilberto.castillo@etecsa.cu> wrote:
>>>
>>> El 2019-02-25 14:16, Pepe TD Vo escribió:
>>>
>>>> I am running script in local host (same db server)
>>>
>>> El 2019-02-25 14:16, Pepe TD Vo escribió:
>>>
>>>> I am running script in local host (same db server)
>>>
>>> Please, Check this:
>>>
>>> root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
>>>
>>> USERNAME="postgres"; DATABASE="postgres"
>>>
>>> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
>>>
>>> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>>>
>>> Password:
>>>
>>> pg_dump: [archiver (db)] connection to database "postgres" failed:
>>>
>>> FATAL: password authentication failed for user "postgres"
>>>
>>> FATAL: password authentication failed for user "postgres"
>>>
>>> Other:
>>>
>>> root@gilbertoc:/home/gilbertoc# sudo su - postgres
>>>
>>> postgres@gilbertoc:~$ export HOSTNAME="localhost";
>>> USERNAME="postgres";
>>>
>>> DATABASE="postgres"
>>>
>>> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
>>>
>>> "$DATABASE" > /tmp/postresp.sql
>>>
>>> /tmp/postresp.sql: Permiso denegado
>>>
>>> Fine:
>>>
>>> postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1";
>>> USERNAME="postgres";
>>>
>>> DATABASE="postgres"
>>>
>>> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
>>>
>>> "$DATABASE" > /tmp/salvapostgres.backup
>>>
>>> postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
>>>
>>> /tmp/salvapostgres.backup
>>>
>>>>
>>>
>>>> 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 Monday, February 25, 2019 1:58 PM,
>>> "gilberto.castillo@etecsa.cu"
>>>
>>>> <gilberto.castillo@etecsa.cu> wrote:
>>>
>>>>
>>>
>>>> El 2019-02-25 13:48, Pepe TD Vo escribió:
>>>
>>>>
>>>
>>>>> Thank you for your information.
>>>
>>>>
>>>
>>>>> I saw this document this morning and I did check my pg_hba.conf
>>> and
>>>
>>>>
>>>
>>>>> for local host and tried to connect to the template1/0 and/or
>>> other
>>>
>>>>
>>>
>>>>> database with postgres fine without prompting me for the password
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> #psql -d template0 -U postgres
>>>
>>>>
>>>
>>>>> template0-#
>>>
>>>>
>>>
>>>>> #psql -d template1 -U postgres
>>>
>>>>
>>>
>>>>> template1-#
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> #psql -d CIDR -U postgres
>>>
>>>>
>>>
>>>>> CIDR-#
>>>
>>>>
>>>
>>>>> #psql -d postgres -U postgres
>>>
>>>>
>>>
>>>>> postgres-#
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> and a pg_hba.conf:
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> "
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> #TYPE DATABASE USER ADDRESS METHOD
>>>
>>>>
>>>
>>>>> local all all trust
>>>
>>>>
>>>
>>>>> host all all 127.0.0.1/32 [1] trust
>>>
>>>>
>>>
>>>>> host all all ::1/128 trust
>>>
>>>>
>>>
>>>> Look here the IP only connect to localhost. From where Are your
>>>
>>>> running
>>>
>>>>
>>>
>>>> the script?
>>>
>>>>
>>>
>>>>> #allo replication connections from localhost, by a user with the
>>>
>>>>
>>>
>>>>> replication privilege
>>>
>>>>
>>>
>>>>> local replication all trust
>>>
>>>>
>>>
>>>>> host replication all 127..0.1/32 trust
>>>
>>>>
>>>
>>>>> host replication all ::1/128 trust
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> the problem is I'm not sure I need to reconfigure pg_hba.conf
>>> with
>>>
>>>>
>>>
>>>>> database with user postgres or not?
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> When I'm connecting into the each database and the "show
>>>
>>>> pg_hba.conf"
>>>
>>>>
>>>
>>>>> show nothing.
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> postgres-# show pg_hba.conf
>>>
>>>>
>>>
>>>>> postgres-#
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>>>
>>>>
>>>
>>>>> <shreeyansh2014@gmail.com> wrote:
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> Hi Pepe,
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> It seems your are using os user for taking the backup.
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> When you run command line commands against the postgres database
>>> and
>>>
>>>>
>>>
>>>>> they ask for the user and password that is the database user
>>>
>>>> postgres
>>>
>>>>
>>>
>>>>> and its associated password, so when you do something like: psql
>>> -d
>>>
>>>>
>>>
>>>>> template1 -U postgres the password you will be prompted for is
>>>
>>>>
>>>
>>>>> your_db_user password
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> Now the above also depends on what is set in pg_hba.conf for the
>>>
>>>>
>>>
>>>>> various combinations of host, database, user and auth_method.
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> For more information see
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> Thanks & Regards,
>>>
>>>>
>>>
>>>>> SHREEYANSH DBA TEAM
>>>
>>>>
>>>
>>>>> www.shreeyansh.com [2] [1]
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
>>>
>>>> wrote:
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>>> good morning Expert DBAs,
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> I created a script to do backup and I have faced the error of
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>>> Performing globals backup:
>>>
>>>>
>>>
>>>>>>> pg_dumpall: could not connect to database "template1":FATAL:
>>> Ident
>>>
>>>>
>>>
>>>>>>> authentication failed for user "postgres" fro globals backup.
>>> As
>>>
>>>>
>>>
>>>>>>> same as performing schema-only backups and full 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 but
>>>
>>>>
>>>
>>>>>> couldn't run from script even the script declared
>>>
>>>>
>>>
>>>>>> BACKUP_USER=postgres
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>>>
>>>>
>>>
>>>>>> backup script working fine
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # VI PG_BACKUP.CONFIG
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ##############################
>>>
>>>>
>>>
>>>>>> ## POSTGRESQL BACKUP CONFIG ##
>>>
>>>>
>>>
>>>>>> ##############################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Optional system user to run backups as. If the user the
>>> script
>>>
>>>> is
>>>
>>>>
>>>
>>>>>> running as doesn't match this
>>>
>>>>
>>>
>>>>>> # the script terminates. Leave blank to skip check.
>>>
>>>>
>>>
>>>>>> BACKUP_USER=
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Optional hostname to adhere to pg_hba policies. Will default
>>> to
>>>
>>>>
>>>
>>>>>> "localhost" if none specified.
>>>
>>>>
>>>
>>>>>> HOSTNAME="hostname"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Optional username to connect to database as. Will default to
>>>
>>>>
>>>
>>>>>> "postgres" if none specified.
>>>
>>>>
>>>
>>>>>> USERNAME="postgres"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # This dir will be created if it doesn't exist. This must be
>>>
>>>>
>>>
>>>>>> writable by the user the script is
>>>
>>>>
>>>
>>>>>> # running as.
>>>
>>>>
>>>
>>>>>> BACKUP_DIR=/home/backups/database/postgresql/
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # List of strings to match against in database name, separated
>>> by
>>>
>>>>
>>>
>>>>>> space or comma, for which we only
>>>
>>>>
>>>
>>>>>> # wish to keep a backup of the schema, not the data. Any
>>> database
>>>
>>>>
>>>
>>>>>> names which contain any of these
>>>
>>>>
>>>
>>>>>> # values will be considered candidates. (e.g. "system_log" will
>>>
>>>>
>>>
>>>>>> match "dev_system_log_2010-01")
>>>
>>>>
>>>
>>>>>> SCHEMA_ONLY_LIST=""
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Will produce a custom-format backup if set to "yes"
>>>
>>>>
>>>
>>>>>> ENABLE_CUSTOM_BACKUPS=yes
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Will produce a gzipped plain-format backup if set to "yes"
>>>
>>>>
>>>
>>>>>> ENABLE_PLAIN_BACKUPS=yes
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Will produce gzipped sql file containing the cluster globals,
>>>
>>>> like
>>>
>>>>
>>>
>>>>>> users and passwords, if set to "yes"
>>>
>>>>
>>>
>>>>>> ENABLE_GLOBALS_BACKUPS=yes
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> #### SETTINGS FOR ROTATED BACKUPS ####
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>>>
>>>>
>>>
>>>>>> DAY_OF_WEEK_TO_KEEP=5
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Number of days to keep daily backups
>>>
>>>>
>>>
>>>>>> DAYS_TO_KEEP=7
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # How many weeks to keep weekly backups
>>>
>>>>
>>>
>>>>>> WEEKS_TO_KEEP=5
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ######################################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> #VI PG_BACKUP.SH
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> #!/bin/bash
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> ####### LOAD CONFIG #######
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> while [ $# -gt 0 ]; do
>>>
>>>>
>>>
>>>>>> case $1 in
>>>
>>>>
>>>
>>>>>> -c)
>>>
>>>>
>>>
>>>>>> if [ -r "$2" ]; then
>>>
>>>>
>>>
>>>>>> source "$2"
>>>
>>>>
>>>
>>>>>> shift 2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> ${ECHO} "Unreadable config file
>>>
>>>>
>>>
>>>>>> \"$2\"" 1>&2
>>>
>>>>
>>>
>>>>>> exit 1
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> ;;
>>>
>>>>
>>>
>>>>>> *)
>>>
>>>>
>>>
>>>>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>>>
>>>>
>>>
>>>>>> exit 2
>>>
>>>>
>>>
>>>>>> ;;
>>>
>>>>
>>>
>>>>>> esac
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ $# = 0 ]; then
>>>
>>>>
>>>
>>>>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>>>
>>>>
>>>
>>>>>> source $SCRIPTPATH/pg_backup.config
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> #### PRE-BACKUP CHECKS ####
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Make sure we're running as the required backup user
>>>
>>>>
>>>
>>>>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ];
>>> then
>>>
>>>>
>>>
>>>>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>>>
>>>>
>>>
>>>>>> exit 1;
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> ### INITIALISE DEFAULTS ###
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ ! $HOSTNAME ]; then
>>>
>>>>
>>>
>>>>>> HOSTNAME="localhost"
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ ! $USERNAME ]; then
>>>
>>>>
>>>
>>>>>> USERNAME="postgres"
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> #### START THE BACKUPS ####
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>>>
>>>>
>>>
>>>>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>>>
>>>>
>>>
>>>>>> and fix it!" 1>&2
>>>
>>>>
>>>
>>>>>> exit 1;
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> #######################
>>>
>>>>
>>>
>>>>>> ### GLOBALS BACKUPS ###
>>>
>>>>
>>>
>>>>>> #######################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "\n\nPerforming globals backup"
>>>
>>>>
>>>
>>>>>> echo -e "--------------------------------------------\n"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>>>
>>>>
>>>
>>>>>> then
>>>
>>>>
>>>
>>>>>> echo "Globals backup"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>>>
>>>>
>>>
>>>>>> echo "[!!ERROR!!] Failed to produce globals backup"
>>>
>>>>
>>>
>>>>>> 1>&2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"globals".sql.gz
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> echo "None"
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> ### SCHEMA-ONLY BACKUPS ###
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>>>
>>>>
>>>
>>>>>> do
>>>
>>>>
>>>
>>>>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>>>
>>>>
>>>
>>>>>> '$SCHEMA_ONLY_DB'"
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>>>
>>>>
>>>
>>>>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "\n\nPerforming schema-only backups"
>>>
>>>>
>>>
>>>>>> echo -e "--------------------------------------------\n"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>>>
>>>>
>>>
>>>>>> "$SCHEMA_ONLY_QUERY" postgres`
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "The following databases were matched for schema-only
>>>
>>>>
>>>
>>>>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>>>
>>>>
>>>
>>>>>> do
>>>
>>>>
>>>
>>>>>> echo "Schema-only backup of $DATABASE"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>>>
>>>>
>>>
>>>>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress;
>>> then
>>>
>>>>
>>>
>>>>>> echo "[!!ERROR!!] Failed to backup database schema of
>>>
>>>>
>>>
>>>>>> $DATABASE" 1>&2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> ###### FULL BACKUPS #######
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>>>
>>>>
>>>
>>>>>> do
>>>
>>>>
>>>
>>>>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>>>
>>>>
>>>
>>>>>> datname !~ '$SCHEMA_ONLY_DB'"
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>>>
>>>>
>>>
>>>>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order
>>> by
>>>
>>>>
>>>
>>>>>> datname;"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "\n\nPerforming full backups"
>>>
>>>>
>>>
>>>>>> echo -e "--------------------------------------------\n"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>>>
>>>>
>>>
>>>>>> "$FULL_BACKUP_QUERY" postgres`
>>>
>>>>
>>>
>>>>>> do
>>>
>>>>
>>>
>>>>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>>>
>>>>
>>>
>>>>>> then
>>>
>>>>
>>>
>>>>>> echo "Plain backup of $DATABASE"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>>>
>>>>
>>>
>>>>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>>>
>>>>
>>>
>>>>>> echo "[!!ERROR!!] Failed to produce plain backup
>>>
>>>>
>>>
>>>>>> database $DATABASE" 1>&2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>>>
>>>>
>>>
>>>>>> then
>>>
>>>>
>>>
>>>>>> echo "Custom backup of $DATABASE"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>>>
>>>>
>>>
>>>>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>>>
>>>>
>>>
>>>>>> echo "[!!ERROR!!] Failed to produce custom backup
>>>
>>>>
>>>
>>>>>> database $DATABASE" 1>&2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "\nAll database backups complete!"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> I'm appreciate if anyone know how to correct this?
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> thank you.
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> 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
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> Links:
>>>
>>>>
>>>
>>>>> ------
>>>
>>>>
>>>
>>>>> [1] http://www.shreeyansh.com/
>>
>>
>>
>> Links:
>> ------
>> [1] http://127.0.0.1/32
>> [2] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-26 16:00 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
1 sibling, 1 reply; 24+ messages in thread
From: Shreeyansh Dba @ 2019-02-26 16:00 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Ohh, It looks your pg_hba entries are correct, reset your database user
"postgres" password then try again or use -w option, use a single hba.conf
file.
try: pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postresp.sql
Thanks & Regards,
*Shreeyansh DBA Team*
www.shreeyansh.com
On Tue, Feb 26, 2019 at 9:06 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
> yes mam'm/sir. I already posted it
>
> here it is again.
>
> #vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
>
> #TYPE DATABASE USER ADDRESS METHOD
> # "local" is for Unix domain socket connectiosn only
>
> local all all trust
>
> # IPv4 local connections:
>
> host all all 127.0.0.1/32 trust
>
> # IPv6 local connections:
>
> host all all ::1/128 trust
>
> # allow all replication connections from localhost, by a user with the
> replication privilege
> local replication all trust
> host replication all 127.0.0.1/32 trust
> host replication all ::1/128 trust
>
>
> I also found pg_hba.conf on both folders
> /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I
> modified it as above and the script is not working even run from the
> command prompt.
>
> #vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf &
> /var/lib/pgsql/data/pg_hba.conf)
>
> #TYPE DATABASE USER ADDRESS METHOD
> # "local" is for Unix domain socket connectiosn only
>
> local all all trust
>
> # IPv4 local connections:
>
> host all all 127.0.0.1/32 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 trust
>
> # allow all replication connections from localhost, by a user with the
> replication privilege
> local replication all trust
> host replication all 127.0.0.1/32 rust
> host replication all ::1/128 trust
>
>
> why do I have 3 pg_hba.conf? which one should use?
>
> thank you for looking into it.
>
> 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
>
>
> On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba <
> shreeyansh2014@gmail.com> wrote:
>
>
> The error message says the authentication method used isn't trust. Can you
> please share your pg_hba.conf file entries.
>
> Thanks & Regards,
> *Shreeyansh DBA Team*
> www.shr Hi Pepe eeyansh.com <http://www.shreeyansh.com/;
>
>
> On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
>
> No sir. I have tried what your suggestion and still failed.
>
> as root:
>
> # export HOSTNAME="localhost"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
> # export HOSTNAME="127.0.0.1"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
>
> as same as postgres:
>
> #su - postgres
>
> export HOSTNAME="localhost"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
> # export HOSTNAME="127.0.0.1"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
>
> as the postgres, I can run pgdump dbname > output.sql
>
> 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
>
>
> On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <
> gilberto.castillo@etecsa.cu> wrote:
>
>
> El 2019-02-25 14:16, Pepe TD Vo escribió:
> > I am running script in local host (same db server)
>
> El 2019-02-25 14:16, Pepe TD Vo escribió:
> > I am running script in local host (same db server)
>
>
> Please, Check this:
>
> root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
> USERNAME="postgres"; DATABASE="postgres"
>
> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
> Password:
> pg_dump: [archiver (db)] connection to database "postgres" failed:
> FATAL: password authentication failed for user "postgres"
> FATAL: password authentication failed for user "postgres"
>
>
> Other:
>
> root@gilbertoc:/home/gilbertoc# sudo su - postgres
>
> postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
> DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/postresp.sql
> /tmp/postresp.sql: Permiso denegado
>
>
> Fine:
>
> postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
> DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/salvapostgres.backup
> postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
> /tmp/salvapostgres.backup
>
>
> >
> > 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> > <gilberto.castillo@etecsa.cu> wrote:
> >
> > El 2019-02-25 13:48, Pepe TD Vo escribió:
> >
> >> Thank you for your information.
> >
> >> I saw this document this morning and I did check my pg_hba.conf and
> >
> >> for local host and tried to connect to the template1/0 and/or other
> >
> >> database with postgres fine without prompting me for the password
> >
> >>
> >
> >> #psql -d template0 -U postgres
> >
> >> template0-#
> >
> >> #psql -d template1 -U postgres
> >
> >> template1-#
> >
> >>
> >
> >> #psql -d CIDR -U postgres
> >
> >> CIDR-#
> >
> >> #psql -d postgres -U postgres
> >
> >> postgres-#
> >
> >>
> >
> >> and a pg_hba.conf:
> >
> >>
> >
> >> "
> >
> >>
> >
> >> #TYPE DATABASE USER ADDRESS METHOD
> >
> >> local all all trust
> >
> >> host all all 127.0.0.1/32 trust
> >
> >> host all all ::1/128 trust
> >
> > Look here the IP only connect to localhost. From where Are your
> > running
> >
> > the script?
> >
> >> #allo replication connections from localhost, by a user with the
> >
> >> replication privilege
> >
> >> local replication all trust
> >
> >> host replication all 127..0.1/32 trust
> >
> >> host replication all ::1/128 trust
> >
> >>
> >
> >> the problem is I'm not sure I need to reconfigure pg_hba.conf with
> >
> >> database with user postgres or not?
> >
> >>
> >
> >> When I'm connecting into the each database and the "show
> > pg_hba.conf"
> >
> >> show nothing.
> >
> >>
> >
> >> postgres-# show pg_hba.conf
> >
> >> postgres-#
> >
> >>
> >
> >> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
> >
> >> <shreeyansh2014@gmail.com> wrote:
> >
> >>
> >
> >> Hi Pepe,
> >
> >>
> >
> >> It seems your are using os user for taking the backup.
> >
> >>
> >
> >> When you run command line commands against the postgres database and
> >
> >> they ask for the user and password that is the database user
> > postgres
> >
> >> and its associated password, so when you do something like: psql -d
> >
> >> template1 -U postgres the password you will be prompted for is
> >
> >> your_db_user password
> >
> >>
> >
> >> Now the above also depends on what is set in pg_hba.conf for the
> >
> >> various combinations of host, database, user and auth_method.
> >
> >>
> >
> >> For more information see
> >
> >>
> > https://www.postgresql.org/docs/9.5/static/client-authentication.html
> >
> >>
> >
> >> Thanks & Regards,
> >
> >> SHREEYANSH DBA TEAM
> >
> >> www.shreeyansh.com [1]
> >
> >>
> >
> >> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> > wrote:
> >
> >>
> >
> >>> good morning Expert DBAs,
> >
> >>>
> >
> >>> I created a script to do backup and I have faced the error of
> >
> >>>
> >
> >>>> Performing globals backup:
> >
> >>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
> >
> >>>> authentication failed for user "postgres" fro globals backup. As
> >
> >>>> same as performing schema-only backups and full 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 but
> >
> >>> couldn't run from script even the script declared
> >
> >>> BACKUP_USER=postgres
> >
> >>>
> >
> >>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
> >
> >>> backup script working fine
> >
> >>>
> >
> >>> # VI PG_BACKUP.CONFIG
> >
> >>>
> >
> >>> ##############################
> >
> >>> ## POSTGRESQL BACKUP CONFIG ##
> >
> >>> ##############################
> >
> >>>
> >
> >>> # Optional system user to run backups as. If the user the script
> > is
> >
> >>> running as doesn't match this
> >
> >>> # the script terminates. Leave blank to skip check.
> >
> >>> BACKUP_USER=
> >
> >>>
> >
> >>> # Optional hostname to adhere to pg_hba policies. Will default to
> >
> >>> "localhost" if none specified.
> >
> >>> HOSTNAME="hostname"
> >
> >>>
> >
> >>> # Optional username to connect to database as. Will default to
> >
> >>> "postgres" if none specified.
> >
> >>> USERNAME="postgres"
> >
> >>>
> >
> >>> # This dir will be created if it doesn't exist. This must be
> >
> >>> writable by the user the script is
> >
> >>> # running as.
> >
> >>> BACKUP_DIR=/home/backups/database/postgresql/
> >
> >>>
> >
> >>> # List of strings to match against in database name, separated by
> >
> >>> space or comma, for which we only
> >
> >>> # wish to keep a backup of the schema, not the data. Any database
> >
> >>> names which contain any of these
> >
> >>> # values will be considered candidates. (e.g. "system_log" will
> >
> >>> match "dev_system_log_2010-01")
> >
> >>> SCHEMA_ONLY_LIST=""
> >
> >>>
> >
> >>> # Will produce a custom-format backup if set to "yes"
> >
> >>> ENABLE_CUSTOM_BACKUPS=yes
> >
> >>>
> >
> >>> # Will produce a gzipped plain-format backup if set to "yes"
> >
> >>> ENABLE_PLAIN_BACKUPS=yes
> >
> >>>
> >
> >>> # Will produce gzipped sql file containing the cluster globals,
> > like
> >
> >>> users and passwords, if set to "yes"
> >
> >>> ENABLE_GLOBALS_BACKUPS=yes
> >
> >>>
> >
> >>> #### SETTINGS FOR ROTATED BACKUPS ####
> >
> >>>
> >
> >>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
> >
> >>> DAY_OF_WEEK_TO_KEEP=5
> >
> >>>
> >
> >>> # Number of days to keep daily backups
> >
> >>> DAYS_TO_KEEP=7
> >
> >>>
> >
> >>> # How many weeks to keep weekly backups
> >
> >>> WEEKS_TO_KEEP=5
> >
> >>>
> >
> >>> ######################################
> >
> >>>
> >
> >>> #VI PG_BACKUP.SH
> >
> >>>
> >
> >>> #!/bin/bash
> >
> >>>
> >
> >>> ###########################
> >
> >>> ####### LOAD CONFIG #######
> >
> >>> ###########################
> >
> >>>
> >
> >>> while [ $# -gt 0 ]; do
> >
> >>> case $1 in
> >
> >>> -c)
> >
> >>> if [ -r "$2" ]; then
> >
> >>> source "$2"
> >
> >>> shift 2
> >
> >>> else
> >
> >>> ${ECHO} "Unreadable config file
> >
> >>> \"$2\"" 1>&2
> >
> >>> exit 1
> >
> >>> fi
> >
> >>> ;;
> >
> >>> *)
> >
> >>> ${ECHO} "Unknown Option \"$1\"" 1>&2
> >
> >>> exit 2
> >
> >>> ;;
> >
> >>> esac
> >
> >>> done
> >
> >>>
> >
> >>> if [ $# = 0 ]; then
> >
> >>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
> >
> >>> source $SCRIPTPATH/pg_backup.config
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> #### PRE-BACKUP CHECKS ####
> >
> >>> ###########################
> >
> >>>
> >
> >>> # Make sure we're running as the required backup user
> >
> >>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
> >
> >>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
> >
> >>> exit 1;
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> ### INITIALISE DEFAULTS ###
> >
> >>> ###########################
> >
> >>>
> >
> >>> if [ ! $HOSTNAME ]; then
> >
> >>> HOSTNAME="localhost"
> >
> >>> fi;
> >
> >>>
> >
> >>> if [ ! $USERNAME ]; then
> >
> >>> USERNAME="postgres"
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> #### START THE BACKUPS ####
> >
> >>> ###########################
> >
> >>>
> >
> >>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
> >
> >>>
> >
> >>> echo "Making backup directory in $FINAL_BACKUP_DIR"
> >
> >>>
> >
> >>> if ! mkdir -p $FINAL_BACKUP_DIR; then
> >
> >>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
> >
> >>> and fix it!" 1>&2
> >
> >>> exit 1;
> >
> >>> fi;
> >
> >>>
> >
> >>> #######################
> >
> >>> ### GLOBALS BACKUPS ###
> >
> >>> #######################
> >
> >>>
> >
> >>> echo -e "\n\nPerforming globals backup"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Globals backup"
> >
> >>>
> >
> >>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
> >
> >>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce globals backup"
> >
> >>> 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"globals".sql.gz
> >
> >>> fi
> >
> >>> else
> >
> >>> echo "None"
> >
> >>> fi
> >
> >>>
> >
> >>> ###########################
> >
> >>> ### SCHEMA-ONLY BACKUPS ###
> >
> >>> ###########################
> >
> >>>
> >
> >>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> >
> >>> do
> >
> >>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
> >
> >>> '$SCHEMA_ONLY_DB'"
> >
> >>> done
> >
> >>>
> >
> >>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
> >
> >>> $SCHEMA_ONLY_CLAUSE order by datname;"
> >
> >>>
> >
> >>> echo -e "\n\nPerforming schema-only backups"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> >
> >>> "$SCHEMA_ONLY_QUERY" postgres`
> >
> >>>
> >
> >>> echo -e "The following databases were matched for schema-only
> >
> >>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
> >
> >>>
> >
> >>> for DATABASE in $SCHEMA_ONLY_DB_LIST
> >
> >>> do
> >
> >>> echo "Schema-only backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> >
> >>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to backup database schema of
> >
> >>> $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
> >
> >>> fi
> >
> >>> done
> >
> >>>
> >
> >>> ###########################
> >
> >>> ###### FULL BACKUPS #######
> >
> >>> ###########################
> >
> >>>
> >
> >>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> >
> >>> do
> >
> >>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
> >
> >>> datname !~ '$SCHEMA_ONLY_DB'"
> >
> >>> done
> >
> >>>
> >
> >>> FULL_BACKUP_QUERY="select datname from pg_database where not
> >
> >>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
> >
> >>> datname;"
> >
> >>>
> >
> >>> echo -e "\n\nPerforming full backups"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> >
> >>> "$FULL_BACKUP_QUERY" postgres`
> >
> >>> do
> >
> >>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Plain backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> >
> >>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce plain backup
> >
> >>> database $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
> >
> >>> fi
> >
> >>> fi
> >
> >>>
> >
> >>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Custom backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
> >
> >>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce custom backup
> >
> >>> database $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE".custom
> >
> >>> fi
> >
> >>> fi
> >
> >>>
> >
> >>> done
> >
> >>>
> >
> >>> echo -e "\nAll database backups complete!"
> >
> >>>
> >
> >>> I'm appreciate if anyone know how to correct this?
> >
> >>>
> >
> >>> thank you.
> >
> >>>
> >
> >>> 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
> >
> >>
> >
> >>
> >
> >>
> >
> >> Links:
> >
> >> ------
> >
> >> [1] http://www.shreeyansh.com/
>
>
>
>
>
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
@ 2019-02-26 17:46 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 18:29 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
2019-02-26 18:59 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-27 06:14 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
0 siblings, 3 replies; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-26 17:46 UTC (permalink / raw)
To: Shreeyansh Dba <shreeyansh2014@gmail.com>; +Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
same error:
run as root:# export HOSTNAME=hostname# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
pg_dump:[archiver (db)]connection to database "DATABASE" failed: could not connect to server: Connection refusedIs the server running on host "portal-p" (138.24.1.110) and acceptiong TCP/IP connection on port 5432?
run as postgres# export HOSTNAME=hostname# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
pg_dump:[archiver (db)]connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
portal-p already on /etc/hosts.
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
On Tuesday, February 26, 2019 11:01 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
Ohh, It looks your pg_hba entries are correct, reset your database user "postgres" password then try again or use -w option, use a single hba.conf file.
try: pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postresp.sql
Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com
On Tue, Feb 26, 2019 at 9:06 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
yes mam'm/sir. I already posted it
here it is again.
#vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 trusthost replication all ::1/128 trust
I also found pg_hba.conf on both folders /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the script is not working even run from the command prompt.
#vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
host all power_user 0.0.0.0/0 md5host all other_user 0.0.0.0/0 md5host all storageLoader 0.0.0.0/0 md5
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 rusthost replication all ::1/128 trust
why do I have 3 pg_hba.conf? which one should use?
thank you for looking into it.
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
On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
The error message says the authentication method used isn't trust. Can you please share your pg_hba.conf file entries.
Thanks & Regards,
Shreeyansh DBA Team
www.shr Hi Pepe eeyansh.com
On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
No sir. I have tried what your suggestion and still failed.
as root:
# export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as same as postgres:
#su - postgres
export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as the postgres, I can run pgdump dbname > output.sql
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
On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <gilberto.castillo@etecsa.cu> wrote:
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
Please, Check this:
root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
USERNAME="postgres"; DATABASE="postgres"
root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
"$USERNAME" "$DATABASE" > /tmp/postresp.sql
Password:
pg_dump: [archiver (db)] connection to database "postgres" failed:
FATAL: password authentication failed for user "postgres"
FATAL: password authentication failed for user "postgres"
Other:
root@gilbertoc:/home/gilbertoc# sudo su - postgres
postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/postresp.sql
/tmp/postresp.sql: Permiso denegado
Fine:
postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/salvapostgres.backup
postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
/tmp/salvapostgres.backup
>
> 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> <gilberto.castillo@etecsa.cu> wrote:
>
> El 2019-02-25 13:48, Pepe TD Vo escribió:
>
>> Thank you for your information.
>
>> I saw this document this morning and I did check my pg_hba.conf and
>
>> for local host and tried to connect to the template1/0 and/or other
>
>> database with postgres fine without prompting me for the password
>
>>
>
>> #psql -d template0 -U postgres
>
>> template0-#
>
>> #psql -d template1 -U postgres
>
>> template1-#
>
>>
>
>> #psql -d CIDR -U postgres
>
>> CIDR-#
>
>> #psql -d postgres -U postgres
>
>> postgres-#
>
>>
>
>> and a pg_hba.conf:
>
>>
>
>> "
>
>>
>
>> #TYPE DATABASE USER ADDRESS METHOD
>
>> local all all trust
>
>> host all all 127.0.0.1/32 trust
>
>> host all all ::1/128 trust
>
> Look here the IP only connect to localhost. From where Are your
> running
>
> the script?
>
>> #allo replication connections from localhost, by a user with the
>
>> replication privilege
>
>> local replication all trust
>
>> host replication all 127..0.1/32 trust
>
>> host replication all ::1/128 trust
>
>>
>
>> the problem is I'm not sure I need to reconfigure pg_hba.conf with
>
>> database with user postgres or not?
>
>>
>
>> When I'm connecting into the each database and the "show
> pg_hba.conf"
>
>> show nothing.
>
>>
>
>> postgres-# show pg_hba.conf
>
>> postgres-#
>
>>
>
>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>
>> <shreeyansh2014@gmail.com> wrote:
>
>>
>
>> Hi Pepe,
>
>>
>
>> It seems your are using os user for taking the backup.
>
>>
>
>> When you run command line commands against the postgres database and
>
>> they ask for the user and password that is the database user
> postgres
>
>> and its associated password, so when you do something like: psql -d
>
>> template1 -U postgres the password you will be prompted for is
>
>> your_db_user password
>
>>
>
>> Now the above also depends on what is set in pg_hba.conf for the
>
>> various combinations of host, database, user and auth_method.
>
>>
>
>> For more information see
>
>>
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>
>>
>
>> Thanks & Regards,
>
>> SHREEYANSH DBA TEAM
>
>> www.shreeyansh.com [1]
>
>>
>
>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> wrote:
>
>>
>
>>> good morning Expert DBAs,
>
>>>
>
>>> I created a script to do backup and I have faced the error of
>
>>>
>
>>>> Performing globals backup:
>
>>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
>
>>>> authentication failed for user "postgres" fro globals backup. As
>
>>>> same as performing schema-only backups and full 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 but
>
>>> couldn't run from script even the script declared
>
>>> BACKUP_USER=postgres
>
>>>
>
>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>
>>> backup script working fine
>
>>>
>
>>> # VI PG_BACKUP.CONFIG
>
>>>
>
>>> ##############################
>
>>> ## POSTGRESQL BACKUP CONFIG ##
>
>>> ##############################
>
>>>
>
>>> # Optional system user to run backups as. If the user the script
> is
>
>>> running as doesn't match this
>
>>> # the script terminates. Leave blank to skip check.
>
>>> BACKUP_USER=
>
>>>
>
>>> # Optional hostname to adhere to pg_hba policies. Will default to
>
>>> "localhost" if none specified.
>
>>> HOSTNAME="hostname"
>
>>>
>
>>> # Optional username to connect to database as. Will default to
>
>>> "postgres" if none specified.
>
>>> USERNAME="postgres"
>
>>>
>
>>> # This dir will be created if it doesn't exist. This must be
>
>>> writable by the user the script is
>
>>> # running as.
>
>>> BACKUP_DIR=/home/backups/database/postgresql/
>
>>>
>
>>> # List of strings to match against in database name, separated by
>
>>> space or comma, for which we only
>
>>> # wish to keep a backup of the schema, not the data. Any database
>
>>> names which contain any of these
>
>>> # values will be considered candidates. (e.g. "system_log" will
>
>>> match "dev_system_log_2010-01")
>
>>> SCHEMA_ONLY_LIST=""
>
>>>
>
>>> # Will produce a custom-format backup if set to "yes"
>
>>> ENABLE_CUSTOM_BACKUPS=yes
>
>>>
>
>>> # Will produce a gzipped plain-format backup if set to "yes"
>
>>> ENABLE_PLAIN_BACKUPS=yes
>
>>>
>
>>> # Will produce gzipped sql file containing the cluster globals,
> like
>
>>> users and passwords, if set to "yes"
>
>>> ENABLE_GLOBALS_BACKUPS=yes
>
>>>
>
>>> #### SETTINGS FOR ROTATED BACKUPS ####
>
>>>
>
>>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>
>>> DAY_OF_WEEK_TO_KEEP=5
>
>>>
>
>>> # Number of days to keep daily backups
>
>>> DAYS_TO_KEEP=7
>
>>>
>
>>> # How many weeks to keep weekly backups
>
>>> WEEKS_TO_KEEP=5
>
>>>
>
>>> ######################################
>
>>>
>
>>> #VI PG_BACKUP.SH
>
>>>
>
>>> #!/bin/bash
>
>>>
>
>>> ###########################
>
>>> ####### LOAD CONFIG #######
>
>>> ###########################
>
>>>
>
>>> while [ $# -gt 0 ]; do
>
>>> case $1 in
>
>>> -c)
>
>>> if [ -r "$2" ]; then
>
>>> source "$2"
>
>>> shift 2
>
>>> else
>
>>> ${ECHO} "Unreadable config file
>
>>> \"$2\"" 1>&2
>
>>> exit 1
>
>>> fi
>
>>> ;;
>
>>> *)
>
>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>
>>> exit 2
>
>>> ;;
>
>>> esac
>
>>> done
>
>>>
>
>>> if [ $# = 0 ]; then
>
>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>
>>> source $SCRIPTPATH/pg_backup.config
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### PRE-BACKUP CHECKS ####
>
>>> ###########################
>
>>>
>
>>> # Make sure we're running as the required backup user
>
>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
>
>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> ### INITIALISE DEFAULTS ###
>
>>> ###########################
>
>>>
>
>>> if [ ! $HOSTNAME ]; then
>
>>> HOSTNAME="localhost"
>
>>> fi;
>
>>>
>
>>> if [ ! $USERNAME ]; then
>
>>> USERNAME="postgres"
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### START THE BACKUPS ####
>
>>> ###########################
>
>>>
>
>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>
>>>
>
>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>
>>>
>
>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>
>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>
>>> and fix it!" 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> #######################
>
>>> ### GLOBALS BACKUPS ###
>
>>> #######################
>
>>>
>
>>> echo -e "\n\nPerforming globals backup"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Globals backup"
>
>>>
>
>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce globals backup"
>
>>> 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz
>
>>> fi
>
>>> else
>
>>> echo "None"
>
>>> fi
>
>>>
>
>>> ###########################
>
>>> ### SCHEMA-ONLY BACKUPS ###
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>
>>> '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>
>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>
>>>
>
>>> echo -e "\n\nPerforming schema-only backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$SCHEMA_ONLY_QUERY" postgres`
>
>>>
>
>>> echo -e "The following databases were matched for schema-only
>
>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>
>>>
>
>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>
>>> do
>
>>> echo "Schema-only backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to backup database schema of
>
>>> $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>
>>> fi
>
>>> done
>
>>>
>
>>> ###########################
>
>>> ###### FULL BACKUPS #######
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>
>>> datname !~ '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>
>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
>
>>> datname;"
>
>>>
>
>>> echo -e "\n\nPerforming full backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$FULL_BACKUP_QUERY" postgres`
>
>>> do
>
>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Plain backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce plain backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>
>>> fi
>
>>> fi
>
>>>
>
>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Custom backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>
>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce custom backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>
>>> fi
>
>>> fi
>
>>>
>
>>> done
>
>>>
>
>>> echo -e "\nAll database backups complete!"
>
>>>
>
>>> I'm appreciate if anyone know how to correct this?
>
>>>
>
>>> thank you.
>
>>>
>
>>> 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
>
>>
>
>>
>
>>
>
>> Links:
>
>> ------
>
>> [1] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-26 18:29 ` gilberto.castillo@etecsa.cu
2 siblings, 0 replies; 24+ messages in thread
From: gilberto.castillo@etecsa.cu @ 2019-02-26 18:29 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
El 2019-02-26 12:46, Pepe TD Vo escribió:
> same error:
>
> run as root:
Pepe look my example, You don't run the script like root.
>
> # export HOSTNAME=hostname
> # export USERNAME=postgres
> # export DATABASE=postgres
> # export PORT 5432
> # pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f
> /tmp/postgresbakup.sql
>
> pg_dump:[archiver (db)]connection to database "DATABASE" failed: could
> not connect to server: Connection refused
> Is the server running on host "portal-p" (138.24.1.110) and acceptiong
> TCP/IP connection on port 5432?
>
> run as postgres
> # export HOSTNAME=hostname
> # export USERNAME=postgres
> # export DATABASE=postgres
> # export PORT 5432
> # pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f
> /tmp/postgresbakup.sql
>
> pg_dump:[archiver (db)]connection to database "DATABASE" failed:
> FATAL: Ident authentication failed for user "postgres"
>
> portal-p already on /etc/hosts.
>
> 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
>
> On Tuesday, February 26, 2019 11:01 AM, Shreeyansh Dba
> <shreeyansh2014@gmail.com> wrote:
>
> Ohh, It looks your pg_hba entries are correct, reset your database
> user "postgres" password then try again or use -w option, use a single
> hba.conf file.
>
> try: pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f
> /tmp/postresp.sql
>
> Thanks & Regards,
> SHREEYANSH DBA TEAM
> www.shreeyansh.com [2]
>
> On Tue, Feb 26, 2019 at 9:06 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
>
>> yes mam'm/sir. I already posted it
>>
>> here it is again.
>>
>> #vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
>>
>> #TYPE DATABASE USER ADDRESS METHOD
>> # "local" is for Unix domain socket connectiosn only
>>
>> local all all trust
>>
>> # IPv4 local connections:
>>
>> host all all 127.0.0.1/32 [1] trust
>>
>> # IPv6 local connections:
>>
>> host all all ::1/128 trust
>>
>> # allow all replication connections from localhost, by a user with
>> the replication privilege
>> local replication all trust
>> host replication all 127.0.0.1/32 [1] trust
>> host replication all ::1/128 trust
>>
>> I also found pg_hba.conf on both folders
>> /var/lib/pgsql/11/data/pg_hba.conf &
>> /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the
>> script is not working even run from the command prompt.
>>
>> #vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf &
>> /var/lib/pgsql/data/pg_hba.conf)
>>
>> #TYPE DATABASE USER ADDRESS METHOD
>> # "local" is for Unix domain socket connectiosn only
>>
>> local all all trust
>>
>> # IPv4 local connections:
>>
>> host all all 127.0.0.1/32 [1] trust
>>
>> host all power_user 0.0.0.0/0 [3] md5
>> host all other_user 0.0.0.0/0 [3] md5
>> host all storageLoader 0.0.0.0/0 [3] md5
>>
>> # IPv6 local connections:
>>
>> host all all ::1/128 trust
>>
>> # allow all replication connections from localhost, by a user with
>> the replication privilege
>> local replication all trust
>> host replication all 127.0.0.1/32 [1] rust
>> host replication all ::1/128 trust
>>
>> why do I have 3 pg_hba.conf? which one should use?
>>
>> thank you for looking into it.
>>
>> 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
>>
>> On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba
>> <shreeyansh2014@gmail.com> wrote:
>>
>> The error message says the authentication method used isn't trust.
>> Can you please share your pg_hba.conf file entries.
>>
>> Thanks & Regards,
>> SHREEYANSH DBA TEAM
>> www.shr Hi Pepe eeyansh.com [2]
>>
>> On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
>>
>>> No sir. I have tried what your suggestion and still failed.
>>>
>>> as root:
>>>
>>> # export HOSTNAME="localhost"
>>> # export USERNAME="postgres"
>>> # export DATABASE="postgres"
>>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>>> /tmp/postresp.sql
>>>
>>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>>> FATAL: Ident authentication failed for user "postgres"
>>>
>>> # export HOSTNAME="127.0.0.1"
>>> # export USERNAME="postgres"
>>> # export DATABASE="postgres"
>>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>>> /tmp/postresp.sql
>>>
>>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>>> FATAL: Ident authentication failed for user "postgres"
>>>
>>> as same as postgres:
>>>
>>> #su - postgres
>>>
>>> export HOSTNAME="localhost"
>>> # export USERNAME="postgres"
>>> # export DATABASE="postgres"
>>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>>> /tmp/postresp.sql
>>>
>>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>>> FATAL: Ident authentication failed for user "postgres"
>>>
>>> # export HOSTNAME="127.0.0.1"
>>> # export USERNAME="postgres"
>>> # export DATABASE="postgres"
>>> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" >
>>> /tmp/postresp.sql
>>>
>>> pg_dump:[archiver (db)] connection to database "DATABASE" failed:
>>> FATAL: Ident authentication failed for user "postgres"
>>>
>>> as the postgres, I can run pgdump dbname > output.sql
>>>
>>> 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
>>>
>>> On Monday, February 25, 2019 2:39 PM,
>>> "gilberto.castillo@etecsa.cu" <gilberto.castillo@etecsa.cu> wrote:
>>>
>>> El 2019-02-25 14:16, Pepe TD Vo escribió:
>>>
>>>> I am running script in local host (same db server)
>>>
>>> El 2019-02-25 14:16, Pepe TD Vo escribió:
>>>
>>>> I am running script in local host (same db server)
>>>
>>> Please, Check this:
>>>
>>> root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
>>>
>>> USERNAME="postgres"; DATABASE="postgres"
>>>
>>> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
>>>
>>> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>>>
>>> Password:
>>>
>>> pg_dump: [archiver (db)] connection to database "postgres" failed:
>>>
>>>
>>> FATAL: password authentication failed for user "postgres"
>>>
>>> FATAL: password authentication failed for user "postgres"
>>>
>>> Other:
>>>
>>> root@gilbertoc:/home/gilbertoc# sudo su - postgres
>>>
>>> postgres@gilbertoc:~$ export HOSTNAME="localhost";
>>> USERNAME="postgres";
>>>
>>> DATABASE="postgres"
>>>
>>> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
>>>
>>> "$DATABASE" > /tmp/postresp.sql
>>>
>>> /tmp/postresp.sql: Permiso denegado
>>>
>>> Fine:
>>>
>>> postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1";
>>> USERNAME="postgres";
>>>
>>> DATABASE="postgres"
>>>
>>> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
>>>
>>> "$DATABASE" > /tmp/salvapostgres.backup
>>>
>>> postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
>>>
>>> /tmp/salvapostgres.backup
>>>
>>>>
>>>
>>>> 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 Monday, February 25, 2019 1:58 PM,
>>> "gilberto.castillo@etecsa.cu"
>>>
>>>> <gilberto.castillo@etecsa.cu> wrote:
>>>
>>>>
>>>
>>>> El 2019-02-25 13:48, Pepe TD Vo escribió:
>>>
>>>>
>>>
>>>>> Thank you for your information.
>>>
>>>>
>>>
>>>>> I saw this document this morning and I did check my pg_hba.conf
>>> and
>>>
>>>>
>>>
>>>>> for local host and tried to connect to the template1/0 and/or
>>> other
>>>
>>>>
>>>
>>>>> database with postgres fine without prompting me for the
>>> password
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> #psql -d template0 -U postgres
>>>
>>>>
>>>
>>>>> template0-#
>>>
>>>>
>>>
>>>>> #psql -d template1 -U postgres
>>>
>>>>
>>>
>>>>> template1-#
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> #psql -d CIDR -U postgres
>>>
>>>>
>>>
>>>>> CIDR-#
>>>
>>>>
>>>
>>>>> #psql -d postgres -U postgres
>>>
>>>>
>>>
>>>>> postgres-#
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> and a pg_hba.conf:
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> "
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> #TYPE DATABASE USER ADDRESS METHOD
>>>
>>>>
>>>
>>>>> local all all
>>> trust
>>>
>>>>
>>>
>>>>> host all all 127.0.0.1/32 [1] trust
>>>
>>>>
>>>
>>>>> host all all ::1/128 trust
>>>
>>>>
>>>
>>>> Look here the IP only connect to localhost. From where Are your
>>>
>>>> running
>>>
>>>>
>>>
>>>> the script?
>>>
>>>>
>>>
>>>>> #allo replication connections from localhost, by a user with
>>> the
>>>
>>>>
>>>
>>>>> replication privilege
>>>
>>>>
>>>
>>>>> local replication all
>>> trust
>>>
>>>>
>>>
>>>>> host replication all 127..0.1/32 trust
>>>
>>>>
>>>
>>>>> host replication all ::1/128 trust
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> the problem is I'm not sure I need to reconfigure pg_hba.conf
>>> with
>>>
>>>>
>>>
>>>>> database with user postgres or not?
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> When I'm connecting into the each database and the "show
>>>
>>>> pg_hba.conf"
>>>
>>>>
>>>
>>>>> show nothing.
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> postgres-# show pg_hba.conf
>>>
>>>>
>>>
>>>>> postgres-#
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>>>
>>>>
>>>
>>>>> <shreeyansh2014@gmail.com> wrote:
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> Hi Pepe,
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> It seems your are using os user for taking the backup.
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> When you run command line commands against the postgres
>>> database and
>>>
>>>>
>>>
>>>>> they ask for the user and password that is the database user
>>>
>>>> postgres
>>>
>>>>
>>>
>>>>> and its associated password, so when you do something like:
>>> psql -d
>>>
>>>>
>>>
>>>>> template1 -U postgres the password you will be prompted for is
>>>
>>>>
>>>
>>>>> your_db_user password
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> Now the above also depends on what is set in pg_hba.conf for
>>> the
>>>
>>>>
>>>
>>>>> various combinations of host, database, user and auth_method.
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> For more information see
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> Thanks & Regards,
>>>
>>>>
>>>
>>>>> SHREEYANSH DBA TEAM
>>>
>>>>
>>>
>>>>> www.shreeyansh.com [2] [1]
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
>>>
>>>> wrote:
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>>> good morning Expert DBAs,
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> I created a script to do backup and I have faced the error of
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>>> Performing globals backup:
>>>
>>>>
>>>
>>>>>>> pg_dumpall: could not connect to database "template1":FATAL:
>>> Ident
>>>
>>>>
>>>
>>>>>>> authentication failed for user "postgres" fro globals backup.
>>> As
>>>
>>>>
>>>
>>>>>>> same as performing schema-only backups and full 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
>>> but
>>>
>>>>
>>>
>>>>>> couldn't run from script even the script declared
>>>
>>>>
>>>
>>>>>> BACKUP_USER=postgres
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and
>>> the
>>>
>>>>
>>>
>>>>>> backup script working fine
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # VI PG_BACKUP.CONFIG
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ##############################
>>>
>>>>
>>>
>>>>>> ## POSTGRESQL BACKUP CONFIG ##
>>>
>>>>
>>>
>>>>>> ##############################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Optional system user to run backups as. If the user the
>>> script
>>>
>>>> is
>>>
>>>>
>>>
>>>>>> running as doesn't match this
>>>
>>>>
>>>
>>>>>> # the script terminates. Leave blank to skip check.
>>>
>>>>
>>>
>>>>>> BACKUP_USER=
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Optional hostname to adhere to pg_hba policies. Will
>>> default to
>>>
>>>>
>>>
>>>>>> "localhost" if none specified.
>>>
>>>>
>>>
>>>>>> HOSTNAME="hostname"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Optional username to connect to database as. Will default
>>> to
>>>
>>>>
>>>
>>>>>> "postgres" if none specified.
>>>
>>>>
>>>
>>>>>> USERNAME="postgres"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # This dir will be created if it doesn't exist. This must be
>>>
>>>>
>>>
>>>>>> writable by the user the script is
>>>
>>>>
>>>
>>>>>> # running as.
>>>
>>>>
>>>
>>>>>> BACKUP_DIR=/home/backups/database/postgresql/
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # List of strings to match against in database name, separated
>>> by
>>>
>>>>
>>>
>>>>>> space or comma, for which we only
>>>
>>>>
>>>
>>>>>> # wish to keep a backup of the schema, not the data. Any
>>> database
>>>
>>>>
>>>
>>>>>> names which contain any of these
>>>
>>>>
>>>
>>>>>> # values will be considered candidates. (e.g. "system_log"
>>> will
>>>
>>>>
>>>
>>>>>> match "dev_system_log_2010-01")
>>>
>>>>
>>>
>>>>>> SCHEMA_ONLY_LIST=""
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Will produce a custom-format backup if set to "yes"
>>>
>>>>
>>>
>>>>>> ENABLE_CUSTOM_BACKUPS=yes
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Will produce a gzipped plain-format backup if set to "yes"
>>>
>>>>
>>>
>>>>>> ENABLE_PLAIN_BACKUPS=yes
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Will produce gzipped sql file containing the cluster
>>> globals,
>>>
>>>> like
>>>
>>>>
>>>
>>>>>> users and passwords, if set to "yes"
>>>
>>>>
>>>
>>>>>> ENABLE_GLOBALS_BACKUPS=yes
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> #### SETTINGS FOR ROTATED BACKUPS ####
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Which day to take the weekly backup from (1-7 =
>>> Monday-Sunday)
>>>
>>>>
>>>
>>>>>> DAY_OF_WEEK_TO_KEEP=5
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Number of days to keep daily backups
>>>
>>>>
>>>
>>>>>> DAYS_TO_KEEP=7
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # How many weeks to keep weekly backups
>>>
>>>>
>>>
>>>>>> WEEKS_TO_KEEP=5
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ######################################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> #VI PG_BACKUP.SH
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> #!/bin/bash
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> ####### LOAD CONFIG #######
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> while [ $# -gt 0 ]; do
>>>
>>>>
>>>
>>>>>> case $1 in
>>>
>>>>
>>>
>>>>>> -c)
>>>
>>>>
>>>
>>>>>> if [ -r "$2" ]; then
>>>
>>>>
>>>
>>>>>> source "$2"
>>>
>>>>
>>>
>>>>>> shift 2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> ${ECHO} "Unreadable config file
>>>
>>>>
>>>
>>>>>> \"$2\"" 1>&2
>>>
>>>>
>>>
>>>>>> exit 1
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> ;;
>>>
>>>>
>>>
>>>>>> *)
>>>
>>>>
>>>
>>>>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>>>
>>>>
>>>
>>>>>> exit 2
>>>
>>>>
>>>
>>>>>> ;;
>>>
>>>>
>>>
>>>>>> esac
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ $# = 0 ]; then
>>>
>>>>
>>>
>>>>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>>>
>>>>
>>>
>>>>>> source $SCRIPTPATH/pg_backup.config
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> #### PRE-BACKUP CHECKS ####
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> # Make sure we're running as the required backup user
>>>
>>>>
>>>
>>>>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ];
>>> then
>>>
>>>>
>>>
>>>>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>>>
>>>>
>>>
>>>>>> exit 1;
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> ### INITIALISE DEFAULTS ###
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ ! $HOSTNAME ]; then
>>>
>>>>
>>>
>>>>>> HOSTNAME="localhost"
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ ! $USERNAME ]; then
>>>
>>>>
>>>
>>>>>> USERNAME="postgres"
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> #### START THE BACKUPS ####
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>>>
>>>>
>>>
>>>>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>>>
>>>>
>>>
>>>>>> and fix it!" 1>&2
>>>
>>>>
>>>
>>>>>> exit 1;
>>>
>>>>
>>>
>>>>>> fi;
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> #######################
>>>
>>>>
>>>
>>>>>> ### GLOBALS BACKUPS ###
>>>
>>>>
>>>
>>>>>> #######################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "\n\nPerforming globals backup"
>>>
>>>>
>>>
>>>>>> echo -e "--------------------------------------------\n"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>>>
>>>>
>>>
>>>>>> then
>>>
>>>>
>>>
>>>>>> echo "Globals backup"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>>>
>>>>
>>>
>>>>>> echo "[!!ERROR!!] Failed to produce globals backup"
>>>
>>>>
>>>
>>>>>> 1>&2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"globals".sql.gz
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> echo "None"
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> ### SCHEMA-ONLY BACKUPS ###
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>>>
>>>>
>>>
>>>>>> do
>>>
>>>>
>>>
>>>>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>>>
>>>>
>>>
>>>>>> '$SCHEMA_ONLY_DB'"
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>>>
>>>>
>>>
>>>>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "\n\nPerforming schema-only backups"
>>>
>>>>
>>>
>>>>>> echo -e "--------------------------------------------\n"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>>>
>>>>
>>>
>>>>>> "$SCHEMA_ONLY_QUERY" postgres`
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "The following databases were matched for schema-only
>>>
>>>>
>>>
>>>>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>>>
>>>>
>>>
>>>>>> do
>>>
>>>>
>>>
>>>>>> echo "Schema-only backup of $DATABASE"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>>> |
>>>
>>>>
>>>
>>>>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress;
>>> then
>>>
>>>>
>>>
>>>>>> echo "[!!ERROR!!] Failed to backup database schema of
>>>
>>>>
>>>
>>>>>> $DATABASE" 1>&2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>> ###### FULL BACKUPS #######
>>>
>>>>
>>>
>>>>>> ###########################
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>>>
>>>>
>>>
>>>>>> do
>>>
>>>>
>>>
>>>>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>>>
>>>>
>>>
>>>>>> datname !~ '$SCHEMA_ONLY_DB'"
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>>>
>>>>
>>>
>>>>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE
>>> order by
>>>
>>>>
>>>
>>>>>> datname;"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "\n\nPerforming full backups"
>>>
>>>>
>>>
>>>>>> echo -e "--------------------------------------------\n"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>>>
>>>>
>>>
>>>>>> "$FULL_BACKUP_QUERY" postgres`
>>>
>>>>
>>>
>>>>>> do
>>>
>>>>
>>>
>>>>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>>>
>>>>
>>>
>>>>>> then
>>>
>>>>
>>>
>>>>>> echo "Plain backup of $DATABASE"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>>>
>>>>
>>>
>>>>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>>>
>>>>
>>>
>>>>>> echo "[!!ERROR!!] Failed to produce plain backup
>>>
>>>>
>>>
>>>>>> database $DATABASE" 1>&2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>>>
>>>>
>>>
>>>>>> then
>>>
>>>>
>>>
>>>>>> echo "Custom backup of $DATABASE"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>>>
>>>>
>>>
>>>>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>>>
>>>>
>>>
>>>>>> echo "[!!ERROR!!] Failed to produce custom backup
>>>
>>>>
>>>
>>>>>> database $DATABASE" 1>&2
>>>
>>>>
>>>
>>>>>> else
>>>
>>>>
>>>
>>>>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>>>
>>>>
>>>
>>>>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>> fi
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> done
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> echo -e "\nAll database backups complete!"
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> I'm appreciate if anyone know how to correct this?
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> thank you.
>>>
>>>>
>>>
>>>>>>
>>>
>>>>
>>>
>>>>>> 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
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>>
>>>
>>>>
>>>
>>>>> Links:
>>>
>>>>
>>>
>>>>> ------
>>>
>>>>
>>>
>>>>> [1] http://www.shreeyansh.com/
>
>
>
> Links:
> ------
> [1] http://127.0.0.1/32
> [2] http://www.shreeyansh.com/
> [3] http://0.0.0.0/0
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-26 18:59 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 20:52 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 20:55 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Steve Crawford <scrawford@pinpointresearch.com>
2019-02-26 21:27 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL David G. Johnston <david.g.johnston@gmail.com>
2 siblings, 3 replies; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-26 18:59 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; Shreeyansh Dba <shreeyansh2014@gmail.com>; +Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
I have tried to see the file read from pg_hba.conf and the config file within psql
#postgres=# select pg_read_file('pg_hba.conf');
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 trusthost replication all ::1/128 trust
I also found pg_hba.conf on both folders /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the script is not working even run from the command prompt.
#vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
host all power_user 0.0.0.0/0 md5host all other_user 0.0.0.0/0 md5host all storageLoader 0.0.0.0/0 md5
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 rusthost replication all ::1/128 trust
(1 row)
postgres=# select pg_conf_load_time() > modification from pg_stat_file('pg_hba.conf'):?column?----------f(1 row)
Can you tell me what "f" mean? force? load time should be by date?
how come, when I show pg_hba.conf from psql, it didn't give any row return? 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 Tuesday, February 26, 2019 12:47 PM, Pepe TD Vo <pepevo@yahoo.com> wrote:
same error:
run as root:# export HOSTNAME=hostname# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
pg_dump:[archiver (db)]connection to database "DATABASE" failed: could not connect to server: Connection refusedIs the server running on host "portal-p" (138.24.1.110) and acceptiong TCP/IP connection on port 5432?
run as postgres# export HOSTNAME=hostname# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
pg_dump:[archiver (db)]connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
portal-p already on /etc/hosts.
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
On Tuesday, February 26, 2019 11:01 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
Ohh, It looks your pg_hba entries are correct, reset your database user "postgres" password then try again or use -w option, use a single hba.conf file.
try: pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postresp.sql
Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com
On Tue, Feb 26, 2019 at 9:06 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
yes mam'm/sir. I already posted it
here it is again.
#vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 trusthost replication all ::1/128 trust
I also found pg_hba.conf on both folders /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the script is not working even run from the command prompt.
#vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
host all power_user 0.0.0.0/0 md5host all other_user 0.0.0.0/0 md5host all storageLoader 0.0.0.0/0 md5
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 rusthost replication all ::1/128 trust
why do I have 3 pg_hba.conf? which one should use?
thank you for looking into it.
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
On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
The error message says the authentication method used isn't trust. Can you please share your pg_hba.conf file entries.
Thanks & Regards,
Shreeyansh DBA Team
www.shr Hi Pepe eeyansh.com
On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
No sir. I have tried what your suggestion and still failed.
as root:
# export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as same as postgres:
#su - postgres
export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as the postgres, I can run pgdump dbname > output.sql
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
On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <gilberto.castillo@etecsa.cu> wrote:
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
Please, Check this:
root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
USERNAME="postgres"; DATABASE="postgres"
root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
"$USERNAME" "$DATABASE" > /tmp/postresp.sql
Password:
pg_dump: [archiver (db)] connection to database "postgres" failed:
FATAL: password authentication failed for user "postgres"
FATAL: password authentication failed for user "postgres"
Other:
root@gilbertoc:/home/gilbertoc# sudo su - postgres
postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/postresp.sql
/tmp/postresp.sql: Permiso denegado
Fine:
postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/salvapostgres.backup
postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
/tmp/salvapostgres.backup
>
> 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> <gilberto.castillo@etecsa.cu> wrote:
>
> El 2019-02-25 13:48, Pepe TD Vo escribió:
>
>> Thank you for your information.
>
>> I saw this document this morning and I did check my pg_hba.conf and
>
>> for local host and tried to connect to the template1/0 and/or other
>
>> database with postgres fine without prompting me for the password
>
>>
>
>> #psql -d template0 -U postgres
>
>> template0-#
>
>> #psql -d template1 -U postgres
>
>> template1-#
>
>>
>
>> #psql -d CIDR -U postgres
>
>> CIDR-#
>
>> #psql -d postgres -U postgres
>
>> postgres-#
>
>>
>
>> and a pg_hba.conf:
>
>>
>
>> "
>
>>
>
>> #TYPE DATABASE USER ADDRESS METHOD
>
>> local all all trust
>
>> host all all 127.0.0.1/32 trust
>
>> host all all ::1/128 trust
>
> Look here the IP only connect to localhost. From where Are your
> running
>
> the script?
>
>> #allo replication connections from localhost, by a user with the
>
>> replication privilege
>
>> local replication all trust
>
>> host replication all 127..0.1/32 trust
>
>> host replication all ::1/128 trust
>
>>
>
>> the problem is I'm not sure I need to reconfigure pg_hba.conf with
>
>> database with user postgres or not?
>
>>
>
>> When I'm connecting into the each database and the "show
> pg_hba.conf"
>
>> show nothing.
>
>>
>
>> postgres-# show pg_hba.conf
>
>> postgres-#
>
>>
>
>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>
>> <shreeyansh2014@gmail.com> wrote:
>
>>
>
>> Hi Pepe,
>
>>
>
>> It seems your are using os user for taking the backup.
>
>>
>
>> When you run command line commands against the postgres database and
>
>> they ask for the user and password that is the database user
> postgres
>
>> and its associated password, so when you do something like: psql -d
>
>> template1 -U postgres the password you will be prompted for is
>
>> your_db_user password
>
>>
>
>> Now the above also depends on what is set in pg_hba.conf for the
>
>> various combinations of host, database, user and auth_method.
>
>>
>
>> For more information see
>
>>
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>
>>
>
>> Thanks & Regards,
>
>> SHREEYANSH DBA TEAM
>
>> www.shreeyansh.com [1]
>
>>
>
>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> wrote:
>
>>
>
>>> good morning Expert DBAs,
>
>>>
>
>>> I created a script to do backup and I have faced the error of
>
>>>
>
>>>> Performing globals backup:
>
>>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
>
>>>> authentication failed for user "postgres" fro globals backup. As
>
>>>> same as performing schema-only backups and full 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 but
>
>>> couldn't run from script even the script declared
>
>>> BACKUP_USER=postgres
>
>>>
>
>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>
>>> backup script working fine
>
>>>
>
>>> # VI PG_BACKUP.CONFIG
>
>>>
>
>>> ##############################
>
>>> ## POSTGRESQL BACKUP CONFIG ##
>
>>> ##############################
>
>>>
>
>>> # Optional system user to run backups as. If the user the script
> is
>
>>> running as doesn't match this
>
>>> # the script terminates. Leave blank to skip check.
>
>>> BACKUP_USER=
>
>>>
>
>>> # Optional hostname to adhere to pg_hba policies. Will default to
>
>>> "localhost" if none specified.
>
>>> HOSTNAME="hostname"
>
>>>
>
>>> # Optional username to connect to database as. Will default to
>
>>> "postgres" if none specified.
>
>>> USERNAME="postgres"
>
>>>
>
>>> # This dir will be created if it doesn't exist. This must be
>
>>> writable by the user the script is
>
>>> # running as.
>
>>> BACKUP_DIR=/home/backups/database/postgresql/
>
>>>
>
>>> # List of strings to match against in database name, separated by
>
>>> space or comma, for which we only
>
>>> # wish to keep a backup of the schema, not the data. Any database
>
>>> names which contain any of these
>
>>> # values will be considered candidates. (e.g. "system_log" will
>
>>> match "dev_system_log_2010-01")
>
>>> SCHEMA_ONLY_LIST=""
>
>>>
>
>>> # Will produce a custom-format backup if set to "yes"
>
>>> ENABLE_CUSTOM_BACKUPS=yes
>
>>>
>
>>> # Will produce a gzipped plain-format backup if set to "yes"
>
>>> ENABLE_PLAIN_BACKUPS=yes
>
>>>
>
>>> # Will produce gzipped sql file containing the cluster globals,
> like
>
>>> users and passwords, if set to "yes"
>
>>> ENABLE_GLOBALS_BACKUPS=yes
>
>>>
>
>>> #### SETTINGS FOR ROTATED BACKUPS ####
>
>>>
>
>>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>
>>> DAY_OF_WEEK_TO_KEEP=5
>
>>>
>
>>> # Number of days to keep daily backups
>
>>> DAYS_TO_KEEP=7
>
>>>
>
>>> # How many weeks to keep weekly backups
>
>>> WEEKS_TO_KEEP=5
>
>>>
>
>>> ######################################
>
>>>
>
>>> #VI PG_BACKUP.SH
>
>>>
>
>>> #!/bin/bash
>
>>>
>
>>> ###########################
>
>>> ####### LOAD CONFIG #######
>
>>> ###########################
>
>>>
>
>>> while [ $# -gt 0 ]; do
>
>>> case $1 in
>
>>> -c)
>
>>> if [ -r "$2" ]; then
>
>>> source "$2"
>
>>> shift 2
>
>>> else
>
>>> ${ECHO} "Unreadable config file
>
>>> \"$2\"" 1>&2
>
>>> exit 1
>
>>> fi
>
>>> ;;
>
>>> *)
>
>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>
>>> exit 2
>
>>> ;;
>
>>> esac
>
>>> done
>
>>>
>
>>> if [ $# = 0 ]; then
>
>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>
>>> source $SCRIPTPATH/pg_backup.config
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### PRE-BACKUP CHECKS ####
>
>>> ###########################
>
>>>
>
>>> # Make sure we're running as the required backup user
>
>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
>
>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> ### INITIALISE DEFAULTS ###
>
>>> ###########################
>
>>>
>
>>> if [ ! $HOSTNAME ]; then
>
>>> HOSTNAME="localhost"
>
>>> fi;
>
>>>
>
>>> if [ ! $USERNAME ]; then
>
>>> USERNAME="postgres"
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### START THE BACKUPS ####
>
>>> ###########################
>
>>>
>
>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>
>>>
>
>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>
>>>
>
>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>
>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>
>>> and fix it!" 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> #######################
>
>>> ### GLOBALS BACKUPS ###
>
>>> #######################
>
>>>
>
>>> echo -e "\n\nPerforming globals backup"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Globals backup"
>
>>>
>
>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce globals backup"
>
>>> 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz
>
>>> fi
>
>>> else
>
>>> echo "None"
>
>>> fi
>
>>>
>
>>> ###########################
>
>>> ### SCHEMA-ONLY BACKUPS ###
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>
>>> '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>
>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>
>>>
>
>>> echo -e "\n\nPerforming schema-only backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$SCHEMA_ONLY_QUERY" postgres`
>
>>>
>
>>> echo -e "The following databases were matched for schema-only
>
>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>
>>>
>
>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>
>>> do
>
>>> echo "Schema-only backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to backup database schema of
>
>>> $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>
>>> fi
>
>>> done
>
>>>
>
>>> ###########################
>
>>> ###### FULL BACKUPS #######
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>
>>> datname !~ '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>
>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
>
>>> datname;"
>
>>>
>
>>> echo -e "\n\nPerforming full backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$FULL_BACKUP_QUERY" postgres`
>
>>> do
>
>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Plain backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce plain backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>
>>> fi
>
>>> fi
>
>>>
>
>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Custom backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>
>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce custom backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>
>>> fi
>
>>> fi
>
>>>
>
>>> done
>
>>>
>
>>> echo -e "\nAll database backups complete!"
>
>>>
>
>>> I'm appreciate if anyone know how to correct this?
>
>>>
>
>>> thank you.
>
>>>
>
>>> 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
>
>>
>
>>
>
>>
>
>> Links:
>
>> ------
>
>> [1] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 18:59 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-26 20:52 ` Pepe TD Vo <pepevo@yahoo.com>
2 siblings, 0 replies; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-26 20:52 UTC (permalink / raw)
To: Shreeyansh Dba <shreeyansh2014@gmail.com>; +Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
I have work around and I found a document to add "listen_addresses = '*' " on pg_indent.conf file to supports multiple client authentication methods.
after add that parameter in and I can run:
$ pg_dump -h localhost -U postgres -d postgres -f /tmp/postgres.sql $ ls /tmppostgres.sql
but still cannot using the variable
$ export HOST=localhost (or "localhost")$ echo $HOSTlocalhost$ export USERNAME="postgres"; DATABASE="postgres"$ echo USERNAMpostgres$ echo DATABASEposgres$ pg_dump -h "$HOST" -U "$USERNAME" -d "DATABASE" -f /tmp/postgres.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
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
On Tuesday, February 26, 2019 1:59 PM, Pepe TD Vo <pepevo@yahoo.com> wrote:
I have tried to see the file read from pg_hba.conf and the config file within psql
#postgres=# select pg_read_file('pg_hba.conf');
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 trusthost replication all ::1/128 trust
I also found pg_hba.conf on both folders /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the script is not working even run from the command prompt.
#vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
host all power_user 0.0.0.0/0 md5host all other_user 0.0.0.0/0 md5host all storageLoader 0.0.0.0/0 md5
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 rusthost replication all ::1/128 trust
(1 row)
postgres=# select pg_conf_load_time() > modification from pg_stat_file('pg_hba.conf'):?column?----------f(1 row)
Can you tell me what "f" mean? force? load time should be by date?
how come, when I show pg_hba.conf from psql, it didn't give any row return? 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 Tuesday, February 26, 2019 12:47 PM, Pepe TD Vo <pepevo@yahoo.com> wrote:
same error:
run as root:# export HOSTNAME=hostname# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
pg_dump:[archiver (db)]connection to database "DATABASE" failed: could not connect to server: Connection refusedIs the server running on host "portal-p" (138.24.1.110) and acceptiong TCP/IP connection on port 5432?
run as postgres# export HOSTNAME=hostname# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
pg_dump:[archiver (db)]connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
portal-p already on /etc/hosts.
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
On Tuesday, February 26, 2019 11:01 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
Ohh, It looks your pg_hba entries are correct, reset your database user "postgres" password then try again or use -w option, use a single hba.conf file.
try: pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postresp.sql
Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com
On Tue, Feb 26, 2019 at 9:06 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
yes mam'm/sir. I already posted it
here it is again.
#vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 trusthost replication all ::1/128 trust
I also found pg_hba.conf on both folders /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the script is not working even run from the command prompt.
#vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
host all power_user 0.0.0.0/0 md5host all other_user 0.0.0.0/0 md5host all storageLoader 0.0.0.0/0 md5
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 rusthost replication all ::1/128 trust
why do I have 3 pg_hba.conf? which one should use?
thank you for looking into it.
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
On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
The error message says the authentication method used isn't trust. Can you please share your pg_hba.conf file entries.
Thanks & Regards,
Shreeyansh DBA Team
www.shr Hi Pepe eeyansh.com
On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
No sir. I have tried what your suggestion and still failed.
as root:
# export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as same as postgres:
#su - postgres
export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as the postgres, I can run pgdump dbname > output.sql
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
On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <gilberto.castillo@etecsa.cu> wrote:
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
Please, Check this:
root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
USERNAME="postgres"; DATABASE="postgres"
root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
"$USERNAME" "$DATABASE" > /tmp/postresp.sql
Password:
pg_dump: [archiver (db)] connection to database "postgres" failed:
FATAL: password authentication failed for user "postgres"
FATAL: password authentication failed for user "postgres"
Other:
root@gilbertoc:/home/gilbertoc# sudo su - postgres
postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/postresp.sql
/tmp/postresp.sql: Permiso denegado
Fine:
postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/salvapostgres.backup
postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
/tmp/salvapostgres.backup
>
> 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> <gilberto.castillo@etecsa.cu> wrote:
>
> El 2019-02-25 13:48, Pepe TD Vo escribió:
>
>> Thank you for your information.
>
>> I saw this document this morning and I did check my pg_hba.conf and
>
>> for local host and tried to connect to the template1/0 and/or other
>
>> database with postgres fine without prompting me for the password
>
>>
>
>> #psql -d template0 -U postgres
>
>> template0-#
>
>> #psql -d template1 -U postgres
>
>> template1-#
>
>>
>
>> #psql -d CIDR -U postgres
>
>> CIDR-#
>
>> #psql -d postgres -U postgres
>
>> postgres-#
>
>>
>
>> and a pg_hba.conf:
>
>>
>
>> "
>
>>
>
>> #TYPE DATABASE USER ADDRESS METHOD
>
>> local all all trust
>
>> host all all 127.0.0.1/32 trust
>
>> host all all ::1/128 trust
>
> Look here the IP only connect to localhost. From where Are your
> running
>
> the script?
>
>> #allo replication connections from localhost, by a user with the
>
>> replication privilege
>
>> local replication all trust
>
>> host replication all 127..0.1/32 trust
>
>> host replication all ::1/128 trust
>
>>
>
>> the problem is I'm not sure I need to reconfigure pg_hba.conf with
>
>> database with user postgres or not?
>
>>
>
>> When I'm connecting into the each database and the "show
> pg_hba.conf"
>
>> show nothing.
>
>>
>
>> postgres-# show pg_hba.conf
>
>> postgres-#
>
>>
>
>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>
>> <shreeyansh2014@gmail.com> wrote:
>
>>
>
>> Hi Pepe,
>
>>
>
>> It seems your are using os user for taking the backup.
>
>>
>
>> When you run command line commands against the postgres database and
>
>> they ask for the user and password that is the database user
> postgres
>
>> and its associated password, so when you do something like: psql -d
>
>> template1 -U postgres the password you will be prompted for is
>
>> your_db_user password
>
>>
>
>> Now the above also depends on what is set in pg_hba.conf for the
>
>> various combinations of host, database, user and auth_method.
>
>>
>
>> For more information see
>
>>
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>
>>
>
>> Thanks & Regards,
>
>> SHREEYANSH DBA TEAM
>
>> www.shreeyansh.com [1]
>
>>
>
>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> wrote:
>
>>
>
>>> good morning Expert DBAs,
>
>>>
>
>>> I created a script to do backup and I have faced the error of
>
>>>
>
>>>> Performing globals backup:
>
>>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
>
>>>> authentication failed for user "postgres" fro globals backup. As
>
>>>> same as performing schema-only backups and full 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 but
>
>>> couldn't run from script even the script declared
>
>>> BACKUP_USER=postgres
>
>>>
>
>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>
>>> backup script working fine
>
>>>
>
>>> # VI PG_BACKUP.CONFIG
>
>>>
>
>>> ##############################
>
>>> ## POSTGRESQL BACKUP CONFIG ##
>
>>> ##############################
>
>>>
>
>>> # Optional system user to run backups as. If the user the script
> is
>
>>> running as doesn't match this
>
>>> # the script terminates. Leave blank to skip check.
>
>>> BACKUP_USER=
>
>>>
>
>>> # Optional hostname to adhere to pg_hba policies. Will default to
>
>>> "localhost" if none specified.
>
>>> HOSTNAME="hostname"
>
>>>
>
>>> # Optional username to connect to database as. Will default to
>
>>> "postgres" if none specified.
>
>>> USERNAME="postgres"
>
>>>
>
>>> # This dir will be created if it doesn't exist. This must be
>
>>> writable by the user the script is
>
>>> # running as.
>
>>> BACKUP_DIR=/home/backups/database/postgresql/
>
>>>
>
>>> # List of strings to match against in database name, separated by
>
>>> space or comma, for which we only
>
>>> # wish to keep a backup of the schema, not the data. Any database
>
>>> names which contain any of these
>
>>> # values will be considered candidates. (e.g. "system_log" will
>
>>> match "dev_system_log_2010-01")
>
>>> SCHEMA_ONLY_LIST=""
>
>>>
>
>>> # Will produce a custom-format backup if set to "yes"
>
>>> ENABLE_CUSTOM_BACKUPS=yes
>
>>>
>
>>> # Will produce a gzipped plain-format backup if set to "yes"
>
>>> ENABLE_PLAIN_BACKUPS=yes
>
>>>
>
>>> # Will produce gzipped sql file containing the cluster globals,
> like
>
>>> users and passwords, if set to "yes"
>
>>> ENABLE_GLOBALS_BACKUPS=yes
>
>>>
>
>>> #### SETTINGS FOR ROTATED BACKUPS ####
>
>>>
>
>>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>
>>> DAY_OF_WEEK_TO_KEEP=5
>
>>>
>
>>> # Number of days to keep daily backups
>
>>> DAYS_TO_KEEP=7
>
>>>
>
>>> # How many weeks to keep weekly backups
>
>>> WEEKS_TO_KEEP=5
>
>>>
>
>>> ######################################
>
>>>
>
>>> #VI PG_BACKUP.SH
>
>>>
>
>>> #!/bin/bash
>
>>>
>
>>> ###########################
>
>>> ####### LOAD CONFIG #######
>
>>> ###########################
>
>>>
>
>>> while [ $# -gt 0 ]; do
>
>>> case $1 in
>
>>> -c)
>
>>> if [ -r "$2" ]; then
>
>>> source "$2"
>
>>> shift 2
>
>>> else
>
>>> ${ECHO} "Unreadable config file
>
>>> \"$2\"" 1>&2
>
>>> exit 1
>
>>> fi
>
>>> ;;
>
>>> *)
>
>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>
>>> exit 2
>
>>> ;;
>
>>> esac
>
>>> done
>
>>>
>
>>> if [ $# = 0 ]; then
>
>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>
>>> source $SCRIPTPATH/pg_backup.config
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### PRE-BACKUP CHECKS ####
>
>>> ###########################
>
>>>
>
>>> # Make sure we're running as the required backup user
>
>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
>
>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> ### INITIALISE DEFAULTS ###
>
>>> ###########################
>
>>>
>
>>> if [ ! $HOSTNAME ]; then
>
>>> HOSTNAME="localhost"
>
>>> fi;
>
>>>
>
>>> if [ ! $USERNAME ]; then
>
>>> USERNAME="postgres"
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### START THE BACKUPS ####
>
>>> ###########################
>
>>>
>
>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>
>>>
>
>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>
>>>
>
>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>
>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>
>>> and fix it!" 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> #######################
>
>>> ### GLOBALS BACKUPS ###
>
>>> #######################
>
>>>
>
>>> echo -e "\n\nPerforming globals backup"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Globals backup"
>
>>>
>
>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce globals backup"
>
>>> 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz
>
>>> fi
>
>>> else
>
>>> echo "None"
>
>>> fi
>
>>>
>
>>> ###########################
>
>>> ### SCHEMA-ONLY BACKUPS ###
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>
>>> '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>
>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>
>>>
>
>>> echo -e "\n\nPerforming schema-only backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$SCHEMA_ONLY_QUERY" postgres`
>
>>>
>
>>> echo -e "The following databases were matched for schema-only
>
>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>
>>>
>
>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>
>>> do
>
>>> echo "Schema-only backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to backup database schema of
>
>>> $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>
>>> fi
>
>>> done
>
>>>
>
>>> ###########################
>
>>> ###### FULL BACKUPS #######
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>
>>> datname !~ '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>
>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
>
>>> datname;"
>
>>>
>
>>> echo -e "\n\nPerforming full backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$FULL_BACKUP_QUERY" postgres`
>
>>> do
>
>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Plain backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce plain backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>
>>> fi
>
>>> fi
>
>>>
>
>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Custom backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>
>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce custom backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>
>>> fi
>
>>> fi
>
>>>
>
>>> done
>
>>>
>
>>> echo -e "\nAll database backups complete!"
>
>>>
>
>>> I'm appreciate if anyone know how to correct this?
>
>>>
>
>>> thank you.
>
>>>
>
>>> 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
>
>>
>
>>
>
>>
>
>> Links:
>
>> ------
>
>> [1] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 18:59 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-26 20:55 ` Steve Crawford <scrawford@pinpointresearch.com>
2019-02-26 21:09 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2 siblings, 1 reply; 24+ messages in thread
From: Steve Crawford @ 2019-02-26 20:55 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>; gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Some random observations that may or may not be of use.
Are you making sure to reload PostgreSQL whenever you make a config change?
> I also found pg_hba.conf on both folders
> /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I
> modified it as above and the script is not working even run from the
> command prompt.
>
>
To find out which pg_hba.conf file your running database is using run:
show all;
Then search for hba_file or view directly by:
select setting from pg_settings where name = 'hba_file';
You can verify your pg_hba.conf settings with (as user postgres):
select * from pg_hba_file_rules ;
> # export HOSTNAME=hostname
> # export USERNAME=postgres
> # export DATABASE=postgres
> # export PORT 5432
> # pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
>
Looks like you are missing the "=" between PORT and 5432
Cheers,
Steve
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 18:59 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 20:55 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Steve Crawford <scrawford@pinpointresearch.com>
@ 2019-02-26 21:09 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 21:14 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL gilberto.castillo@etecsa.cu
0 siblings, 1 reply; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-26 21:09 UTC (permalink / raw)
To: Steve Crawford <scrawford@pinpointresearch.com>; +Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>; gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
I typo PORT without =
yes, I did reload postgres after make a configuration change.
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
On Tuesday, February 26, 2019 3:55 PM, Steve Crawford <scrawford@pinpointresearch.com> wrote:
Some random observations that may or may not be of use.
Are you making sure to reload PostgreSQL whenever you make a config change?
I also found pg_hba.conf on both folders /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the script is not working even run from the command prompt.
To find out which pg_hba.conf file your running database is using run:
show all;
Then search for hba_file or view directly by:
select setting from pg_settings where name = 'hba_file';
You can verify your pg_hba.conf settings with (as user postgres):
select * from pg_hba_file_rules ;
# export HOSTNAME=hostname
# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
Looks like you are missing the "=" between PORT and 5432
Cheers,Steve
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 18:59 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 20:55 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Steve Crawford <scrawford@pinpointresearch.com>
2019-02-26 21:09 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-26 21:14 ` gilberto.castillo@etecsa.cu
0 siblings, 0 replies; 24+ messages in thread
From: gilberto.castillo@etecsa.cu @ 2019-02-26 21:14 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: Steve Crawford <scrawford@pinpointresearch.com>; Shreeyansh Dba <shreeyansh2014@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Is possible that postgres it is running for other port? Check!!
El 2019-02-26 16:09, Pepe TD Vo escribió:
> I typo PORT without =
>
> yes, I did reload postgres after make a configuration change.
>
> 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
>
> On Tuesday, February 26, 2019 3:55 PM, Steve Crawford
> <scrawford@pinpointresearch.com> wrote:
>
> Some random observations that may or may not be of use.
>
> Are you making sure to reload PostgreSQL whenever you make a config
> change?
>
>> I also found pg_hba.conf on both folders
>> /var/lib/pgsql/11/data/pg_hba.conf &
>> /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the
>> script is not working even run from the command prompt.
>
> To find out which pg_hba.conf file your running database is using run:
>
> show all;
>
> Then search for hba_file or view directly by:
>
> select setting from pg_settings where name = 'hba_file';
>
> You can verify your pg_hba.conf settings with (as user postgres):
>
> select * from pg_hba_file_rules ;
>
>> # export HOSTNAME=hostname
>>
>> # export USERNAME=postgres
>> # export DATABASE=postgres
>> # export PORT 5432
>> # pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f
>> /tmp/postgresbakup.sql
>
> Looks like you are missing the "=" between PORT and 5432
>
> Cheers,
> Steve
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 18:59 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-26 21:27 ` David G. Johnston <david.g.johnston@gmail.com>
2019-02-27 00:03 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2 siblings, 1 reply; 24+ messages in thread
From: David G. Johnston @ 2019-02-26 21:27 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>; gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Tue, Feb 26, 2019 at 11:59 AM Pepe TD Vo <pepevo@yahoo.com> wrote:
> postgres=# select pg_conf_load_time() > modification from pg_stat_file('pg_hba.conf'):
> ?column?
> ----------
> f
> (1 row)
>
> Can you tell me what "f" mean?
Your query has an inequality (comparison) expression for its only
column - the result of which can be only: true, false, or NULL. The
"f" means false.
David J.
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 18:59 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 21:27 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL David G. Johnston <david.g.johnston@gmail.com>
@ 2019-02-27 00:03 ` Pepe TD Vo <pepevo@yahoo.com>
0 siblings, 0 replies; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-27 00:03 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>; gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
I already checked netstat -p and the port for Postgres is 5432.
Do I need to alter pg_conf_load_time to true?
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
On Tuesday, February 26, 2019 4:27 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Tue, Feb 26, 2019 at 11:59 AM Pepe TD Vo <pepevo@yahoo.com> wrote:
> postgres=# select pg_conf_load_time() > modification from pg_stat_file('pg_hba.conf'):
> ?column?
> ----------
> f
> (1 row)
>
> Can you tell me what "f" mean?
Your query has an inequality (comparison) expression for its only
column - the result of which can be only: true, false, or NULL. The
"f" means false.
David J.
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-27 06:14 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-27 11:37 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2 siblings, 1 reply; 24+ messages in thread
From: Shreeyansh Dba @ 2019-02-27 06:14 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; +Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
Hmmn, An error says you don't have mentioned an entry of server from where
you are performing the backup.
Are you performing a backup from the local machine or remote server?
Check the below parameter settings and make sure you have an entry of your
remote server in pg_hba.conf file if you are taking backup remotely.
listen_addresses = '*'
port = your_db_port
Thanks & Regards,
*Shreeyansh DBA Team*
www.shreeyansh.com
On Tue, Feb 26, 2019 at 11:16 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
> same error:
>
> run as root:
> # export HOSTNAME=hostname
> # export USERNAME=postgres
> # export DATABASE=postgres
> # export PORT 5432
> # pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
>
> pg_dump:[archiver (db)]connection to database "DATABASE" failed: could not
> connect to server: Connection refused
> Is the server running on host "portal-p" (138.24.1.110) and acceptiong
> TCP/IP connection on port 5432?
>
> run as postgres
> # export HOSTNAME=hostname
> # export USERNAME=postgres
> # export DATABASE=postgres
> # export PORT 5432
> # pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
>
> pg_dump:[archiver (db)]connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
>
> portal-p already on /etc/hosts.
>
> 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
>
>
> On Tuesday, February 26, 2019 11:01 AM, Shreeyansh Dba <
> shreeyansh2014@gmail.com> wrote:
>
>
> Ohh, It looks your pg_hba entries are correct, reset your database user
> "postgres" password then try again or use -w option, use a single hba.conf
> file.
>
> try: pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postresp.sql
>
> Thanks & Regards,
> *Shreeyansh DBA Team*
> www.shreeyansh.com
>
>
> On Tue, Feb 26, 2019 at 9:06 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
>
> yes mam'm/sir. I already posted it
>
> here it is again.
>
> #vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
>
> #TYPE DATABASE USER ADDRESS METHOD
> # "local" is for Unix domain socket connectiosn only
>
> local all all trust
>
> # IPv4 local connections:
>
> host all all 127.0.0.1/32 trust
>
> # IPv6 local connections:
>
> host all all ::1/128 trust
>
> # allow all replication connections from localhost, by a user with the
> replication privilege
> local replication all trust
> host replication all 127.0.0.1/32 trust
> host replication all ::1/128 trust
>
>
> I also found pg_hba.conf on both folders
> /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I
> modified it as above and the script is not working even run from the
> command prompt.
>
> #vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf &
> /var/lib/pgsql/data/pg_hba.conf)
>
> #TYPE DATABASE USER ADDRESS METHOD
> # "local" is for Unix domain socket connectiosn only
>
> local all all trust
>
> # IPv4 local connections:
>
> host all all 127.0.0.1/32 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 trust
>
> # allow all replication connections from localhost, by a user with the
> replication privilege
> local replication all trust
> host replication all 127.0.0.1/32 rust
> host replication all ::1/128 trust
>
>
> why do I have 3 pg_hba.conf? which one should use?
>
> thank you for looking into it.
>
> 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
>
>
> On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba <
> shreeyansh2014@gmail.com> wrote:
>
>
> The error message says the authentication method used isn't trust. Can you
> please share your pg_hba.conf file entries.
>
> Thanks & Regards,
> *Shreeyansh DBA Team*
> www.shr Hi Pepe eeyansh.com <http://www.shreeyansh.com/;
>
>
> On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
>
> No sir. I have tried what your suggestion and still failed.
>
> as root:
>
> # export HOSTNAME="localhost"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
> # export HOSTNAME="127.0.0.1"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
>
> as same as postgres:
>
> #su - postgres
>
> export HOSTNAME="localhost"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
> # export HOSTNAME="127.0.0.1"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL:
> Ident authentication failed for user "postgres"
>
>
> as the postgres, I can run pgdump dbname > output.sql
>
> 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
>
>
> On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <
> gilberto.castillo@etecsa.cu> wrote:
>
>
> El 2019-02-25 14:16, Pepe TD Vo escribió:
> > I am running script in local host (same db server)
>
> El 2019-02-25 14:16, Pepe TD Vo escribió:
> > I am running script in local host (same db server)
>
>
> Please, Check this:
>
> root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
> USERNAME="postgres"; DATABASE="postgres"
>
> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
> Password:
> pg_dump: [archiver (db)] connection to database "postgres" failed:
> FATAL: password authentication failed for user "postgres"
> FATAL: password authentication failed for user "postgres"
>
>
> Other:
>
> root@gilbertoc:/home/gilbertoc# sudo su - postgres
>
> postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
> DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/postresp.sql
> /tmp/postresp.sql: Permiso denegado
>
>
> Fine:
>
> postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
> DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/salvapostgres.backup
> postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
> /tmp/salvapostgres.backup
>
>
> >
> > 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> > <gilberto.castillo@etecsa.cu> wrote:
> >
> > El 2019-02-25 13:48, Pepe TD Vo escribió:
> >
> >> Thank you for your information.
> >
> >> I saw this document this morning and I did check my pg_hba.conf and
> >
> >> for local host and tried to connect to the template1/0 and/or other
> >
> >> database with postgres fine without prompting me for the password
> >
> >>
> >
> >> #psql -d template0 -U postgres
> >
> >> template0-#
> >
> >> #psql -d template1 -U postgres
> >
> >> template1-#
> >
> >>
> >
> >> #psql -d CIDR -U postgres
> >
> >> CIDR-#
> >
> >> #psql -d postgres -U postgres
> >
> >> postgres-#
> >
> >>
> >
> >> and a pg_hba.conf:
> >
> >>
> >
> >> "
> >
> >>
> >
> >> #TYPE DATABASE USER ADDRESS METHOD
> >
> >> local all all trust
> >
> >> host all all 127.0.0.1/32 trust
> >
> >> host all all ::1/128 trust
> >
> > Look here the IP only connect to localhost. From where Are your
> > running
> >
> > the script?
> >
> >> #allo replication connections from localhost, by a user with the
> >
> >> replication privilege
> >
> >> local replication all trust
> >
> >> host replication all 127..0.1/32 trust
> >
> >> host replication all ::1/128 trust
> >
> >>
> >
> >> the problem is I'm not sure I need to reconfigure pg_hba.conf with
> >
> >> database with user postgres or not?
> >
> >>
> >
> >> When I'm connecting into the each database and the "show
> > pg_hba.conf"
> >
> >> show nothing.
> >
> >>
> >
> >> postgres-# show pg_hba.conf
> >
> >> postgres-#
> >
> >>
> >
> >> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
> >
> >> <shreeyansh2014@gmail.com> wrote:
> >
> >>
> >
> >> Hi Pepe,
> >
> >>
> >
> >> It seems your are using os user for taking the backup.
> >
> >>
> >
> >> When you run command line commands against the postgres database and
> >
> >> they ask for the user and password that is the database user
> > postgres
> >
> >> and its associated password, so when you do something like: psql -d
> >
> >> template1 -U postgres the password you will be prompted for is
> >
> >> your_db_user password
> >
> >>
> >
> >> Now the above also depends on what is set in pg_hba.conf for the
> >
> >> various combinations of host, database, user and auth_method.
> >
> >>
> >
> >> For more information see
> >
> >>
> > https://www.postgresql.org/docs/9.5/static/client-authentication.html
> >
> >>
> >
> >> Thanks & Regards,
> >
> >> SHREEYANSH DBA TEAM
> >
> >> www.shreeyansh.com [1]
> >
> >>
> >
> >> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> > wrote:
> >
> >>
> >
> >>> good morning Expert DBAs,
> >
> >>>
> >
> >>> I created a script to do backup and I have faced the error of
> >
> >>>
> >
> >>>> Performing globals backup:
> >
> >>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
> >
> >>>> authentication failed for user "postgres" fro globals backup. As
> >
> >>>> same as performing schema-only backups and full 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 but
> >
> >>> couldn't run from script even the script declared
> >
> >>> BACKUP_USER=postgres
> >
> >>>
> >
> >>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
> >
> >>> backup script working fine
> >
> >>>
> >
> >>> # VI PG_BACKUP.CONFIG
> >
> >>>
> >
> >>> ##############################
> >
> >>> ## POSTGRESQL BACKUP CONFIG ##
> >
> >>> ##############################
> >
> >>>
> >
> >>> # Optional system user to run backups as. If the user the script
> > is
> >
> >>> running as doesn't match this
> >
> >>> # the script terminates. Leave blank to skip check.
> >
> >>> BACKUP_USER=
> >
> >>>
> >
> >>> # Optional hostname to adhere to pg_hba policies. Will default to
> >
> >>> "localhost" if none specified.
> >
> >>> HOSTNAME="hostname"
> >
> >>>
> >
> >>> # Optional username to connect to database as. Will default to
> >
> >>> "postgres" if none specified.
> >
> >>> USERNAME="postgres"
> >
> >>>
> >
> >>> # This dir will be created if it doesn't exist. This must be
> >
> >>> writable by the user the script is
> >
> >>> # running as.
> >
> >>> BACKUP_DIR=/home/backups/database/postgresql/
> >
> >>>
> >
> >>> # List of strings to match against in database name, separated by
> >
> >>> space or comma, for which we only
> >
> >>> # wish to keep a backup of the schema, not the data. Any database
> >
> >>> names which contain any of these
> >
> >>> # values will be considered candidates. (e.g. "system_log" will
> >
> >>> match "dev_system_log_2010-01")
> >
> >>> SCHEMA_ONLY_LIST=""
> >
> >>>
> >
> >>> # Will produce a custom-format backup if set to "yes"
> >
> >>> ENABLE_CUSTOM_BACKUPS=yes
> >
> >>>
> >
> >>> # Will produce a gzipped plain-format backup if set to "yes"
> >
> >>> ENABLE_PLAIN_BACKUPS=yes
> >
> >>>
> >
> >>> # Will produce gzipped sql file containing the cluster globals,
> > like
> >
> >>> users and passwords, if set to "yes"
> >
> >>> ENABLE_GLOBALS_BACKUPS=yes
> >
> >>>
> >
> >>> #### SETTINGS FOR ROTATED BACKUPS ####
> >
> >>>
> >
> >>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
> >
> >>> DAY_OF_WEEK_TO_KEEP=5
> >
> >>>
> >
> >>> # Number of days to keep daily backups
> >
> >>> DAYS_TO_KEEP=7
> >
> >>>
> >
> >>> # How many weeks to keep weekly backups
> >
> >>> WEEKS_TO_KEEP=5
> >
> >>>
> >
> >>> ######################################
> >
> >>>
> >
> >>> #VI PG_BACKUP.SH
> >
> >>>
> >
> >>> #!/bin/bash
> >
> >>>
> >
> >>> ###########################
> >
> >>> ####### LOAD CONFIG #######
> >
> >>> ###########################
> >
> >>>
> >
> >>> while [ $# -gt 0 ]; do
> >
> >>> case $1 in
> >
> >>> -c)
> >
> >>> if [ -r "$2" ]; then
> >
> >>> source "$2"
> >
> >>> shift 2
> >
> >>> else
> >
> >>> ${ECHO} "Unreadable config file
> >
> >>> \"$2\"" 1>&2
> >
> >>> exit 1
> >
> >>> fi
> >
> >>> ;;
> >
> >>> *)
> >
> >>> ${ECHO} "Unknown Option \"$1\"" 1>&2
> >
> >>> exit 2
> >
> >>> ;;
> >
> >>> esac
> >
> >>> done
> >
> >>>
> >
> >>> if [ $# = 0 ]; then
> >
> >>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
> >
> >>> source $SCRIPTPATH/pg_backup.config
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> #### PRE-BACKUP CHECKS ####
> >
> >>> ###########################
> >
> >>>
> >
> >>> # Make sure we're running as the required backup user
> >
> >>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
> >
> >>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
> >
> >>> exit 1;
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> ### INITIALISE DEFAULTS ###
> >
> >>> ###########################
> >
> >>>
> >
> >>> if [ ! $HOSTNAME ]; then
> >
> >>> HOSTNAME="localhost"
> >
> >>> fi;
> >
> >>>
> >
> >>> if [ ! $USERNAME ]; then
> >
> >>> USERNAME="postgres"
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> #### START THE BACKUPS ####
> >
> >>> ###########################
> >
> >>>
> >
> >>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
> >
> >>>
> >
> >>> echo "Making backup directory in $FINAL_BACKUP_DIR"
> >
> >>>
> >
> >>> if ! mkdir -p $FINAL_BACKUP_DIR; then
> >
> >>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
> >
> >>> and fix it!" 1>&2
> >
> >>> exit 1;
> >
> >>> fi;
> >
> >>>
> >
> >>> #######################
> >
> >>> ### GLOBALS BACKUPS ###
> >
> >>> #######################
> >
> >>>
> >
> >>> echo -e "\n\nPerforming globals backup"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Globals backup"
> >
> >>>
> >
> >>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
> >
> >>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce globals backup"
> >
> >>> 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"globals".sql.gz
> >
> >>> fi
> >
> >>> else
> >
> >>> echo "None"
> >
> >>> fi
> >
> >>>
> >
> >>> ###########################
> >
> >>> ### SCHEMA-ONLY BACKUPS ###
> >
> >>> ###########################
> >
> >>>
> >
> >>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> >
> >>> do
> >
> >>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
> >
> >>> '$SCHEMA_ONLY_DB'"
> >
> >>> done
> >
> >>>
> >
> >>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
> >
> >>> $SCHEMA_ONLY_CLAUSE order by datname;"
> >
> >>>
> >
> >>> echo -e "\n\nPerforming schema-only backups"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> >
> >>> "$SCHEMA_ONLY_QUERY" postgres`
> >
> >>>
> >
> >>> echo -e "The following databases were matched for schema-only
> >
> >>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
> >
> >>>
> >
> >>> for DATABASE in $SCHEMA_ONLY_DB_LIST
> >
> >>> do
> >
> >>> echo "Schema-only backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> >
> >>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to backup database schema of
> >
> >>> $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
> >
> >>> fi
> >
> >>> done
> >
> >>>
> >
> >>> ###########################
> >
> >>> ###### FULL BACKUPS #######
> >
> >>> ###########################
> >
> >>>
> >
> >>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> >
> >>> do
> >
> >>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
> >
> >>> datname !~ '$SCHEMA_ONLY_DB'"
> >
> >>> done
> >
> >>>
> >
> >>> FULL_BACKUP_QUERY="select datname from pg_database where not
> >
> >>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
> >
> >>> datname;"
> >
> >>>
> >
> >>> echo -e "\n\nPerforming full backups"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> >
> >>> "$FULL_BACKUP_QUERY" postgres`
> >
> >>> do
> >
> >>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Plain backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> >
> >>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce plain backup
> >
> >>> database $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
> >
> >>> fi
> >
> >>> fi
> >
> >>>
> >
> >>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Custom backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
> >
> >>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce custom backup
> >
> >>> database $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE".custom
> >
> >>> fi
> >
> >>> fi
> >
> >>>
> >
> >>> done
> >
> >>>
> >
> >>> echo -e "\nAll database backups complete!"
> >
> >>>
> >
> >>> I'm appreciate if anyone know how to correct this?
> >
> >>>
> >
> >>> thank you.
> >
> >>>
> >
> >>> 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
> >
> >>
> >
> >>
> >
> >>
> >
> >> Links:
> >
> >> ------
> >
> >> [1] http://www.shreeyansh.com/
>
>
>
>
>
>
>
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-27 06:14 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
@ 2019-02-27 11:37 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-28 14:26 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
0 siblings, 1 reply; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-27 11:37 UTC (permalink / raw)
To: Shreeyansh Dba <shreeyansh2014@gmail.com>; +Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
I am back up from local machine not remote. Even the port and listen_address = '*' already set.
I can run without environment settings but not with the environment settings.
V/r,
Bach Nga
On Feb 27, 2019, at 1:14 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
Hmmn, An error says you don't have mentioned an entry of server from where you are performing the backup.
Are you performing a backup from the local machine or remote server?
Check the below parameter settings and make sure you have an entry of your remote server in pg_hba.conf file if you are taking backup remotely.
listen_addresses = '*'
port = your_db_port
Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com
> On Tue, Feb 26, 2019 at 11:16 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
> same error:
>
> run as root:
> # export HOSTNAME=hostname
> # export USERNAME=postgres
> # export DATABASE=postgres
> # export PORT 5432
> # pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
>
> pg_dump:[archiver (db)]connection to database "DATABASE" failed: could not connect to server: Connection refused
> Is the server running on host "portal-p" (138.24.1.110) and acceptiong TCP/IP connection on port 5432?
>
> run as postgres
> # export HOSTNAME=hostname
> # export USERNAME=postgres
> # export DATABASE=postgres
> # export PORT 5432
> # pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
>
> pg_dump:[archiver (db)]connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
>
>
> portal-p already on /etc/hosts.
>
> 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
>
>
> On Tuesday, February 26, 2019 11:01 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
>
>
> Ohh, It looks your pg_hba entries are correct, reset your database user "postgres" password then try again or use -w option, use a single hba.conf file.
>
> try: pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postresp.sql
>
> Thanks & Regards,
> Shreeyansh DBA Team
> www.shreeyansh.com
>
>
> On Tue, Feb 26, 2019 at 9:06 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
> yes mam'm/sir. I already posted it
>
> here it is again.
>
> #vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
>
> #TYPE DATABASE USER ADDRESS METHOD
> # "local" is for Unix domain socket connectiosn only
>
> local all all trust
>
> # IPv4 local connections:
>
> host all all 127.0.0.1/32 trust
>
> # IPv6 local connections:
>
> host all all ::1/128 trust
>
> # allow all replication connections from localhost, by a user with the replication privilege
> local replication all trust
> host replication all 127.0.0.1/32 trust
> host replication all ::1/128 trust
>
>
> I also found pg_hba.conf on both folders /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the script is not working even run from the command prompt.
>
> #vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf)
>
> #TYPE DATABASE USER ADDRESS METHOD
> # "local" is for Unix domain socket connectiosn only
>
> local all all trust
>
> # IPv4 local connections:
>
> host all all 127.0.0.1/32 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 trust
>
> # allow all replication connections from localhost, by a user with the replication privilege
> local replication all trust
> host replication all 127.0.0.1/32 rust
> host replication all ::1/128 trust
>
>
> why do I have 3 pg_hba.conf? which one should use?
>
> thank you for looking into it.
>
> 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
>
>
> On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
>
>
> The error message says the authentication method used isn't trust. Can you please share your pg_hba.conf file entries.
>
> Thanks & Regards,
> Shreeyansh DBA Team
> www.shr Hi Pepe eeyansh.com
>
>
> On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
> No sir. I have tried what your suggestion and still failed.
>
> as root:
>
> # export HOSTNAME="localhost"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
>
> # export HOSTNAME="127.0.0.1"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
>
>
> as same as postgres:
>
> #su - postgres
>
> export HOSTNAME="localhost"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
>
> # export HOSTNAME="127.0.0.1"
> # export USERNAME="postgres"
> # export DATABASE="postgres"
> # pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
>
> pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
>
>
> as the postgres, I can run pgdump dbname > output.sql
>
> 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
>
>
> On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <gilberto.castillo@etecsa.cu> wrote:
>
>
> El 2019-02-25 14:16, Pepe TD Vo escribió:
> > I am running script in local host (same db server)
>
> El 2019-02-25 14:16, Pepe TD Vo escribió:
> > I am running script in local host (same db server)
>
>
> Please, Check this:
>
> root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
> USERNAME="postgres"; DATABASE="postgres"
>
> root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
> "$USERNAME" "$DATABASE" > /tmp/postresp.sql
> Password:
> pg_dump: [archiver (db)] connection to database "postgres" failed:
> FATAL: password authentication failed for user "postgres"
> FATAL: password authentication failed for user "postgres"
>
>
> Other:
>
> root@gilbertoc:/home/gilbertoc# sudo su - postgres
>
> postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
> DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/postresp.sql
> /tmp/postresp.sql: Permiso denegado
>
>
> Fine:
>
> postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
> DATABASE="postgres"
>
> postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
> "$DATABASE" > /tmp/salvapostgres.backup
> postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
> /tmp/salvapostgres.backup
>
>
> >
> > 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> > <gilberto.castillo@etecsa.cu> wrote:
> >
> > El 2019-02-25 13:48, Pepe TD Vo escribió:
> >
> >> Thank you for your information.
> >
> >> I saw this document this morning and I did check my pg_hba.conf and
> >
> >> for local host and tried to connect to the template1/0 and/or other
> >
> >> database with postgres fine without prompting me for the password
> >
> >>
> >
> >> #psql -d template0 -U postgres
> >
> >> template0-#
> >
> >> #psql -d template1 -U postgres
> >
> >> template1-#
> >
> >>
> >
> >> #psql -d CIDR -U postgres
> >
> >> CIDR-#
> >
> >> #psql -d postgres -U postgres
> >
> >> postgres-#
> >
> >>
> >
> >> and a pg_hba.conf:
> >
> >>
> >
> >> "
> >
> >>
> >
> >> #TYPE DATABASE USER ADDRESS METHOD
> >
> >> local all all trust
> >
> >> host all all 127.0.0.1/32 trust
> >
> >> host all all ::1/128 trust
> >
> > Look here the IP only connect to localhost. From where Are your
> > running
> >
> > the script?
> >
> >> #allo replication connections from localhost, by a user with the
> >
> >> replication privilege
> >
> >> local replication all trust
> >
> >> host replication all 127..0.1/32 trust
> >
> >> host replication all ::1/128 trust
> >
> >>
> >
> >> the problem is I'm not sure I need to reconfigure pg_hba.conf with
> >
> >> database with user postgres or not?
> >
> >>
> >
> >> When I'm connecting into the each database and the "show
> > pg_hba.conf"
> >
> >> show nothing.
> >
> >>
> >
> >> postgres-# show pg_hba.conf
> >
> >> postgres-#
> >
> >>
> >
> >> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
> >
> >> <shreeyansh2014@gmail.com> wrote:
> >
> >>
> >
> >> Hi Pepe,
> >
> >>
> >
> >> It seems your are using os user for taking the backup.
> >
> >>
> >
> >> When you run command line commands against the postgres database and
> >
> >> they ask for the user and password that is the database user
> > postgres
> >
> >> and its associated password, so when you do something like: psql -d
> >
> >> template1 -U postgres the password you will be prompted for is
> >
> >> your_db_user password
> >
> >>
> >
> >> Now the above also depends on what is set in pg_hba.conf for the
> >
> >> various combinations of host, database, user and auth_method.
> >
> >>
> >
> >> For more information see
> >
> >>
> > https://www.postgresql.org/docs/9.5/static/client-authentication.html
> >
> >>
> >
> >> Thanks & Regards,
> >
> >> SHREEYANSH DBA TEAM
> >
> >> www.shreeyansh.com [1]
> >
> >>
> >
> >> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> > wrote:
> >
> >>
> >
> >>> good morning Expert DBAs,
> >
> >>>
> >
> >>> I created a script to do backup and I have faced the error of
> >
> >>>
> >
> >>>> Performing globals backup:
> >
> >>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
> >
> >>>> authentication failed for user "postgres" fro globals backup. As
> >
> >>>> same as performing schema-only backups and full 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 but
> >
> >>> couldn't run from script even the script declared
> >
> >>> BACKUP_USER=postgres
> >
> >>>
> >
> >>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
> >
> >>> backup script working fine
> >
> >>>
> >
> >>> # VI PG_BACKUP.CONFIG
> >
> >>>
> >
> >>> ##############################
> >
> >>> ## POSTGRESQL BACKUP CONFIG ##
> >
> >>> ##############################
> >
> >>>
> >
> >>> # Optional system user to run backups as. If the user the script
> > is
> >
> >>> running as doesn't match this
> >
> >>> # the script terminates. Leave blank to skip check.
> >
> >>> BACKUP_USER=
> >
> >>>
> >
> >>> # Optional hostname to adhere to pg_hba policies. Will default to
> >
> >>> "localhost" if none specified.
> >
> >>> HOSTNAME="hostname"
> >
> >>>
> >
> >>> # Optional username to connect to database as. Will default to
> >
> >>> "postgres" if none specified.
> >
> >>> USERNAME="postgres"
> >
> >>>
> >
> >>> # This dir will be created if it doesn't exist. This must be
> >
> >>> writable by the user the script is
> >
> >>> # running as.
> >
> >>> BACKUP_DIR=/home/backups/database/postgresql/
> >
> >>>
> >
> >>> # List of strings to match against in database name, separated by
> >
> >>> space or comma, for which we only
> >
> >>> # wish to keep a backup of the schema, not the data. Any database
> >
> >>> names which contain any of these
> >
> >>> # values will be considered candidates. (e.g. "system_log" will
> >
> >>> match "dev_system_log_2010-01")
> >
> >>> SCHEMA_ONLY_LIST=""
> >
> >>>
> >
> >>> # Will produce a custom-format backup if set to "yes"
> >
> >>> ENABLE_CUSTOM_BACKUPS=yes
> >
> >>>
> >
> >>> # Will produce a gzipped plain-format backup if set to "yes"
> >
> >>> ENABLE_PLAIN_BACKUPS=yes
> >
> >>>
> >
> >>> # Will produce gzipped sql file containing the cluster globals,
> > like
> >
> >>> users and passwords, if set to "yes"
> >
> >>> ENABLE_GLOBALS_BACKUPS=yes
> >
> >>>
> >
> >>> #### SETTINGS FOR ROTATED BACKUPS ####
> >
> >>>
> >
> >>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
> >
> >>> DAY_OF_WEEK_TO_KEEP=5
> >
> >>>
> >
> >>> # Number of days to keep daily backups
> >
> >>> DAYS_TO_KEEP=7
> >
> >>>
> >
> >>> # How many weeks to keep weekly backups
> >
> >>> WEEKS_TO_KEEP=5
> >
> >>>
> >
> >>> ######################################
> >
> >>>
> >
> >>> #VI PG_BACKUP.SH
> >
> >>>
> >
> >>> #!/bin/bash
> >
> >>>
> >
> >>> ###########################
> >
> >>> ####### LOAD CONFIG #######
> >
> >>> ###########################
> >
> >>>
> >
> >>> while [ $# -gt 0 ]; do
> >
> >>> case $1 in
> >
> >>> -c)
> >
> >>> if [ -r "$2" ]; then
> >
> >>> source "$2"
> >
> >>> shift 2
> >
> >>> else
> >
> >>> ${ECHO} "Unreadable config file
> >
> >>> \"$2\"" 1>&2
> >
> >>> exit 1
> >
> >>> fi
> >
> >>> ;;
> >
> >>> *)
> >
> >>> ${ECHO} "Unknown Option \"$1\"" 1>&2
> >
> >>> exit 2
> >
> >>> ;;
> >
> >>> esac
> >
> >>> done
> >
> >>>
> >
> >>> if [ $# = 0 ]; then
> >
> >>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
> >
> >>> source $SCRIPTPATH/pg_backup.config
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> #### PRE-BACKUP CHECKS ####
> >
> >>> ###########################
> >
> >>>
> >
> >>> # Make sure we're running as the required backup user
> >
> >>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
> >
> >>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
> >
> >>> exit 1;
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> ### INITIALISE DEFAULTS ###
> >
> >>> ###########################
> >
> >>>
> >
> >>> if [ ! $HOSTNAME ]; then
> >
> >>> HOSTNAME="localhost"
> >
> >>> fi;
> >
> >>>
> >
> >>> if [ ! $USERNAME ]; then
> >
> >>> USERNAME="postgres"
> >
> >>> fi;
> >
> >>>
> >
> >>> ###########################
> >
> >>> #### START THE BACKUPS ####
> >
> >>> ###########################
> >
> >>>
> >
> >>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
> >
> >>>
> >
> >>> echo "Making backup directory in $FINAL_BACKUP_DIR"
> >
> >>>
> >
> >>> if ! mkdir -p $FINAL_BACKUP_DIR; then
> >
> >>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
> >
> >>> and fix it!" 1>&2
> >
> >>> exit 1;
> >
> >>> fi;
> >
> >>>
> >
> >>> #######################
> >
> >>> ### GLOBALS BACKUPS ###
> >
> >>> #######################
> >
> >>>
> >
> >>> echo -e "\n\nPerforming globals backup"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Globals backup"
> >
> >>>
> >
> >>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
> >
> >>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce globals backup"
> >
> >>> 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"globals".sql.gz
> >
> >>> fi
> >
> >>> else
> >
> >>> echo "None"
> >
> >>> fi
> >
> >>>
> >
> >>> ###########################
> >
> >>> ### SCHEMA-ONLY BACKUPS ###
> >
> >>> ###########################
> >
> >>>
> >
> >>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> >
> >>> do
> >
> >>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
> >
> >>> '$SCHEMA_ONLY_DB'"
> >
> >>> done
> >
> >>>
> >
> >>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
> >
> >>> $SCHEMA_ONLY_CLAUSE order by datname;"
> >
> >>>
> >
> >>> echo -e "\n\nPerforming schema-only backups"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> >
> >>> "$SCHEMA_ONLY_QUERY" postgres`
> >
> >>>
> >
> >>> echo -e "The following databases were matched for schema-only
> >
> >>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
> >
> >>>
> >
> >>> for DATABASE in $SCHEMA_ONLY_DB_LIST
> >
> >>> do
> >
> >>> echo "Schema-only backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> >
> >>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to backup database schema of
> >
> >>> $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
> >
> >>> fi
> >
> >>> done
> >
> >>>
> >
> >>> ###########################
> >
> >>> ###### FULL BACKUPS #######
> >
> >>> ###########################
> >
> >>>
> >
> >>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
> >
> >>> do
> >
> >>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
> >
> >>> datname !~ '$SCHEMA_ONLY_DB'"
> >
> >>> done
> >
> >>>
> >
> >>> FULL_BACKUP_QUERY="select datname from pg_database where not
> >
> >>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
> >
> >>> datname;"
> >
> >>>
> >
> >>> echo -e "\n\nPerforming full backups"
> >
> >>> echo -e "--------------------------------------------\n"
> >
> >>>
> >
> >>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
> >
> >>> "$FULL_BACKUP_QUERY" postgres`
> >
> >>> do
> >
> >>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Plain backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
> >
> >>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce plain backup
> >
> >>> database $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
> >
> >>> fi
> >
> >>> fi
> >
> >>>
> >
> >>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
> >
> >>> then
> >
> >>> echo "Custom backup of $DATABASE"
> >
> >>>
> >
> >>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
> >
> >>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
> >
> >>> echo "[!!ERROR!!] Failed to produce custom backup
> >
> >>> database $DATABASE" 1>&2
> >
> >>> else
> >
> >>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
> >
> >>> $FINAL_BACKUP_DIR"$DATABASE".custom
> >
> >>> fi
> >
> >>> fi
> >
> >>>
> >
> >>> done
> >
> >>>
> >
> >>> echo -e "\nAll database backups complete!"
> >
> >>>
> >
> >>> I'm appreciate if anyone know how to correct this?
> >
> >>>
> >
> >>> thank you.
> >
> >>>
> >
> >>> 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
> >
> >>
> >
> >>
> >
> >>
> >
> >> Links:
> >
> >> ------
> >
> >> [1] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
* Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 16:00 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-27 06:14 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-27 11:37 ` Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
@ 2019-02-28 14:26 ` Pepe TD Vo <pepevo@yahoo.com>
0 siblings, 0 replies; 24+ messages in thread
From: Pepe TD Vo @ 2019-02-28 14:26 UTC (permalink / raw)
To: Pepe TD Vo <pepevo@yahoo.com>; Shreeyansh Dba <shreeyansh2014@gmail.com>; +Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>; Pgsql-admin <pgsql-admin@lists.postgresql.org>
thank you for you all. I hard code everything in 1 script and it works fine now.
I am appreciated for all the inputs and advises.
best regards, 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 Wednesday, February 27, 2019 6:38 AM, Pepe TD Vo <pepevo@yahoo.com> wrote:
I am back up from local machine not remote. Even the port and listen_address = '*' already set.
I can run without environment settings but not with the environment settings.
V/r,
Bach Nga
On Feb 27, 2019, at 1:14 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
Hmmn, An error says you don't have mentioned an entry of server from where you are performing the backup.Are you performing a backup from the local machine or remote server?Check the below parameter settings and make sure you have an entry of your remote server in pg_hba.conf file if you are taking backup remotely. listen_addresses = '*'
port = your_db_port
Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com
On Tue, Feb 26, 2019 at 11:16 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
same error:
run as root:# export HOSTNAME=hostname# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
pg_dump:[archiver (db)]connection to database "DATABASE" failed: could not connect to server: Connection refusedIs the server running on host "portal-p" (138.24.1.110) and acceptiong TCP/IP connection on port 5432?
run as postgres# export HOSTNAME=hostname# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql
pg_dump:[archiver (db)]connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
portal-p already on /etc/hosts.
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
On Tuesday, February 26, 2019 11:01 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
Ohh, It looks your pg_hba entries are correct, reset your database user "postgres" password then try again or use -w option, use a single hba.conf file.
try: pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postresp.sql
Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com
On Tue, Feb 26, 2019 at 9:06 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
yes mam'm/sir. I already posted it
here it is again.
#vi pg_hba.conf (from /usr/local/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 trusthost replication all ::1/128 trust
I also found pg_hba.conf on both folders /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the script is not working even run from the command prompt.
#vi pg_hba.conf ( (from /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf)
#TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connectiosn only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
host all power_user 0.0.0.0/0 md5host all other_user 0.0.0.0/0 md5host all storageLoader 0.0.0.0/0 md5
# IPv6 local connections:
host all all ::1/128 trust
# allow all replication connections from localhost, by a user with the replication privilegelocal replication all trusthost replication all 127.0.0.1/32 rusthost replication all ::1/128 trust
why do I have 3 pg_hba.conf? which one should use?
thank you for looking into it.
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
On Tuesday, February 26, 2019 9:52 AM, Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:
The error message says the authentication method used isn't trust. Can you please share your pg_hba.conf file entries.
Thanks & Regards,
Shreeyansh DBA Team
www.shr Hi Pepe eeyansh.com
On Tue, Feb 26, 2019 at 7:41 PM Pepe TD Vo <pepevo@yahoo.com> wrote:
No sir. I have tried what your suggestion and still failed.
as root:
# export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as same as postgres:
#su - postgres
export HOSTNAME="localhost"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
# export HOSTNAME="127.0.0.1"# export USERNAME="postgres"# export DATABASE="postgres"# pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" > /tmp/postresp.sql
pg_dump:[archiver (db)] connection to database "DATABASE" failed: FATAL: Ident authentication failed for user "postgres"
as the postgres, I can run pgdump dbname > output.sql
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
On Monday, February 25, 2019 2:39 PM, "gilberto.castillo@etecsa.cu" <gilberto.castillo@etecsa.cu> wrote:
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
El 2019-02-25 14:16, Pepe TD Vo escribió:
> I am running script in local host (same db server)
Please, Check this:
root@gilbertoc:/home/gilbertoc# export HOSTNAME="localhost";
USERNAME="postgres"; DATABASE="postgres"
root@gilbertoc:/home/gilbertoc# pg_dump -Fc -h "$HOSTNAME" -U
"$USERNAME" "$DATABASE" > /tmp/postresp.sql
Password:
pg_dump: [archiver (db)] connection to database "postgres" failed:
FATAL: password authentication failed for user "postgres"
FATAL: password authentication failed for user "postgres"
Other:
root@gilbertoc:/home/gilbertoc# sudo su - postgres
postgres@gilbertoc:~$ export HOSTNAME="localhost"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/postresp.sql
/tmp/postresp.sql: Permiso denegado
Fine:
postgres@gilbertoc:~$ export HOSTNAME="127.0.0.1"; USERNAME="postgres";
DATABASE="postgres"
postgres@gilbertoc:~$ pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME"
"$DATABASE" > /tmp/salvapostgres.backup
postgres@gilbertoc:~$ ls /tmp/salvapostgres.backup
/tmp/salvapostgres.backup
>
> 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 Monday, February 25, 2019 1:58 PM, "gilberto.castillo@etecsa.cu"
> <gilberto.castillo@etecsa.cu> wrote:
>
> El 2019-02-25 13:48, Pepe TD Vo escribió:
>
>> Thank you for your information.
>
>> I saw this document this morning and I did check my pg_hba.conf and
>
>> for local host and tried to connect to the template1/0 and/or other
>
>> database with postgres fine without prompting me for the password
>
>>
>
>> #psql -d template0 -U postgres
>
>> template0-#
>
>> #psql -d template1 -U postgres
>
>> template1-#
>
>>
>
>> #psql -d CIDR -U postgres
>
>> CIDR-#
>
>> #psql -d postgres -U postgres
>
>> postgres-#
>
>>
>
>> and a pg_hba.conf:
>
>>
>
>> "
>
>>
>
>> #TYPE DATABASE USER ADDRESS METHOD
>
>> local all all trust
>
>> host all all 127.0.0.1/32 trust
>
>> host all all ::1/128 trust
>
> Look here the IP only connect to localhost. From where Are your
> running
>
> the script?
>
>> #allo replication connections from localhost, by a user with the
>
>> replication privilege
>
>> local replication all trust
>
>> host replication all 127..0.1/32 trust
>
>> host replication all ::1/128 trust
>
>>
>
>> the problem is I'm not sure I need to reconfigure pg_hba.conf with
>
>> database with user postgres or not?
>
>>
>
>> When I'm connecting into the each database and the "show
> pg_hba.conf"
>
>> show nothing.
>
>>
>
>> postgres-# show pg_hba.conf
>
>> postgres-#
>
>>
>
>> 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 Monday, February 25, 2019 12:28 PM, Shreeyansh Dba
>
>> <shreeyansh2014@gmail.com> wrote:
>
>>
>
>> Hi Pepe,
>
>>
>
>> It seems your are using os user for taking the backup.
>
>>
>
>> When you run command line commands against the postgres database and
>
>> they ask for the user and password that is the database user
> postgres
>
>> and its associated password, so when you do something like: psql -d
>
>> template1 -U postgres the password you will be prompted for is
>
>> your_db_user password
>
>>
>
>> Now the above also depends on what is set in pg_hba.conf for the
>
>> various combinations of host, database, user and auth_method.
>
>>
>
>> For more information see
>
>>
> https://www.postgresql.org/docs/9.5/static/client-authentication.html
>
>>
>
>> Thanks & Regards,
>
>> SHREEYANSH DBA TEAM
>
>> www.shreeyansh.com [1]
>
>>
>
>> On Mon, Feb 25, 2019 at 10:21 PM Pepe TD Vo <pepevo@yahoo.com>
> wrote:
>
>>
>
>>> good morning Expert DBAs,
>
>>>
>
>>> I created a script to do backup and I have faced the error of
>
>>>
>
>>>> Performing globals backup:
>
>>>> pg_dumpall: could not connect to database "template1":FATAL: Ident
>
>>>> authentication failed for user "postgres" fro globals backup. As
>
>>>> same as performing schema-only backups and full 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 but
>
>>> couldn't run from script even the script declared
>
>>> BACKUP_USER=postgres
>
>>>
>
>>> If I take the syntax, -H "$HOSTNAME" -U "$USERNAME" out and the
>
>>> backup script working fine
>
>>>
>
>>> # VI PG_BACKUP.CONFIG
>
>>>
>
>>> ##############################
>
>>> ## POSTGRESQL BACKUP CONFIG ##
>
>>> ##############################
>
>>>
>
>>> # Optional system user to run backups as. If the user the script
> is
>
>>> running as doesn't match this
>
>>> # the script terminates. Leave blank to skip check.
>
>>> BACKUP_USER=
>
>>>
>
>>> # Optional hostname to adhere to pg_hba policies. Will default to
>
>>> "localhost" if none specified.
>
>>> HOSTNAME="hostname"
>
>>>
>
>>> # Optional username to connect to database as. Will default to
>
>>> "postgres" if none specified.
>
>>> USERNAME="postgres"
>
>>>
>
>>> # This dir will be created if it doesn't exist. This must be
>
>>> writable by the user the script is
>
>>> # running as.
>
>>> BACKUP_DIR=/home/backups/database/postgresql/
>
>>>
>
>>> # List of strings to match against in database name, separated by
>
>>> space or comma, for which we only
>
>>> # wish to keep a backup of the schema, not the data. Any database
>
>>> names which contain any of these
>
>>> # values will be considered candidates. (e.g. "system_log" will
>
>>> match "dev_system_log_2010-01")
>
>>> SCHEMA_ONLY_LIST=""
>
>>>
>
>>> # Will produce a custom-format backup if set to "yes"
>
>>> ENABLE_CUSTOM_BACKUPS=yes
>
>>>
>
>>> # Will produce a gzipped plain-format backup if set to "yes"
>
>>> ENABLE_PLAIN_BACKUPS=yes
>
>>>
>
>>> # Will produce gzipped sql file containing the cluster globals,
> like
>
>>> users and passwords, if set to "yes"
>
>>> ENABLE_GLOBALS_BACKUPS=yes
>
>>>
>
>>> #### SETTINGS FOR ROTATED BACKUPS ####
>
>>>
>
>>> # Which day to take the weekly backup from (1-7 = Monday-Sunday)
>
>>> DAY_OF_WEEK_TO_KEEP=5
>
>>>
>
>>> # Number of days to keep daily backups
>
>>> DAYS_TO_KEEP=7
>
>>>
>
>>> # How many weeks to keep weekly backups
>
>>> WEEKS_TO_KEEP=5
>
>>>
>
>>> ######################################
>
>>>
>
>>> #VI PG_BACKUP.SH
>
>>>
>
>>> #!/bin/bash
>
>>>
>
>>> ###########################
>
>>> ####### LOAD CONFIG #######
>
>>> ###########################
>
>>>
>
>>> while [ $# -gt 0 ]; do
>
>>> case $1 in
>
>>> -c)
>
>>> if [ -r "$2" ]; then
>
>>> source "$2"
>
>>> shift 2
>
>>> else
>
>>> ${ECHO} "Unreadable config file
>
>>> \"$2\"" 1>&2
>
>>> exit 1
>
>>> fi
>
>>> ;;
>
>>> *)
>
>>> ${ECHO} "Unknown Option \"$1\"" 1>&2
>
>>> exit 2
>
>>> ;;
>
>>> esac
>
>>> done
>
>>>
>
>>> if [ $# = 0 ]; then
>
>>> SCRIPTPATH=$(cd ${0%/*} && pwd -P)
>
>>> source $SCRIPTPATH/pg_backup.config
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### PRE-BACKUP CHECKS ####
>
>>> ###########################
>
>>>
>
>>> # Make sure we're running as the required backup user
>
>>> if [ "$BACKUP_USER" != "" -a "$(id -un)" != "$BACKUP_USER" ]; then
>
>>> echo "This script must be run as $BACKUP_USER. Exiting." 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> ### INITIALISE DEFAULTS ###
>
>>> ###########################
>
>>>
>
>>> if [ ! $HOSTNAME ]; then
>
>>> HOSTNAME="localhost"
>
>>> fi;
>
>>>
>
>>> if [ ! $USERNAME ]; then
>
>>> USERNAME="postgres"
>
>>> fi;
>
>>>
>
>>> ###########################
>
>>> #### START THE BACKUPS ####
>
>>> ###########################
>
>>>
>
>>> FINAL_BACKUP_DIR=$BACKUP_DIR"`date +\%Y-\%m-\%d`/"
>
>>>
>
>>> echo "Making backup directory in $FINAL_BACKUP_DIR"
>
>>>
>
>>> if ! mkdir -p $FINAL_BACKUP_DIR; then
>
>>> echo "Cannot create backup directory in $FINAL_BACKUP_DIR. Go
>
>>> and fix it!" 1>&2
>
>>> exit 1;
>
>>> fi;
>
>>>
>
>>> #######################
>
>>> ### GLOBALS BACKUPS ###
>
>>> #######################
>
>>>
>
>>> echo -e "\n\nPerforming globals backup"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> if [ $ENABLE_GLOBALS_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Globals backup"
>
>>>
>
>>> if ! pg_dumpall -g -h "$HOSTNAME" -U "$USERNAME" | gzip >
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce globals backup"
>
>>> 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"globals".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"globals".sql.gz
>
>>> fi
>
>>> else
>
>>> echo "None"
>
>>> fi
>
>>>
>
>>> ###########################
>
>>> ### SCHEMA-ONLY BACKUPS ###
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> SCHEMA_ONLY_CLAUSE="$SCHEMA_ONLY_CLAUSE or datname ~
>
>>> '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> SCHEMA_ONLY_QUERY="select datname from pg_database where false
>
>>> $SCHEMA_ONLY_CLAUSE order by datname;"
>
>>>
>
>>> echo -e "\n\nPerforming schema-only backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> SCHEMA_ONLY_DB_LIST=`psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$SCHEMA_ONLY_QUERY" postgres`
>
>>>
>
>>> echo -e "The following databases were matched for schema-only
>
>>> backup:\n${SCHEMA_ONLY_DB_LIST}\n"
>
>>>
>
>>> for DATABASE in $SCHEMA_ONLY_DB_LIST
>
>>> do
>
>>> echo "Schema-only backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -s -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to backup database schema of
>
>>> $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE"_SCHEMA.sql.gz
>
>>> fi
>
>>> done
>
>>>
>
>>> ###########################
>
>>> ###### FULL BACKUPS #######
>
>>> ###########################
>
>>>
>
>>> for SCHEMA_ONLY_DB in ${SCHEMA_ONLY_LIST//,/ }
>
>>> do
>
>>> EXCLUDE_SCHEMA_ONLY_CLAUSE="$EXCLUDE_SCHEMA_ONLY_CLAUSE and
>
>>> datname !~ '$SCHEMA_ONLY_DB'"
>
>>> done
>
>>>
>
>>> FULL_BACKUP_QUERY="select datname from pg_database where not
>
>>> datistemplate and datallowconn $EXCLUDE_SCHEMA_ONLY_CLAUSE order by
>
>>> datname;"
>
>>>
>
>>> echo -e "\n\nPerforming full backups"
>
>>> echo -e "--------------------------------------------\n"
>
>>>
>
>>> for DATABASE in `psql -h "$HOSTNAME" -U "$USERNAME" -At -c
>
>>> "$FULL_BACKUP_QUERY" postgres`
>
>>> do
>
>>> if [ $ENABLE_PLAIN_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Plain backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fp -h "$HOSTNAME" -U "$USERNAME" "$DATABASE" |
>
>>> gzip > $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce plain backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".sql.gz.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".sql.gz
>
>>> fi
>
>>> fi
>
>>>
>
>>> if [ $ENABLE_CUSTOM_BACKUPS = "yes" ]
>
>>> then
>
>>> echo "Custom backup of $DATABASE"
>
>>>
>
>>> if ! pg_dump -Fc -h "$HOSTNAME" -U "$USERNAME" "$DATABASE"
>
>>> -f $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress; then
>
>>> echo "[!!ERROR!!] Failed to produce custom backup
>
>>> database $DATABASE" 1>&2
>
>>> else
>
>>> mv $FINAL_BACKUP_DIR"$DATABASE".custom.in_progress
>
>>> $FINAL_BACKUP_DIR"$DATABASE".custom
>
>>> fi
>
>>> fi
>
>>>
>
>>> done
>
>>>
>
>>> echo -e "\nAll database backups complete!"
>
>>>
>
>>> I'm appreciate if anyone know how to correct this?
>
>>>
>
>>> thank you.
>
>>>
>
>>> 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
>
>>
>
>>
>
>>
>
>> Links:
>
>> ------
>
>> [1] http://www.shreeyansh.com/
^ permalink raw reply [nested|flat] 24+ messages in thread
end of thread, other threads:[~2019-02-28 14:26 UTC | newest]
Thread overview: 24+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-02-25 16:50 pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 16:54 ` gilberto.castillo@etecsa.cu
2019-02-25 17:28 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-25 18:48 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-25 18:58 ` gilberto.castillo@etecsa.cu
2019-02-26 14:11 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 14:52 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 15:19 ` gilberto.castillo@etecsa.cu
2019-02-26 15:36 Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 15:46 ` gilberto.castillo@etecsa.cu
2019-02-26 15:48 ` gilberto.castillo@etecsa.cu
2019-02-26 16:00 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-26 17:46 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 18:29 ` gilberto.castillo@etecsa.cu
2019-02-26 18:59 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 20:52 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 20:55 ` Steve Crawford <scrawford@pinpointresearch.com>
2019-02-26 21:09 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-26 21:14 ` gilberto.castillo@etecsa.cu
2019-02-26 21:27 ` David G. Johnston <david.g.johnston@gmail.com>
2019-02-27 00:03 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-27 06:14 ` Shreeyansh Dba <shreeyansh2014@gmail.com>
2019-02-27 11:37 ` Pepe TD Vo <pepevo@yahoo.com>
2019-02-28 14:26 ` Pepe TD Vo <pepevo@yahoo.com>
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