View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000600Pgpool-IIBugpublic2020-03-30 21:072020-04-13 09:30
Reportersajithts Assigned Topengbo  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionopen 
Product Version4.1.0 
Summary0000600: Pgpool ii Node status 'waiting'
DescriptionWhen I try "show pool_status", some of the node status is shown 'waiting'

I tried "pcp_attach_node -U postgres -h 192.168.29.168 2" from one of the standby. But issue still persists
Tagspgpool

Activities

sajithts

2020-03-30 21:07

reporter  

pgpool status.JPG (77,049 bytes)   
pgpool status.JPG (77,049 bytes)   

pengbo

2020-03-31 17:26

developer   ~0003287

It is the normal behaviour.

"Waiting" means the PostgreSQL server is up and running but has not been connected from Pgpool-II yet.
"waiting" can be safely assumed same as "up".
So once a client connects to Pgpool-II, it connects to PostgreSQL and the status will be turned to "up".

sajithts

2020-03-31 22:52

reporter   ~0003288

@pengbo:

I tried "pcp_attach_node -U postgres -h 192.168.29.168 2" from one of the standby. Is there another way to connect clients to Pgpool-II?

Can you please elaborate the steps?

Thanks.

sajithts

2020-03-31 23:05

reporter   ~0003289

@pengbo:
This is my environment setup:
>1 Master node
>2 Standby nodes
>1 PgPool-II node
> CentOs7
>EDB Advanced Server Version 10
> EFM Version 3.9
>PgPool-II Version 4.1

I had follow the below steps:
     Step.1) Setup streaming replication by editing the postgresql.conf file
     Step.2) Install and configure EFM 3.9 for Automatic failover
     Step.3) Install and configure PgPool-II 4.1 for load balancing.

Step 1 & 2 are working fine.
But loadbalancing is not working.

Thanks.

pengbo

2020-04-06 09:56

developer   ~0003303

Could you share the pgpool.log?

sajithts

2020-04-06 16:26

reporter   ~0003305

@pengbo:
edb-pgpool-4.1.log is pasted below.


2020-04-01 04:36:35: pid 45283: WARNING: "pool_conn_dbname" is depreciated, use "health_check_database" to configure health check database
2020-04-01 04:36:35: pid 45283: LOG: stop request sent to pgpool. waiting for termination...
.done.
2020-04-01 04:36:37: pid 45290: WARNING: "pool_conn_dbname" is depreciated, use "health_check_database" to configure health check database
2020-04-01 04:36:37: pid 45290: LOG: Backend status file /var/log/edb/pgpool4.1/pgpool_status discarded
2020-04-01 04:36:37: pid 45290: LOG: memory cache initialized
2020-04-01 04:36:37: pid 45290: DETAIL: memcache blocks :64
2020-04-01 04:36:37: pid 45290: LOG: pool_discard_oid_maps: discarded memqcache oid maps
2020-04-01 04:36:37: pid 45290: LOG: Setting up socket for 0.0.0.0:9998
2020-04-01 04:36:37: pid 45290: LOG: Setting up socket for :::9998
2020-04-01 04:36:37: pid 45325: LOG: PCP process: 45325 started
2020-04-01 04:36:37: pid 45290: LOG: pgpool-II successfully started. version 4.1.1 (karasukiboshi)
2020-04-01 04:46:04: pid 45325: LOG: forked new pcp worker, pid=45887 socket=7
2020-04-01 04:46:04: pid 45887: FATAL: authentication failed for user "postgres"
2020-04-01 04:46:04: pid 45887: DETAIL: username and/or password does not match
2020-04-01 04:46:04: pid 45325: LOG: PCP process with pid: 45887 exit with SUCCESS.
2020-04-01 04:46:04: pid 45325: LOG: PCP process with pid: 45887 exits with status 256
2020-04-01 04:49:29: pid 45313: LOG: pool_reuse_block: blockid: 0
2020-04-01 04:49:29: pid 45313: CONTEXT: while searching system catalog, When relcache is missed
2020-04-01 04:54:29: pid 45290: LOG: child process with pid: 45313 exits with status 256
2020-04-01 04:54:29: pid 45290: LOG: fork a new child process with pid: 46410
2020-04-01 04:58:40: pid 45325: LOG: forked new pcp worker, pid=46641 socket=7
2020-04-01 04:58:40: pid 46641: FATAL: authentication failed for user "postgres"
2020-04-01 04:58:40: pid 46641: DETAIL: username and/or password does not match
2020-04-01 04:58:40: pid 45325: LOG: PCP process with pid: 46641 exit with SUCCESS.
2020-04-01 04:58:40: pid 45325: LOG: PCP process with pid: 46641 exits with status 256
2020-04-01 05:04:35: pid 47005: WARNING: "pool_conn_dbname" is depreciated, use "health_check_database" to configure health check database
2020-04-01 05:04:35: pid 47005: LOG: stop request sent to pgpool. waiting for termination...
.done.
2020-04-01 05:04:37: pid 47013: WARNING: "pool_conn_dbname" is depreciated, use "health_check_database" to configure health check database
2020-04-01 05:04:37: pid 47013: LOG: Backend status file /var/log/edb/pgpool4.1/pgpool_status discarded
2020-04-01 05:04:37: pid 47013: LOG: memory cache initialized
2020-04-01 05:04:37: pid 47013: DETAIL: memcache blocks :64
2020-04-01 05:04:37: pid 47013: LOG: pool_discard_oid_maps: discarded memqcache oid maps
2020-04-01 05:04:37: pid 47013: LOG: Setting up socket for 0.0.0.0:9998
2020-04-01 05:04:37: pid 47013: LOG: Setting up socket for :::9998
2020-04-01 05:04:37: pid 47013: LOG: pgpool-II successfully started. version 4.1.1 (karasukiboshi)
2020-04-01 05:04:37: pid 47048: LOG: PCP process: 47048 started
2020-04-01 05:04:43: pid 47035: LOG: pool_reuse_block: blockid: 0
2020-04-01 05:04:43: pid 47035: CONTEXT: while searching system catalog, When relcache is missed
2020-04-01 05:05:58: pid 47048: LOG: forked new pcp worker, pid=47142 socket=7
2020-04-01 05:05:58: pid 47142: FATAL: authentication failed for user "postgres"
2020-04-01 05:05:58: pid 47142: DETAIL: username and/or password does not match
2020-04-01 05:05:58: pid 47048: LOG: PCP process with pid: 47142 exit with SUCCESS.
2020-04-01 05:05:58: pid 47048: LOG: PCP process with pid: 47142 exits with status 256
2020-04-01 05:14:11: pid 47013: LOG: child process with pid: 47035 exits with status 256
2020-04-01 05:14:11: pid 47013: LOG: fork a new child process with pid: 47624
2020-04-01 05:18:27: pid 47013: LOG: child process with pid: 47016 exits with status 256
2020-04-01 05:18:27: pid 47013: LOG: fork a new child process with pid: 47828
2020-04-01 09:12:22: pid 47013: LOG: child process with pid: 47038 exits with status 256
2020-04-01 09:12:22: pid 47013: LOG: fork a new child process with pid: 61245

