[pgpool-general: 5351] Re: can not connect to slave after failover

Tatsuo Ishii ishii at sraoss.co.jp
Tue Feb 28 11:27:31 JST 2017


> Im having an issue. So I have 3 vm servers running Centos 6 and
> postgres 9.4. I have 1 set up as a pgpool server. The other 2 are in a
> master slave configuration via hot_standby. The set up all works. From
> the pgpool server I can connect to both db servers via psql -h and ssh
> keys are set up. I have a script for fail over. In my test I will shut
> down the master, then pgpool runs my script and it reaches out to the
> slave and promotes it. However theres an issue. Pgpool then can not
> connect to the promoted slave. If as postgres I run psql -h I can
> connect fine. I checked the log file for pgpool and im getting 2 lines
> looping over and over.
> 
> 
> 2017-02-27 (current time) pid 2765: LOG: find_primary_node: checking
> backend no 0
> 2017-02-27 (current time) pid 2765: LOG: find_primary_node: checking
> backend no 1
> 
> Those just repeat over and over, and any attempted connection just
> hangs.

Pgpool-II uses sr_check_user, sr_check_password and sr_check_database
to connect to PostgreSQL. Are they valid?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


More information about the pgpool-general mailing list