[pgpool-general: 4820] Re: Pg pool setup issues

Vaidyanathaswamy, Sai (NBCUniversal) Sai.Vaidyanathaswamy at nbcuni.com
Tue Jul 26 08:00:09 JST 2016


HI all,


I have issues creating replicated tables, any help would be greatly
appreciate.


ld00034 bin]$ udo su postgres
-bash: udo: command not found
[openplatform at ushdbld00034 bin]$  createdb -p 9999 test
createdb: could not connect to database template1: ERROR:  pgpool is not
accepting any new connections
DETAIL:  all backend nodes are down, pgpool requires at least one valid
node
HINT:  repair the backend nodes and restart pgpool
[openplatform at ushdbld00034 bin]$

4: pid 17256: LOG:  child process with pid: 17615 exits with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17615 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17616 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17616 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17616 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17617 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17617 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17617 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17618 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17618 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17618 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17619 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17619 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17619 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17620 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17620 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17620 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17621 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17621 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17621 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17622 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17622 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17622 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17623 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17623 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17623 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17624 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17624 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17624 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17625 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17625 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17625 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17626 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17626 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17626 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17627 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17627 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17627 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17628 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17628 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17628 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17629 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17629 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17629 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17630 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17630 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17630 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17631 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17631 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17631 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17632 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17632 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17632 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17633 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17633 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17633 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17634 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17634 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17634 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17635 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17635 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17635 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17636 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17636 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17636 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17637 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17637 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17637 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17638 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17638 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17638 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17639 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17639 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17639 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17640 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17640 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17640 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17641 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17641 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17641 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17642 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17642 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17642 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17643 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17643 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17643 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17644 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17644 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17644 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17645 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17645 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17645 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17646 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17646 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17646 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17647 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17647 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17647 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17648 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17648 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17648 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17649 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17649 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17649 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17650 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17650 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17650 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17651 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17651 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17651 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: DEBUG:  child process with pid: 17652 exit
with SUCCESS. child will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17652 exits
with status 0
2016-07-25 15:52:24: pid 17256: LOG:  child process with pid: 17652 exited
with success and will not be restarted
2016-07-25 15:52:24: pid 17256: LOG:  worker child process with pid: 17655
exits with status 256
2016-07-25 15:52:24: pid 17256: LOG:  fork a new worker child process with
pid: 17853
2016-07-25 15:52:24: pid 17853: DEBUG:  I am 17853
ler: exiting normally
2016-07-25 15:52:24: pid 17853: DEBUG:  initializing backend status
2016-07-25 15:52:29: pid 17256: DEBUG:  starting health check
2016-07-25 15:52:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:29: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:52:29: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:52:29: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:52:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:34: pid 17256: DEBUG:  starting health check
2016-07-25 15:52:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:34: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:52:34: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:52:34: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:52:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:39: pid 17256: DEBUG:  starting health check
2016-07-25 15:52:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:39: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:52:39: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:52:39: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:52:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:44: pid 17256: DEBUG:  starting health check
2016-07-25 15:52:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:44: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:52:44: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:52:44: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:52:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:49: pid 17256: DEBUG:  starting health check
2016-07-25 15:52:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:49: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:52:49: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:52:49: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:52:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:54: pid 17256: DEBUG:  starting health check
2016-07-25 15:52:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:54: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:52:54: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:52:54: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:52:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:59: pid 17256: DEBUG:  starting health check
2016-07-25 15:52:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:59: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:52:59: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:52:59: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:52:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:52:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:04: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:04: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:04: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:04: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:09: pid 17849: DEBUG:  reading startup packet
2016-07-25 15:53:09: pid 17849: DETAIL:  application_name: createdb
2016-07-25 15:53:09: pid 17849: DEBUG:  reading startup packet
2016-07-25 15:53:09: pid 17849: DETAIL:  Protocol Major: 3 Minor: 0
database: postgres user: openplatform
2016-07-25 15:53:09: pid 17849: DEBUG:  forwarding error message to
frontend
2016-07-25 15:53:09: pid 17849: FATAL:  pgpool is not accepting any new
connections
2016-07-25 15:53:09: pid 17849: DETAIL:  all backend nodes are down,
pgpool requires at least one valid node
2016-07-25 15:53:09: pid 17849: HINT:  repair the backend nodes and
restart pgpool
2016-07-25 15:53:09: pid 17256: DEBUG:  reaper handler
2016-07-25 15:53:09: pid 17256: LOG:  child process with pid: 17849 exits
with status 256
2016-07-25 15:53:09: pid 17256: LOG:  fork a new child process with pid:
17859
2016-07-25 15:53:09: pid 17256: DEBUG:  reaper handler: exiting normally
2016-07-25 15:53:09: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:09: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:09: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:09: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:09: pid 17848: DEBUG:  reading startup packet
2016-07-25 15:53:09: pid 17848: DETAIL:  application_name: createdb
2016-07-25 15:53:09: pid 17848: DEBUG:  reading startup packet
2016-07-25 15:53:09: pid 17848: DETAIL:  Protocol Major: 3 Minor: 0
database: template1 user: openplatform
2016-07-25 15:53:09: pid 17848: DEBUG:  forwarding error message to
frontend
2016-07-25 15:53:09: pid 17848: FATAL:  pgpool is not accepting any new
connections
2016-07-25 15:53:09: pid 17848: DETAIL:  all backend nodes are down,
pgpool requires at least one valid node
2016-07-25 15:53:09: pid 17848: HINT:  repair the backend nodes and
restart pgpool
2016-07-25 15:53:09: pid 17256: DEBUG:  reaper handler
2016-07-25 15:53:09: pid 17256: LOG:  child process with pid: 17848 exits
with status 256
2016-07-25 15:53:09: pid 17256: LOG:  fork a new child process with pid:
17860
2016-07-25 15:53:09: pid 17256: DEBUG:  reaper handler: exiting normally
2016-07-25 15:53:09: pid 17860: DEBUG:  initializing backend status
2016-07-25 15:53:14: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:14: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:14: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:14: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:19: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:19: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:19: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:19: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:24: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:24: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:24: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:24: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:29: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:29: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:29: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:29: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:34: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:34: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:34: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:34: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:39: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:39: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:39: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:39: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:44: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:44: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:44: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:44: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:49: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:49: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:49: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:49: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:54: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:54: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:54: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:54: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:59: pid 17256: DEBUG:  starting health check
2016-07-25 15:53:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:59: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:53:59: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:53:59: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:53:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:53:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:04: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:04: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:04: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:04: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:09: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:09: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:09: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:09: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:14: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:14: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:14: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:14: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:19: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:19: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:19: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:19: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:24: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:24: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:24: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:24: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:29: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:29: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:29: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:29: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:34: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:34: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:34: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:34: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:39: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:39: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:39: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:39: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:44: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:44: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:44: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:44: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:49: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:49: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:49: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:49: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:54: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:54: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:54: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:54: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:59: pid 17256: DEBUG:  starting health check
2016-07-25 15:54:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:59: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:54:59: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:54:59: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:54:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:54:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:04: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:04: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:55:04: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:04: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:09: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:09: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:55:09: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:09: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:14: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:14: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:55:14: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:14: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:19: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:19: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:55:19: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:19: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:24: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:24: pid 17256: DEBUG:  doing health check against
database:postgres user:postgres
2016-07-25 15:55:24: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:24: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:29: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:29: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:55:29: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:29: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:34: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:34: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:55:34: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:34: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:39: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:39: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:55:39: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:39: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:44: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:44: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:55:44: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:44: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:49: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:49: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:55:49: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:49: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:54: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:54: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:55:54: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:54: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:59: pid 17256: DEBUG:  starting health check
2016-07-25 15:55:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:59: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:55:59: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:55:59: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:55:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:55:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:04: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:04: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:04: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:04: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:09: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:09: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:09: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:09: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:14: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:14: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:14: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:14: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:19: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:19: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:19: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:19: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:24: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:24: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:24: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:24: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:29: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:29: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:29: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:29: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:34: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:34: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:34: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:34: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:39: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:39: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:39: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:39: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:44: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:44: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:44: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:44: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:49: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:49: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:49: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:49: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:54: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:54: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:54: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:54: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:59: pid 17256: DEBUG:  starting health check
2016-07-25 15:56:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:59: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:56:59: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:56:59: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:56:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:56:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:04: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:04: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:04: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:04: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:09: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:09: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:09: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:09: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:14: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:14: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:14: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:14: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:19: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:19: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:19: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:19: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:24: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:24: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:24: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:24: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:29: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:29: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:29: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:29: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:34: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:34: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:34: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:34: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:39: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:39: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:39: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:39: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:44: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:44: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:44: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:44: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:49: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:49: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:49: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:49: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:54: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:54: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:54: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:54: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:59: pid 17256: DEBUG:  starting health check
2016-07-25 15:57:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:59: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:57:59: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:57:59: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:57:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:57:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:04: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:04: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:04: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:04: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:09: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:09: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:09: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:09: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:14: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:14: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:14: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:14: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:19: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:19: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:19: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:19: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:19: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:24: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:24: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:24: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:24: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:24: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:29: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:29: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:29: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:29: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:29: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:34: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:34: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:34: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:34: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:34: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:39: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:39: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:39: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:39: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:39: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:44: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:44: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:44: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:44: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:44: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:49: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:49: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:49: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:49: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:49: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:54: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:54: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:54: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:54: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:54: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:59: pid 17256: DEBUG:  starting health check
2016-07-25 15:58:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:59: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:58:59: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:58:59: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:58:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:58:59: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:59:04: pid 17256: DEBUG:  starting health check
2016-07-25 15:59:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:59:04: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:59:04: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:59:04: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:59:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:59:04: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:59:09: pid 17256: DEBUG:  starting health check
2016-07-25 15:59:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:59:09: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:59:09: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:59:09: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:59:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:59:09: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:59:14: pid 17256: DEBUG:  starting health check
2016-07-25 15:59:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:59:14: pid 17256: DEBUG:  doing health check against 
database:postgres user:postgres
2016-07-25 15:59:14: pid 17256: DEBUG:  Backend DB node 0 status is 3
2016-07-25 15:59:14: pid 17256: DEBUG:  Backend DB node 1 status is 3
2016-07-25 15:59:14: pid 17256: DEBUG:  health check: clearing alarm
2016-07-25 15:59:14: pid 17256: DEBUG:  health check: clearing alarm





