[pgpool-general: 22] Re: About pgpool-HA with md5 authentication method

TAKATSUKA Haruka harukat at sraoss.co.jp
Fri Dec 2 13:25:00 JST 2011


Hi.

The pgpool-ha monitor program just runs psql like the following.

$ psql -U [pgpool.conf health check user] -h localhost \
       -p [pgpool port] -c 'SHOW pool_status' [pgpool.conf health check user]

You can edit ${OCF_ROOT}/resource.d/heartbeat/pgpool

- PGPOOL_MONITOR_ARGS="--conf=$PGP_CONF localhost"
+ PGPOOL_MONITOR_ARGS="--port=9999 --password=pass --username=checkuser --database=dbname localhost"

to specify connection parameters.

or

- PGPOOL_MONITOR=${PGPOOLCMD}.monitor
+ PGPOOL_MONITOR=true

to check only pgpool process existence.


regards, 


On Thu, 1 Dec 2011 22:05:53 -0430
Lazaro Rubén García Martinez <lgarciam at vnz.uci.cu> wrote:

> Hello everyone in the list, I am creating a high availability cluster with Pgpool-II, Pgpool-HA and Heartbet. The monitor operation fails if the authentication with the database use md5, but if the authentication method is true, there isn't problem. This is the information logged in PostgreSQL and pgpool log file each one.
> The question is:
> Allows pgpool-ha the md5 authentication method??
> 
> Postgres's log
> 
> LOG:  connection received: host=pg_01.vnz.uci.cu port=60224
> LOG:  could not receive data from client: Connection reset by peer
> LOG:  connection received: host=pg_01.vnz.uci.cu port=60226
> LOG:  could not receive data from client: Connection reset by peer
> LOG:  connection received: host=pg_01.vnz.uci.cu port=60228
> LOG:  could not receive data from client: Connection reset by peer
> LOG:  connection received: host=pg_01.vnz.uci.cu port=60230
> LOG:  could not receive data from client: Connection reset by peer
> LOG:  connection received: host=pg_01.vnz.uci.cu port=60232
> LOG:  could not receive data from client: Connection reset by peer
> LOG:  connection received: host=pg_01.vnz.uci.cu port=60234
> LOG:  could not receive data from client: Connection reset by peer
> 
> Pgpool's log
> 
> 2011-12-01 17:16:47 LOG:   pid 4636: connection received: host=localhost port=42143
> 2011-12-01 17:16:47 DEBUG: pid 4636: Protocol Major: 1234 Minor: 5679 database:  user:
> 2011-12-01 17:16:47 DEBUG: pid 4636: SSLRequest from client
> 2011-12-01 17:16:47 DEBUG: pid 4636: read_startup_packet: application_name: psql
> 2011-12-01 17:16:47 DEBUG: pid 4636: Protocol Major: 3 Minor: 0 database: pgpool user: pgpool
> 2011-12-01 17:16:47 DEBUG: pid 4636: new_connection: connecting 0 backend
> 2011-12-01 17:16:47 DEBUG: pid 4636: new_connection: connecting 1 backend
> 2011-12-01 17:16:47 DEBUG: pid 4636: new_connection: skipping slot 1 because backend_status = 3
> 2011-12-01 17:16:47 DEBUG: pid 4636: pool_ssl: sending client->server SSL request
> 2011-12-01 17:16:47 DEBUG: pid 4636: pool_ssl: client->server SSL response: S
> 2011-12-01 17:16:47 DEBUG: pid 4636: pool_read_message_length: slot: 0 length: 12
> 2011-12-01 17:16:47 DEBUG: pid 4636: pool_do_auth: auth kind:5
> 2011-12-01 17:16:47 DEBUG: pid 4636: trying md5 authentication
> 2011-12-01 17:16:47 ERROR: pid 4636: pool_ssl: SSL_read: no SSL error reported
> 2011-12-01 17:16:47 ERROR: pid 4636: pool_read: read failed (Success)
> 2011-12-01 17:16:47 DEBUG: pid 4636: read_password_packet_password: failed to read password packet "p"
> 2011-12-01 17:16:47 DEBUG: pid 4636: do_md5: read_password_packet failed
> 2011-12-01 17:16:47 DEBUG: pid 4636: do_md5failed in slot 0
> 
> Thank you very much for your time.
> Regards.





More information about the pgpool-general mailing list