pengbo

2020-04-07 10:46

developer   ~0003308

I found the following error:
----------------------------------------
2020-04-01 05:05:58: pid 47142: FATAL: authentication failed for user "postgres"
2020-04-01 05:05:58: pid 47142: DETAIL: username and/or password does not match
----------------------------------------

Does pcp_recovery_node command exit with "pcp_recovery_node -- Command Successful"?

Example:
$ pcp_recovery_node -h /tmp -p 11001 -U pengbo -n 1
Password:
pcp_recovery_node -- Command Successful

sajithts

2020-04-07 19:56

reporter   ~0003310

@pengbo

I have tried "pcp_recovery_node" command on my Pgpool-II server running node.

The result is given:

[root@localhost bin]# ./pcp_recovery_node -h /tmp -p 9898 -U postgres -n 1
Password:
ERROR: process recovery request failed
DETAIL: recovery request is only allowed in replication and streaming replication modes.

Here 9898 is my PCP process port and 'postgres' is my PCP user.
Streaming replication is already implemented and running with EFM.

The complete pgpool log is given:
root@localhost bin]# more /var/log/edb/pgpool4.0/edb-pgpool-4.0.log
2020-04-07 16:21:52: pid 4262: LOG: child process with pid: 4288 exits with status 256
2020-04-07 16:21:52: pid 4262: LOG: fork a new child process with pid: 5678
2020-04-07 16:22:00: pid 4296: LOG: forked new pcp worker, pid=5683 socket=7
2020-04-07 16:22:00: pid 5683: ERROR: process recovery request failed
2020-04-07 16:22:00: pid 5683: DETAIL: recovery request is only allowed in replication and streaming replication modes.
2020-04-07 16:22:00: pid 4296: LOG: PCP process with pid: 5683 exit with SUCCESS.
2020-04-07 16:22:00: pid 4296: LOG: PCP process with pid: 5683 exits with status 0
[root@localhost bin]#

sajithts

2020-04-09 23:40

reporter   ~0003311

Problem resolved.
Loadbalancing is working.

The parameter 'master_slave_mode' was not set to ON. That was the issue.
After it set to ON, loadbalancing is working.

Please close the issue.

Thanks for the support.

pengbo

2020-04-13 09:30

developer   ~0003314

Great to hear that!
I am going to close this issue.

Issue History

Date Modified Username Field Change
2020-03-30 21:07 sajithts New Issue
2020-03-30 21:07 sajithts File Added: pgpool status.JPG
2020-03-30 21:07 sajithts Tag Attached: pgpool
2020-03-31 12:38 pengbo Assigned To => pengbo
2020-03-31 12:38 pengbo Status new => assigned
2020-03-31 12:38 pengbo Description Updated
2020-03-31 17:26 pengbo Note Added: 0003287
2020-03-31 17:26 pengbo Status assigned => feedback
2020-03-31 22:52 sajithts Note Added: 0003288
2020-03-31 22:52 sajithts Status feedback => assigned
2020-03-31 23:05 sajithts Note Added: 0003289
2020-04-06 09:56 pengbo Note Added: 0003303
2020-04-06 16:26 sajithts Note Added: 0003305
2020-04-07 10:46 pengbo Note Added: 0003308
2020-04-07 19:56 sajithts Note Added: 0003310
2020-04-09 23:40 sajithts Note Added: 0003311
2020-04-13 09:30 pengbo Note Added: 0003314
2020-04-13 09:30 pengbo Status assigned => closed