<div dir="ltr">Hi All. I try to setup pgpool 3.6 with postgres-9.6.1 master-slave and stream replication.<div>In pgpool.log I see errors.</div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">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
</span><br>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 "<a href="http://172.20.200.3:16067" target="_blank">172.20.200.3:16067</a>"
<br>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
<br>Dec 12 21:11:09 SBC-MSK pgpool[11551]: [7-1] 2016-12-12 21:11:09: pid 11551: LOG: master watchdog node "<a href="http://172.20.200.3:5432" target="_blank">172.20.200.3:5432</a> Linux <a href="http://sbc-spb.taxisaturn.ru" target="_blank">sbc-spb.taxisaturn.ru</a>" returned status <br>for 2 backend nodes
<br>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 "<a href="http://172.20.200.3:5432" target="_blank">172.20.200.3:5432</a> Linux <a href="http://sbc-spb.taxisaturn.ru" target="_blank">sbc-spb.taxisaturn.ru</a>" <br>is -1
<br>Dec 12 21:11:09 SBC-MSK pgpool[11551]: [9-1] 2016-12-12 21:11:09: pid 11551: LOG: Setting up socket for <a href="http://0.0.0.0:5432" target="_blank">0.0.0.0:5432</a>
<br>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
<br>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)
<br>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
<br>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
<br>Dec 12 21:11:09 SBC-MSK pgpool[11551]: [14-1] 2016-12-12 21:11:09: pid 11551: ERROR: failed to authenticate
<br>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"
<br>Dec 12 21:11:09 SBC-MSK pgpool[11589]: [11-1] 2016-12-12 21:11:09: pid 11589: ERROR: failed to authenticate
<br>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"
<br>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
<br>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.
<br>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
<br>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"
<br>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
<br>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
<br>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.
<br>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
<br>Dec 12 21:11:10 SBC-MSK pgpool[11554]: [12-2] 2016-12-12 21:11:10: pid 11554: DETAIL: set SO_REUSEPORT
<br>Dec 12 21:11:10 SBC-MSK pgpool[11555]: [12-2] 2016-12-12 21:11:10: pid 11555: DETAIL: set SO_REUSEPORT
<br>Dec 12 21:11:19 SBC-MSK pgpool[11589]: [12-1] 2016-12-12 21:11:19: pid 11589: ERROR: failed to authenticate
<br>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"
<br>Dec 12 21:11:29 SBC-MSK pgpool[11589]: [13-1] 2016-12-12 21:11:29: pid<br></span></div><div><span style="font-family:monospace"><br></span></div><div><font face="monospace">When i try to connect with same password with psql it's connect. So the password is ok.</font></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">node_id | hostname | port | status | lb_weight | role | select_cnt | load_balance_node | replication_delay </span><br>---------+--------------+-----<wbr>-+--------+-----------+-------<wbr>--+------------+--------------<wbr>-----+-------------------
<br> 0 | 172.20.200.2 | 5433 | down | 0.500000 | standby | 0 | false | 0
<br> 1 | 172.20.200.3 | 5433 | up | 0.500000 | standby | 0 | true | 0<br>
</span><span style="font-family:monospace"><span style="color:rgb(0,0,0)">#-----------------------------<wbr>------------------------------<wbr>-------------------
</span><br># HEALTH CHECK
<br>#-----------------------------<wbr>------------------------------<wbr>-------------------
<br>
<br>health_check_period = 0
<br> <wbr> # Health check period
<br> <wbr> # Disabled (0) by default
<br>health_check_timeout = 20
<br> <wbr> # Health check timeout
<br> <wbr> # 0 means no timeout
<br>health_check_user = 'postgres'
<br> <wbr> # Health check user
<br>health_check_password = 'password'
<br> <wbr> # Password for health check user
<br>health_check_database = 'postgres'
<br> <wbr> # Database name for health check. If '', tries 'postgres' frist, then 'template1'
<br>
<br>health_check_max_retries = 0
<br> <wbr> # Maximum number of times to retry a failed health check before giving up.
<br>health_check_retry_delay = 1
<br> <wbr> # Amount of time to wait (in seconds) between retries.
<br>connect_timeout = 10000
<br> <wbr> # Timeout value in milliseconds before giving up to connect to backend.
<br> <wbr> <wbr> # Default is 10000 ms (10 second). Flaky network user may want to increase
<br> <wbr> <wbr> # the value. 0 means no timeout.
<br> <wbr> <wbr> # Note that this value is not only used for health check,
<br> <wbr> <wbr> # but also for ordinary conection to backend.
<br><br>
<br></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">#-----------------------------<wbr>------------------------------<wbr>-------------------
</span><br># MASTER/SLAVE MODE
<br>#-----------------------------<wbr>------------------------------<wbr>-------------------
<br>
<br>master_slave_mode = on
<br> <wbr> # Activate master/slave mode
<br> <wbr> # (change requires restart)
<br>master_slave_sub_mode = 'stream'
<br> <wbr> # Master/slave sub mode
<br> <wbr> # Valid values are combinations slony or
<br> <wbr> # stream. Default is slony.
<br> <wbr> # (change requires restart)
<br>
<br># - Streaming -
<br>
<br>sr_check_period = 10
<br> <wbr> # Streaming replication check period
<br> <wbr> # Disabled (0) by default
<br>sr_check_user = 'postgres'
<br> <wbr> # Streaming replication check user
<br> <wbr> # This is necessary even if you disable
<br> <wbr> # streaming replication delay check with
<br> <wbr> # sr_check_period = 0
<br>sr_check_password = 'password'
<br> <wbr> # Password for streaming replication check user
<br>sr_check_database = 'postgres'
<br> <wbr> # Database name for streaming replication check
<br>delay_threshold = 0
<br> <wbr> # Threshold before not dispatching query to standby node
<br> <wbr> # Unit is in bytes
<br> <wbr> # Disabled (0) by default<br>
<br></span></div></div>