[pgpool-general: 5162] pgpool config error
Kirill Galinurov
k.galinurov at gmail.com
Tue Dec 13 03:25:15 JST 2016
Hi All. I try to setup pgpool 3.6 with postgres-9.6.1 master-slave and
stream replication.
In pgpool.log I see errors.
Dec 12 21:11:09 SBC-MSK pgpool[11553]: [10-1] 2016-12-12 21:11:09: pid
11553: LOG: watchdog lifecheck trusted server "172.20.200.3" added for the
availability check
Dec 12 21:11:09 SBC-MSK pgpool[11552]: [18-1] 2016-12-12 21:11:09: pid
11552: LOG: new watchdog node connection is received from "
172.20.200.3:16067"
Dec 12 21:11:09 SBC-MSK pgpool[11552]: [19-1] 2016-12-12 21:11:09: pid
11552: LOG: new node joined the cluster hostname:"172.20.200.3" port:9000
pgpool_port:5432
Dec 12 21:11:09 SBC-MSK pgpool[11551]: [7-1] 2016-12-12 21:11:09: pid
11551: LOG: master watchdog node "172.20.200.3:5432 Linux
sbc-spb.taxisaturn.ru" returned status
for 2 backend nodes
Dec 12 21:11:09 SBC-MSK pgpool[11551]: [8-1] 2016-12-12 21:11:09: pid
11551: LOG: primary node on master watchdog node "172.20.200.3:5432 Linux
sbc-spb.taxisaturn.ru"
is -1
Dec 12 21:11:09 SBC-MSK pgpool[11551]: [9-1] 2016-12-12 21:11:09: pid
11551: LOG: Setting up socket for 0.0.0.0:5432
Dec 12 21:11:09 SBC-MSK pgpool[11551]: [10-1] 2016-12-12 21:11:09: pid
11551: LOG: Setting up socket for :::5432
Dec 12 21:11:09 SBC-MSK pgpool[11551]: [11-1] 2016-12-12 21:11:09: pid
11551: LOG: pgpool-II successfully started. version 3.6.0 (subaruboshi)
Dec 12 21:11:09 SBC-MSK pgpool[11551]: [12-1] 2016-12-12 21:11:09: pid
11551: LOG: find_primary_node: checking backend no 0
Dec 12 21:11:09 SBC-MSK pgpool[11551]: [13-1] 2016-12-12 21:11:09: pid
11551: LOG: find_primary_node: checking backend no 1
Dec 12 21:11:09 SBC-MSK pgpool[11551]: [14-1] 2016-12-12 21:11:09: pid
11551: ERROR: failed to authenticate
Dec 12 21:11:09 SBC-MSK pgpool[11551]: [14-2] 2016-12-12 21:11:09: pid
11551: DETAIL: password authentication failed for user "postgres"
Dec 12 21:11:09 SBC-MSK pgpool[11589]: [11-1] 2016-12-12 21:11:09: pid
11589: ERROR: failed to authenticate
Dec 12 21:11:09 SBC-MSK pgpool[11589]: [11-2] 2016-12-12 21:11:09: pid
11589: DETAIL: password authentication failed for user "postgres"
Dec 12 21:11:10 SBC-MSK pgpool[11555]: [10-1] 2016-12-12 21:11:10: pid
11555: LOG: creating socket for sending heartbeat
Dec 12 21:11:10 SBC-MSK pgpool[11554]: [10-1] 2016-12-12 21:11:10: pid
11554: LOG: createing watchdog heartbeat receive socket.
Dec 12 21:11:10 SBC-MSK pgpool[11555]: [10-2] 2016-12-12 21:11:10: pid
11555: DETAIL: bind send socket to device: eth1
Dec 12 21:11:10 SBC-MSK pgpool[11554]: [10-2] 2016-12-12 21:11:10: pid
11554: DETAIL: bind receive socket to device: "eth1"
Dec 12 21:11:10 SBC-MSK pgpool[11554]: [11-1] 2016-12-12 21:11:10: pid
11554: LOG: set SO_REUSEPORT option to the socket
Dec 12 21:11:10 SBC-MSK pgpool[11555]: [11-1] 2016-12-12 21:11:10: pid
11555: LOG: set SO_REUSEPORT option to the socket
Dec 12 21:11:10 SBC-MSK pgpool[11554]: [12-1] 2016-12-12 21:11:10: pid
11554: LOG: creating watchdog heartbeat receive socket.
Dec 12 21:11:10 SBC-MSK pgpool[11555]: [12-1] 2016-12-12 21:11:10: pid
11555: LOG: creating socket for sending heartbeat
Dec 12 21:11:10 SBC-MSK pgpool[11554]: [12-2] 2016-12-12 21:11:10: pid
11554: DETAIL: set SO_REUSEPORT
Dec 12 21:11:10 SBC-MSK pgpool[11555]: [12-2] 2016-12-12 21:11:10: pid
11555: DETAIL: set SO_REUSEPORT
Dec 12 21:11:19 SBC-MSK pgpool[11589]: [12-1] 2016-12-12 21:11:19: pid
11589: ERROR: failed to authenticate
Dec 12 21:11:19 SBC-MSK pgpool[11589]: [12-2] 2016-12-12 21:11:19: pid
11589: DETAIL: password authentication failed for user "postgres"
Dec 12 21:11:29 SBC-MSK pgpool[11589]: [13-1] 2016-12-12 21:11:29: pid
When i try to connect with same password with psql it's connect. So the
password is ok.
node_id | hostname | port | status | lb_weight | role | select_cnt |
load_balance_node | replication_delay
---------+--------------+------+--------+-----------+-------
--+------------+-------------------+-------------------
0 | 172.20.200.2 | 5433 | down | 0.500000 | standby | 0 |
false | 0
1 | 172.20.200.3 | 5433 | up | 0.500000 | standby | 0 |
true | 0
#------------------------------------------------------------------------------
# HEALTH CHECK
#------------------------------------------------------------------------------
health_check_period = 0
# Health check period
# Disabled (0) by default
health_check_timeout = 20
# Health check timeout
# 0 means no timeout
health_check_user = 'postgres'
# Health check user
health_check_password = 'password'
# Password for health check user
health_check_database = 'postgres'
# Database name for health check. If '',
tries 'postgres' frist, then 'template1'
health_check_max_retries = 0
# Maximum number of times to retry a
failed health check before giving up.
health_check_retry_delay = 1
# Amount of time to wait (in seconds)
between retries.
connect_timeout = 10000
# Timeout value in milliseconds before
giving up to connect to backend.
# Default
is 10000 ms (10 second). Flaky network user may want to increase
# the
value. 0 means no timeout.
# Note
that this value is not only used for health check,
# but
also for ordinary conection to backend.
#------------------------------------------------------------------------------
# MASTER/SLAVE MODE
#------------------------------------------------------------------------------
master_slave_mode = on
# Activate master/slave mode
# (change requires restart)
master_slave_sub_mode = 'stream'
# Master/slave sub mode
# Valid values are combinations slony or
# stream. Default is slony.
# (change requires restart)
# - Streaming -
sr_check_period = 10
# Streaming replication check period
# Disabled (0) by default
sr_check_user = 'postgres'
# Streaming replication check user
# This is necessary even if you disable
# streaming replication delay check with
# sr_check_period = 0
sr_check_password = 'password'
# Password for streaming replication
check user
sr_check_database = 'postgres'
# Database name for streaming replication
check
delay_threshold = 0
# Threshold before not dispatching query
to standby node
# Unit is in bytes
# Disabled (0) by default
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20161212/11667898/attachment.htm>
More information about the pgpool-general
mailing list