View Issue Details

IDProjectCategoryView StatusLast Update
0000473Pgpool-IIBugpublic2019-05-21 16:15
Reportersandeepkandhway Assigned Topengbo  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionopen 
PlatformLINUXOSRHELOS Version7.2
Product Version3.5.5 
Summary0000473: pgPool no starting up post system reboot
DescriptionHi Team,

I have 3 servers (1 master 2 standby) and pgPool running on the same. EDB EFM cluster is also configured.
However I am facing the below issue while starting up the pgPool on master (note: both standbys are reachable).

After server reboot pgPool not getting started and giving below error in /var/log/messages:

Mar 7 12:01:07 vm1 pgpool[4381]: [2-1] 2019-03-07 12:01:07: pid 4381: WARNING: failed to open status file at: "/tmp/edb/pgpool3.5/pgpool_status"
Mar 7 12:01:07 vm1 pgpool[4381]: [2-2] 2019-03-07 12:01:07: pid 4381: DETAIL: "Permission denied"
Mar 7 12:01:07 vm1 pgpool[4381]: [7-1] 2019-03-07 12:01:07: pid 4381: FATAL: failed to bind a socket: "/tmp/.s.PGSQL.9999"
Mar 7 12:01:07 vm1 pgpool[4381]: [7-2] 2019-03-07 12:01:07: pid 4381: DETAIL: bind socket failed with error: "Address already in use"
Mar 7 12:01:07 vm1 pgpool[4381]: [8-1] 2019-03-07 12:01:07: pid 4381: WARNING: failed to open status file at: "/tmp/edb/pgpool3.5/pgpool_status"
Mar 7 12:01:07 vm1 pgpool[4381]: [8-2] 2019-03-07 12:01:07: pid 4381: DETAIL: "Permission denied"
Mar 7 12:01:45 vm1 pgpool[4414]: [6-1] 2019-03-07 12:01:45: pid 4414: FATAL: failed to bind a socket: "/tmp/.s.PGSQL.9999"
Mar 7 12:01:45 vm1 pgpool[4414]: [6-2] 2019-03-07 12:01:45: pid 4414: DETAIL: bind socket failed with error: "Address already in use"

I later removed the socket 9999 and 9898, taking backups and now again I’m getting the below error messages:


-bash-4.2$ pgpool -f /home/edb/pgpool3.5/etc/pgpool.conf -a /home/edb/pgpool3.5/etc/pool_hba.conf -F /home/edb/pgpool3.5/etc/pcp.conf -n
2019-03-07 12:17:10: pid 4879: LOG: Setting up socket for 0.0.0.0:9999
2019-03-07 12:17:10: pid 4879: LOG: Setting up socket for :::9999
2019-03-07 12:17:10: pid 4879: LOG: pgpool-II successfully started. version 3.5.5 (ekieboshi)
2019-03-07 12:17:10: pid 4879: LOG: find_primary_node: checking backend no 0
2019-03-07 12:17:10: pid 4879: LOG: find_primary_node: primary node id is 0
2019-03-07 12:17:23: pid 4890: LOG: failed to connect to PostgreSQL server on "192.168.56.202:5444", getsockopt() detected error "Connection refused"
2019-03-07 12:17:23: pid 4890: LOG: degenerate backend request for node_id: 1 from pid [4890] is canceled because failover is disallowed on the node
2019-03-07 12:17:23: pid 4890: FATAL: failed to create a backend connection
2019-03-07 12:17:23: pid 4890: DETAIL: executing failover on backend
2019-03-07 12:17:23: pid 4879: LOG: child process with pid: 4890 exits with status 256
2019-03-07 12:17:23: pid 4879: LOG: fork a new child process with pid: 4925
2019-03-07 12:17:30: pid 4925: LOG: failed to connect to PostgreSQL server on "192.168.56.202:5444", getsockopt() detected error "Connection refused"
2019-03-07 12:17:30: pid 4925: LOG: degenerate backend request for node_id: 1 from pid [4925] is canceled because failover is disallowed on the node
2019-03-07 12:17:30: pid 4925: FATAL: failed to create a backend connection
2019-03-07 12:17:30: pid 4925: DETAIL: executing failover on backend
2019-03-07 12:17:30: pid 4879: LOG: child process with pid: 4925 exits with status 256
2019-03-07 12:17:30: pid 4879: LOG: fork a new child process with pid: 4945
Steps To ReproduceServer reboot when pgPool and cluster is running.
TagsNo tags attached.

Activities

sandeepkandhway

2019-03-08 00:43

reporter   ~0002424

Also guide me which version of pgPool will be the most stable to use in PROD environment as currently SIT is going on.
DB version we're using is EDB-9.6.11.18 and EFM-3.4

pengbo

2019-03-11 11:27

developer   ~0002428

Using the latest version of each Stable branch is recommended.
You can download from below:
  https://pgpool.net/mediawiki/index.php/Downloads

Could you try the latest version of 3.5.x branch?

Issue History

Date Modified Username Field Change
2019-03-08 00:37 sandeepkandhway New Issue
2019-03-08 00:43 sandeepkandhway Note Added: 0002424
2019-03-11 11:20 administrator Assigned To => pengbo
2019-03-11 11:20 administrator Status new => assigned
2019-03-11 11:27 pengbo Note Added: 0002428
2019-04-07 23:11 pengbo Status assigned => feedback
2019-05-21 16:15 administrator Status feedback => closed