On 7/18/16, 5:02 PM, "Tatsuo Ishii" <ishii at postgresql.org> wrote:

>[Cc: to pgpool-hackers removed since this is not related to the list]
>
>See http://pgpool.net/mediawiki/index.php/FAQ and search "md5"
>Also see the pgpool-II manual how to set up the pgpool-II authentication.
>
>Best regards,
>--
>Tatsuo Ishii
>SRA OSS, Inc. Japan
>English: http://www.sraoss.co.jp/index_en.php
>Japanese:http://www.sraoss.co.jp
>
>From: "Vaidyanathaswamy, Sai (NBCUniversal)" 
><Sai.Vaidyanathaswamy at nbcuni.com>
>Subject: [pgpool-general: 4789] Pg pool setup issues
>Date: Mon, 18 Jul 2016 20:59:19 +0000
>Message-ID: 
><F2FB436BF14DEB4FAC67561BEA46313BB772C9 at USUSHEMWP013.mail.tfayd.com>
>
>> HI Support,
>> 
>> I am trying to implement pgpool database/creation and replication with 
>>3 different server, Master/slave and class server.
>> 
>> I am not able to create a database, I am getting the following errors . 
>>Your help is much appreciated.
>> I have changed the pg_hba.conf to the following
>> 
>> 
>> 
>> 2016-07-18 13:49:57: pid 2974: DETAIL:  Protocol Major: 3 Minor: 0 
>>database: template1 user: openplatform
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  creating new connection to 
>>backend
>> 2016-07-18 13:49:57: pid 2974: DETAIL:  connecting 0 backend
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  creating new connection to 
>>backend
>> 2016-07-18 13:49:57: pid 2974: DETAIL:  connecting 1 backend
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  creating new connection to 
>>backend
>> 2016-07-18 13:49:57: pid 2974: DETAIL:  skipping backend slot 1 because 
>>backend_status = 3
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  creating new connection to 
>>backend
>> 2016-07-18 13:49:57: pid 2974: DETAIL:  connecting 2 backend
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  SSL is requested but SSL support 
>>is not available
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  SSL is requested but SSL support 
>>is not available
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  pool_read: read 13 bytes from 
>>backend 0
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  pool_read: read 13 bytes from 
>>backend 2
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  reading message length
>> 2016-07-18 13:49:57: pid 2974: DETAIL:  slot: 0 length: 12
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  reading message length
>> 2016-07-18 13:49:57: pid 2974: DETAIL:  slot: 2 length: 12
>> 2016-07-18 13:49:57: pid 2974: DEBUG:  authentication backend
>> 2016-07-18 13:49:57: pid 2974: DETAIL:  auth kind:5
>> 2016-07-18 13:49:57: pid 2974: ERROR:  failed to authenticate with 
>>backend
>> 2016-07-18 13:49:57: pid 2974: DETAIL:  MD5 authentication is not 
>>supported in replication and master-slave modes.
>> 2016-07-18 13:49:57: pid 2974: HINT:  check pg_hba.conf settings on 
>>backend node
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> # If you want to allow non-local connections, you need to add more
>> # "host" records. In that case you will also need to make pgpool listen
>> # on a non-local interface via the listen_addresses configuration 
>>parameter.
>> # TYPE  DATABASE    USER        CIDR-ADDRESS          METHOD
>> # "local" is for Unix domain socket connections only
>> #local   all             postgres              md5
>> local   all                  all               trust
>> # IPv4 local connections:
>> host    all              postgres            127.0.0.1/32       ident
>> #host    all              all               ::1/128              md5
>> host      all             all               100.114.116.68/32    ident
>> host      all             all               100.114.116.69/32    ident
>> 
>> # Allow replication connections from localhost, by a user with the
>> # replication privilege.
>> #local   replication     postgres                                peer
>> host    replication     postgres        127.0.0.1/32            ident
>> #host    replication     postgres        ::1/128                 ident
>> host     replication     postgres       100.114.116.68/32       ident
>> host    replication     postgres        100.114.116.69/32        ident
>> 
>> 
>> 
>> Thanks !
>> sai



More information about the pgpool-general mailing list