-bash-4.1$ /usr/pgpool-9.5/bin/pgpool -d -f /etc/pgpool-II-95/pgpool.conf  -n
2016-03-23 10:45:48: pid 17468: DEBUG:  loading hba configuration
2016-03-23 10:45:48: pid 17468: DETAIL:  loading file :"/etc/pgpool-II-95/pool_hba.conf" for client authentication configuration file
2016-03-23 10:45:48: pid 17468: WARNING:  checking setuid bit of if_up_cmd
2016-03-23 10:45:48: pid 17468: DETAIL:  ifup[/data/postgresql/data/pgp_ip_addr.sh] doesn't have setuid bit
2016-03-23 10:45:48: pid 17468: WARNING:  checking setuid bit of if_down_cmd
2016-03-23 10:45:48: pid 17468: DETAIL:  ifdown[/data/postgresql/data/pgp_ip_addr.sh] doesn't have setuid bit
2016-03-23 10:45:48: pid 17468: WARNING:  checking setuid bit of arping command
2016-03-23 10:45:48: pid 17468: DETAIL:  arping[/data/postgresql/data/pgp_arping.sh] doesn't have setuid bit
2016-03-23 10:45:48: pid 17468: LOG:  reading status file: 1 th backend is set to down status
2016-03-23 10:45:48: pid 17468: DEBUG:  pool_coninfo_size: num_init_children (30) * max_pool (4) * MAX_NUM_BACKENDS (128) * sizeof(ConnectionInfo) (136) = 2088960 bytes requested for shared memory
2016-03-23 10:45:48: pid 17468: DEBUG:  ProcessInfo: num_init_children (30) * sizeof(ProcessInfo) (32) = 960 bytes requested for shared memory
2016-03-23 10:45:48: pid 17468: DEBUG:  Request info are: sizeof(POOL_REQUEST_INFO) 5224 bytes requested for shared memory
2016-03-23 10:45:48: pid 17468: DEBUG:  Recovery management area: sizeof(int) 4 bytes requested for shared memory
2016-03-23 10:45:48: pid 17468: DEBUG:  WD_Node_List: sizeof(unsigned char) (1) * MAX_NUM_BACKENDS (128) = 128 bytes requested for shared memory
2016-03-23 10:45:48: pid 17468: LOG:  waiting for watchdog to initialize
2016-03-23 10:45:48: pid 17469: LOG:  setting the local watchdog node name to "Linux_serv-ed01_9999"
2016-03-23 10:45:48: pid 17469: LOG:  watchdog cluster configured with 1 remote nodes
2016-03-23 10:45:48: pid 17469: LOG:  watchdog remote node:0 on serv-ed02:9000
2016-03-23 10:45:48: pid 17469: LOG:  interface monitoring is disabled in watchdog
2016-03-23 10:45:48: pid 17469: LOG:  IPC socket path: "/tmp/.s.PGPOOLWD_CMD.9000"
2016-03-23 10:45:48: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = STATE CHANGED Current State = LOADING
2016-03-23 10:45:48: pid 17469: DEBUG:  error in outbond connection to serv-ed02:9000
2016-03-23 10:45:48: pid 17469: DETAIL:  Connection refused
2016-03-23 10:45:52: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = LOADING
2016-03-23 10:45:52: pid 17469: LOG:  watchdog node state changed from [LOADING] to [JOINING]
2016-03-23 10:45:52: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = STATE CHANGED Current State = JOINING
2016-03-23 10:45:52: pid 17469: DEBUG:  sending packet to node "" failed, closing connection
2016-03-23 10:45:57: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = JOINING
2016-03-23 10:45:57: pid 17469: LOG:  watchdog node state changed from [JOINING] to [INITIALIZING]
2016-03-23 10:45:57: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = STATE CHANGED Current State = INITIALIZING
2016-03-23 10:45:57: pid 17469: DEBUG:  sending packet to node "" failed, closing connection
2016-03-23 10:45:58: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = INITIALIZING
2016-03-23 10:45:58: pid 17469: LOG:  I am the only alive node in the watchdog cluster
2016-03-23 10:45:58: pid 17469: HINT:  skiping stand for coordinator state
2016-03-23 10:45:58: pid 17469: LOG:  watchdog node state changed from [INITIALIZING] to [MASTER]
2016-03-23 10:45:58: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = STATE CHANGED Current State = MASTER
2016-03-23 10:45:58: pid 17469: LOG:  I am announcing my self as master/coordinator watchdog node
2016-03-23 10:45:58: pid 17469: DEBUG:  sending packet to node "" failed, closing connection
2016-03-23 10:45:59: pid 17469: DEBUG:  error in outbond connection to serv-ed02:9000
2016-03-23 10:45:59: pid 17469: DETAIL:  Connection refused
2016-03-23 10:46:03: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:46:03: pid 17469: DEBUG:  declare coordinator command finished with status:[COMMAND TIMEED OUT]
2016-03-23 10:46:03: pid 17469: DETAIL:  The command was sent to 0 nodes and 0 nodes replied to it
2016-03-23 10:46:03: pid 17469: LOG:  I am the cluster leader node
2016-03-23 10:46:03: pid 17469: DETAIL:  our declare coordinator message is accepted by all nodes
2016-03-23 10:46:03: pid 17469: LOG:  I am the cluster leader node. Starting escalation process
2016-03-23 10:46:03: pid 17469: LOG:  escalation process started with PID:17471
2016-03-23 10:46:03: pid 17468: LOG:  watchdog process is initialized
2016-03-23 10:46:03: pid 17471: LOG:  watchdog: escalation started
2016-03-23 10:46:03: pid 17472: DEBUG:  I am watchdog lifecheck child with pid:17472
2016-03-23 10:46:03: pid 17468: LOG:  Setting up socket for 0.0.0.0:9999
2016-03-23 10:46:03: pid 17468: LOG:  Setting up socket for :::9999
2016-03-23 10:46:03: pid 17469: LOG:  new IPC connection received
2016-03-23 10:46:03: pid 17472: LOG:  2 watchdog nodes are configured for lifecheck
2016-03-23 10:46:03: pid 17472: LOG:  watchdog nodes ID:0 Name:"Linux_serv-ed01_9999"
2016-03-23 10:46:03: pid 17472: DETAIL:  Host:"serv-ed01" WD Port:9000 pgpool-II port:9999
2016-03-23 10:46:03: pid 17472: LOG:  watchdog nodes ID:1 Name:"Not_Set"
2016-03-23 10:46:03: pid 17472: DETAIL:  Host:"serv-ed02" WD Port:9000 pgpool-II port:9999
2016-03-23 10:46:03: pid 17474: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17475: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17472: DEBUG:  watchdog checking life check is ready
2016-03-23 10:46:03: pid 17472: DETAIL:  pgpool:1 at "serv-ed02:9999" has not send the heartbeat signal yet
2016-03-23 10:46:03: pid 17477: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17480: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17481: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17482: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17483: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17484: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17485: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17478: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17487: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17488: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17489: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17490: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17491: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17492: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17493: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17495: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17494: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17496: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17497: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17498: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17500: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17499: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17501: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17502: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17503: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17504: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17505: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17506: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17507: DEBUG:  I am PCP child with pid:17507
2016-03-23 10:46:03: pid 17468: LOG:  pgpool-II successfully started. version 3.5.0 (ekieboshi)
2016-03-23 10:46:03: pid 17468: LOG:  find_primary_node: checking backend no 0
2016-03-23 10:46:03: pid 17508: DEBUG:  I am 17508
2016-03-23 10:46:03: pid 17508: DEBUG:  initializing backend status
2016-03-23 10:46:03: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:03: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:03: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:03: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: extended:0 query:"SELECT pg_is_in_recovery()"
2016-03-23 10:46:03: pid 17468: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:46:03: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:03: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:46:03: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:03: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:03: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:03: pid 17468: DEBUG:  pool_read: read 75 bytes from backend 0
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: kind: 'T'
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: kind: 'D'
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: kind: 'C'
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:46:03: pid 17468: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:46:03: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:03: pid 17468: LOG:  find_primary_node: primary node id is 0
2016-03-23 10:46:03: pid 17469: DEBUG:  Network event received
2016-03-23 10:46:03: pid 17469: DETAIL:  deleted = NO Link change event = NO
2016-03-23 10:46:03: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = NETWORK IP IS ASSIGNED Current State = MASTER
2016-03-23 10:46:03: pid 17471: DEBUG:  watchdog exec interface up/down command: 'pgp_ip_addr.sh add $_IP_$/24 eth0' succeeded
2016-03-23 10:46:03: pid 17471: DEBUG:  watchdog exec interface up/down command failed
2016-03-23 10:46:03: pid 17471: DETAIL:  'pgp_arping.sh -U $_IP_$ -w 1' failed. exit status: 3
2016-03-23 10:46:03: pid 17471: WARNING:  watchdog failed to bring up delegate IP, 'if_up_cmd' failed
2016-03-23 10:46:03: pid 17471: WARNING:  watchdog de-escalation failed to bring down delegate IP
2016-03-23 10:46:03: pid 17469: DEBUG:  watchdog child signal handler
2016-03-23 10:46:03: pid 17469: LOG:  watchdog escalation process with pid: 17471 exit with SUCCESS.
2016-03-23 10:46:03: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:03: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:03: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:03: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:03: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:03: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:03: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:03: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:03: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:03: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:03: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:03: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:03: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:03: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:04: pid 17476: LOG:  failed to create watchdog heartbeat receive socket.
2016-03-23 10:46:04: pid 17476: DETAIL:  setsockopt(SO_BINDTODEVICE) requies root privilege
2016-03-23 10:46:04: pid 17476: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:46:04: pid 17476: LOG:  creating watchdog heartbeat receive socket.
2016-03-23 10:46:04: pid 17476: DETAIL:  set SO_REUSEPORT
2016-03-23 10:46:04: pid 17479: LOG:  creating socket for sending heartbeat
2016-03-23 10:46:04: pid 17479: DETAIL:  setsockopt(SO_BINDTODEVICE) requires root privilege
2016-03-23 10:46:04: pid 17479: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:46:04: pid 17479: LOG:  creating socket for sending heartbeat
2016-03-23 10:46:04: pid 17479: DETAIL:  set SO_REUSEPORT
2016-03-23 10:46:04: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:05: pid 17469: LOG:  new watchdog node connection is received from "10.129.124.47:20195"
2016-03-23 10:46:05: pid 17469: DEBUG:  received packet tyep A while need packet type A
2016-03-23 10:46:05: pid 17469: DEBUG:  ADD NODE MESSAGE from Hostname:"serv-ed02" PORT:9000 pgpool_port:9999
2016-03-23 10:46:05: pid 17469: NOTICE:  New node joined the cluster Hostname:"serv-ed02" PORT:9000 pgpool_port:9999
2016-03-23 10:46:05: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:05: pid 17469: DEBUG:  sending watchdog packet Socket:7, Type:[NODE INFO], Command_ID:3, data Length:170
2016-03-23 10:46:05: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:46:05: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:06: pid 17469: DEBUG:  received packet tyep J while need packet type
2016-03-23 10:46:06: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:06: pid 17469: DEBUG:  sending watchdog packet Socket:7, Type:[ACCEPT], Command_ID:5, data Length:0
2016-03-23 10:46:06: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:46:06: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:06: pid 17469: DEBUG:  received packet tyep Y while need packet type
2016-03-23 10:46:06: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:06: pid 17469: DEBUG:  sending watchdog packet Socket:7, Type:[CONFIG DATA], Command_ID:7, data Length:958
2016-03-23 10:46:06: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:07: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:08: pid 17483: DEBUG:  I am 17483 accept fd 7
2016-03-23 10:46:08: pid 17483: DEBUG:  reading startup packet
2016-03-23 10:46:08: pid 17483: DETAIL:  Protocol Major: 1234 Minor: 5679 database:  user:
2016-03-23 10:46:08: pid 17483: DEBUG:  selecting backend connection
2016-03-23 10:46:08: pid 17483: DETAIL:  SSLRequest from client
2016-03-23 10:46:08: pid 17483: DEBUG:  reading startup packet
2016-03-23 10:46:08: pid 17483: DETAIL:  application_name: psql
2016-03-23 10:46:08: pid 17483: DEBUG:  reading startup packet
2016-03-23 10:46:08: pid 17483: DETAIL:  Protocol Major: 3 Minor: 0 database: postgres user: postgres
2016-03-23 10:46:08: pid 17483: DEBUG:  creating new connection to backend
2016-03-23 10:46:08: pid 17483: DETAIL:  connecting 0 backend
2016-03-23 10:46:08: pid 17483: DEBUG:  creating new connection to backend
2016-03-23 10:46:08: pid 17483: DETAIL:  connecting 1 backend
2016-03-23 10:46:08: pid 17483: DEBUG:  creating new connection to backend
2016-03-23 10:46:08: pid 17483: DETAIL:  skipping backend slot 1 because backend_status = 3
2016-03-23 10:46:08: pid 17483: DEBUG:  pool_read: read 331 bytes from backend 0
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  slot: 0 length: 8
2016-03-23 10:46:08: pid 17483: DEBUG:  authentication backend
2016-03-23 10:46:08: pid 17483: DETAIL:  auth kind:0
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 26
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"application_name" value:"psql"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"client_encoding" value:"UTF8"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 23
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"DateStyle" value:"ISO, MDY"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"integer_datetimes" value:"on"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 27
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"IntervalStyle" value:"postgres"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 20
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"is_superuser" value:"on"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"server_encoding" value:"UTF8"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"server_version" value:"9.5.1"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 35
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"session_authorization" value:"postgres"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 35
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"standard_conforming_strings" value:"on"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  master slot: 0 length: 26
2016-03-23 10:46:08: pid 17483: DEBUG:  process parameter status
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 name:"TimeZone" value:"Europe/Paris"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  slot: 0 length: 12
2016-03-23 10:46:08: pid 17483: DEBUG:  authentication backend
2016-03-23 10:46:08: pid 17483: DETAIL:  cp->info[i]:0x7f99567a9000 pid:17523
2016-03-23 10:46:08: pid 17483: DEBUG:  sending backend key data
2016-03-23 10:46:08: pid 17483: DETAIL:  send pid 17523 to frontend
2016-03-23 10:46:08: pid 17483: DEBUG:  selecting load balance node
2016-03-23 10:46:08: pid 17483: DETAIL:  selected backend id is 0
2016-03-23 10:46:08: pid 17483: DEBUG:  initializing session context
2016-03-23 10:46:08: pid 17483: DETAIL:  selected load balancing node: 0
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing transaction isolation. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing writing transaction. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing ignore till sync. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  reading backend data packet kind
2016-03-23 10:46:08: pid 17483: DETAIL:  master node id: 0
2016-03-23 10:46:08: pid 17483: DEBUG:  reading backend data packet kind
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:46:08: pid 17483: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:08: pid 17483: DEBUG:  processing backend response
2016-03-23 10:46:08: pid 17483: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:46:08: pid 17483: DEBUG:  processing backend response
2016-03-23 10:46:08: pid 17483: DETAIL:  Ready For Query received
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  slot: 0 length: 5
2016-03-23 10:46:08: pid 17483: DEBUG:  processing ReadyForQuery
2016-03-23 10:46:08: pid 17483: DETAIL:  transaction state '
2016-03-23 10:46:08: pid 17483: DEBUG:  processing frontend response
2016-03-23 10:46:08: pid 17483: DETAIL:  received kind 'Q'(51) from frontend
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  SimpleQuery
2016-03-23 10:46:08: pid 17483: DETAIL:  nodes reporting
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: setting skip reading from backends. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  processing frontend response
2016-03-23 10:46:08: pid 17483: DETAIL:  received kind 'X'(58) from frontend
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  Frontend terminated
2016-03-23 10:46:08: pid 17483: DETAIL:  received message kind 'X' from frontend
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  decide where to send the queries
2016-03-23 10:46:08: pid 17483: DETAIL:  destination = 3 for query= " DISCARD ALL"
2016-03-23 10:46:08: pid 17483: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:46:08: pid 17483: DEBUG:  waiting for query response
2016-03-23 10:46:08: pid 17483: DETAIL:  waiting for backend:0 to complete the query
2016-03-23 10:46:08: pid 17483: DEBUG:  pool_read: read 80 bytes from backend 0
2016-03-23 10:46:08: pid 17483: DEBUG:  detect error: kind: S
2016-03-23 10:46:08: pid 17483: DEBUG:  detect error: kind: S
2016-03-23 10:46:08: pid 17483: DEBUG:  detect error: kind: S
2016-03-23 10:46:08: pid 17483: DEBUG:  detect error: kind: S
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  reading backend data packet kind
2016-03-23 10:46:08: pid 17483: DETAIL:  master node id: 0
2016-03-23 10:46:08: pid 17483: DEBUG:  reading backend data packet kind
2016-03-23 10:46:08: pid 17483: DETAIL:  parameter name: is_superuser value: "on"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading backend data packet kind
2016-03-23 10:46:08: pid 17483: DETAIL:  parameter name: session_authorization value: "postgres"
2016-03-23 10:46:08: pid 17483: DEBUG:  reading backend data packet kind
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 of 2 kind = 'C'
2016-03-23 10:46:08: pid 17483: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:08: pid 17483: DEBUG:  processing backend response
2016-03-23 10:46:08: pid 17483: DETAIL:  received kind 'C'(43) from backend
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: setting command success. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  reading backend data packet kind
2016-03-23 10:46:08: pid 17483: DETAIL:  master node id: 0
2016-03-23 10:46:08: pid 17483: DEBUG:  reading backend data packet kind
2016-03-23 10:46:08: pid 17483: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:46:08: pid 17483: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:08: pid 17483: DEBUG:  processing backend response
2016-03-23 10:46:08: pid 17483: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:46:08: pid 17483: DEBUG:  processing backend response
2016-03-23 10:46:08: pid 17483: DETAIL:  Ready For Query received
2016-03-23 10:46:08: pid 17483: DEBUG:  reading message length
2016-03-23 10:46:08: pid 17483: DETAIL:  slot: 0 length: 5
2016-03-23 10:46:08: pid 17483: DEBUG:  processing ReadyForQuery
2016-03-23 10:46:08: pid 17483: DETAIL:  transaction state 'I'(49)
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  setting backend connection close timer
2016-03-23 10:46:08: pid 17483: DETAIL:  close time 1458726368
2016-03-23 10:46:08: pid 17483: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:08: pid 17483: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:08: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:08: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:08: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:08: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:08: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:08: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:08: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:08: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:08: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:08: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:08: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:08: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:08: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:08: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:08: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:09: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:09: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:46:09: pid 17469: DEBUG:  sending watchdog packet Socket:7, Type:[IAM COORDINATOR], Command_ID:8, data Length:0
2016-03-23 10:46:09: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:46:09: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:09: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 8
2016-03-23 10:46:09: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:46:09: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:46:09: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:46:10: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:11: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:11: pid 17469: LOG:  new outbond connection to serv-ed02:9000
2016-03-23 10:46:11: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = NEW OUTBOUND_CONNECTION Current State = MASTER
2016-03-23 10:46:11: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[ADD NODE], Command_ID:9, data Length:170
2016-03-23 10:46:12: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:13: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:13: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:13: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:46:13: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:13: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:13: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:13: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:13: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:13: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:13: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:13: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:13: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:13: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:13: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:13: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:13: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:13: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:13: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:13: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:13: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:14: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:15: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:16: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:17: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:18: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:18: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:18: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:18: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:18: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:18: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:18: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:18: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:18: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:18: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:18: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:18: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:18: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:18: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:18: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:19: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:19: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:46:19: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:10, data Length:0
2016-03-23 10:46:19: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:46:19: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:19: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 10
2016-03-23 10:46:19: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:46:19: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:46:19: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:46:20: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:21: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:22: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:23: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:23: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:23: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:46:23: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:23: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:23: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:23: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:23: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:23: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:23: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:23: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:23: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:23: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:23: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:23: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:23: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:23: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:23: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:23: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:23: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:24: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:25: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:26: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:27: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:28: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:28: pid 17507: LOG:  forked new pcp worker, pid=17577 socket=7
2016-03-23 10:46:28: pid 17577: DEBUG:  I am PCP worker child with pid:17577
2016-03-23 10:46:28: pid 17577: DEBUG:  initializing backend status
2016-03-23 10:46:28: pid 17577: DEBUG:  received PCP packet
2016-03-23 10:46:28: pid 17577: DETAIL:  PCP packet type of service 'M'
2016-03-23 10:46:28: pid 17577: DEBUG:  PCP: sending md5 salt to client
2016-03-23 10:46:28: pid 17577: DEBUG:  received PCP packet
2016-03-23 10:46:28: pid 17577: DETAIL:  PCP packet type of service 'R'
2016-03-23 10:46:28: pid 17577: DEBUG:  PCP: processing authentication request
2016-03-23 10:46:28: pid 17577: DETAIL:  authentication OK
2016-03-23 10:46:28: pid 17577: DEBUG:  received PCP packet
2016-03-23 10:46:28: pid 17577: DETAIL:  PCP packet type of service 'O'
2016-03-23 10:46:28: pid 17577: DEBUG:  PCP: processing recovery request
2016-03-23 10:46:28: pid 17577: DETAIL:  start online recovery
2016-03-23 10:46:28: pid 17577: LOG:  starting recovering node 1
2016-03-23 10:46:28: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:28: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:28: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:28: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:28: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:28: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:28: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:28: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:28: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:28: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:28: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:28: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:28: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:28: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:28: pid 17577: LOG:  executing recovery
2016-03-23 10:46:28: pid 17577: DETAIL:  starting recovery command: "SELECT pgpool_recovery('pgpool_recovery.sh', 'serv-ed02', '/data/postgresql/data', '5432')"
2016-03-23 10:46:28: pid 17577: LOG:  executing recovery
2016-03-23 10:46:28: pid 17577: DETAIL:  disabling statement_timeout
2016-03-23 10:46:28: pid 17577: DEBUG:  executing recovery, start recovery
2016-03-23 10:46:28: pid 17504: DEBUG:  I am 17504 accept fd 7
2016-03-23 10:46:28: pid 17504: DEBUG:  reading startup packet
2016-03-23 10:46:28: pid 17504: DETAIL:  Protocol Major: 1234 Minor: 5679 database:  user:
2016-03-23 10:46:28: pid 17504: DEBUG:  selecting backend connection
2016-03-23 10:46:28: pid 17504: DETAIL:  SSLRequest from client
2016-03-23 10:46:28: pid 17504: DEBUG:  reading startup packet
2016-03-23 10:46:28: pid 17504: DETAIL:  application_name: psql
2016-03-23 10:46:28: pid 17504: DEBUG:  reading startup packet
2016-03-23 10:46:28: pid 17504: DETAIL:  Protocol Major: 3 Minor: 0 database: postgres user: postgres
2016-03-23 10:46:28: pid 17504: DEBUG:  creating new connection to backend
2016-03-23 10:46:28: pid 17504: DETAIL:  connecting 0 backend
2016-03-23 10:46:28: pid 17504: DEBUG:  creating new connection to backend
2016-03-23 10:46:28: pid 17504: DETAIL:  connecting 1 backend
2016-03-23 10:46:28: pid 17504: DEBUG:  creating new connection to backend
2016-03-23 10:46:28: pid 17504: DETAIL:  skipping backend slot 1 because backend_status = 3
2016-03-23 10:46:28: pid 17504: DEBUG:  pool_read: read 331 bytes from backend 0
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  slot: 0 length: 8
2016-03-23 10:46:28: pid 17504: DEBUG:  authentication backend
2016-03-23 10:46:28: pid 17504: DETAIL:  auth kind:0
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 26
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"application_name" value:"psql"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"client_encoding" value:"UTF8"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 23
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"DateStyle" value:"ISO, MDY"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"integer_datetimes" value:"on"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 27
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"IntervalStyle" value:"postgres"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 20
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"is_superuser" value:"on"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"server_encoding" value:"UTF8"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"server_version" value:"9.5.1"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 35
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"session_authorization" value:"postgres"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 35
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"standard_conforming_strings" value:"on"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  master slot: 0 length: 26
2016-03-23 10:46:28: pid 17504: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 name:"TimeZone" value:"Europe/Paris"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  slot: 0 length: 12
2016-03-23 10:46:28: pid 17504: DEBUG:  authentication backend
2016-03-23 10:46:28: pid 17504: DETAIL:  cp->info[i]:0x7f99568fd000 pid:17585
2016-03-23 10:46:28: pid 17504: DEBUG:  sending backend key data
2016-03-23 10:46:28: pid 17504: DETAIL:  send pid 17585 to frontend
2016-03-23 10:46:28: pid 17504: DEBUG:  selecting load balance node
2016-03-23 10:46:28: pid 17504: DETAIL:  selected backend id is 0
2016-03-23 10:46:28: pid 17504: DEBUG:  initializing session context
2016-03-23 10:46:28: pid 17504: DETAIL:  selected load balancing node: 0
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing transaction isolation. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing writing transaction. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing ignore till sync. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17504: DETAIL:  master node id: 0
2016-03-23 10:46:28: pid 17504: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:46:28: pid 17504: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:28: pid 17504: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17504: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:46:28: pid 17504: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17504: DETAIL:  Ready For Query received
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  slot: 0 length: 5
2016-03-23 10:46:28: pid 17504: DEBUG:  processing ReadyForQuery
2016-03-23 10:46:28: pid 17504: DETAIL:  transaction state '
2016-03-23 10:46:28: pid 17504: DEBUG:  processing frontend response
2016-03-23 10:46:28: pid 17504: DETAIL:  received kind 'Q'(51) from frontend
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  SimpleQuery
2016-03-23 10:46:28: pid 17504: DETAIL:  nodes reporting
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: setting skip reading from backends. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  processing frontend response
2016-03-23 10:46:28: pid 17504: DETAIL:  received kind 'X'(58) from frontend
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  Frontend terminated
2016-03-23 10:46:28: pid 17504: DETAIL:  received message kind 'X' from frontend
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  decide where to send the queries
2016-03-23 10:46:28: pid 17504: DETAIL:  destination = 3 for query= " DISCARD ALL"
2016-03-23 10:46:28: pid 17504: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:46:28: pid 17504: DEBUG:  waiting for query response
2016-03-23 10:46:28: pid 17504: DETAIL:  waiting for backend:0 to complete the query
2016-03-23 10:46:28: pid 17504: DEBUG:  pool_read: read 80 bytes from backend 0
2016-03-23 10:46:28: pid 17504: DEBUG:  detect error: kind: S
2016-03-23 10:46:28: pid 17504: DEBUG:  detect error: kind: S
2016-03-23 10:46:28: pid 17504: DEBUG:  detect error: kind: S
2016-03-23 10:46:28: pid 17504: DEBUG:  detect error: kind: S
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17504: DETAIL:  master node id: 0
2016-03-23 10:46:28: pid 17504: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17504: DETAIL:  parameter name: is_superuser value: "on"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17504: DETAIL:  parameter name: session_authorization value: "postgres"
2016-03-23 10:46:28: pid 17504: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 of 2 kind = 'C'
2016-03-23 10:46:28: pid 17504: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:28: pid 17504: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17504: DETAIL:  received kind 'C'(43) from backend
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: setting command success. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17504: DETAIL:  master node id: 0
2016-03-23 10:46:28: pid 17504: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17504: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:46:28: pid 17504: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:28: pid 17504: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17504: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:46:28: pid 17504: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17504: DETAIL:  Ready For Query received
2016-03-23 10:46:28: pid 17504: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17504: DETAIL:  slot: 0 length: 5
2016-03-23 10:46:28: pid 17504: DEBUG:  processing ReadyForQuery
2016-03-23 10:46:28: pid 17504: DETAIL:  transaction state 'I'(49)
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  setting backend connection close timer
2016-03-23 10:46:28: pid 17504: DETAIL:  close time 1458726388
2016-03-23 10:46:28: pid 17504: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17504: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:28: pid 17500: DEBUG:  I am 17500 accept fd 7
2016-03-23 10:46:28: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:46:28: pid 17500: DETAIL:  Protocol Major: 1234 Minor: 5679 database:  user:
2016-03-23 10:46:28: pid 17500: DEBUG:  selecting backend connection
2016-03-23 10:46:28: pid 17500: DETAIL:  SSLRequest from client
2016-03-23 10:46:28: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:46:28: pid 17500: DETAIL:  application_name: psql
2016-03-23 10:46:28: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:46:28: pid 17500: DETAIL:  Protocol Major: 3 Minor: 0 database: postgres user: postgres
2016-03-23 10:46:28: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:46:28: pid 17500: DETAIL:  connecting 0 backend
2016-03-23 10:46:28: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:46:28: pid 17500: DETAIL:  connecting 1 backend
2016-03-23 10:46:28: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:46:28: pid 17500: DETAIL:  skipping backend slot 1 because backend_status = 3
2016-03-23 10:46:28: pid 17500: DEBUG:  pool_read: read 331 bytes from backend 0
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  slot: 0 length: 8
2016-03-23 10:46:28: pid 17500: DEBUG:  authentication backend
2016-03-23 10:46:28: pid 17500: DETAIL:  auth kind:0
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 26
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"application_name" value:"psql"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"client_encoding" value:"UTF8"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 23
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"DateStyle" value:"ISO, MDY"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"integer_datetimes" value:"on"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 27
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"IntervalStyle" value:"postgres"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 20
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"is_superuser" value:"on"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"server_encoding" value:"UTF8"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"server_version" value:"9.5.1"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 35
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"session_authorization" value:"postgres"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 35
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"standard_conforming_strings" value:"on"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  master slot: 0 length: 26
2016-03-23 10:46:28: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 name:"TimeZone" value:"Europe/Paris"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  slot: 0 length: 12
2016-03-23 10:46:28: pid 17500: DEBUG:  authentication backend
2016-03-23 10:46:28: pid 17500: DETAIL:  cp->info[i]:0x7f99568b9000 pid:17586
2016-03-23 10:46:28: pid 17500: DEBUG:  sending backend key data
2016-03-23 10:46:28: pid 17500: DETAIL:  send pid 17586 to frontend
2016-03-23 10:46:28: pid 17500: DEBUG:  selecting load balance node
2016-03-23 10:46:28: pid 17500: DETAIL:  selected backend id is 0
2016-03-23 10:46:28: pid 17500: DEBUG:  initializing session context
2016-03-23 10:46:28: pid 17500: DETAIL:  selected load balancing node: 0
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing transaction isolation. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing writing transaction. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing ignore till sync. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:46:28: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:46:28: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:28: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17500: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:46:28: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17500: DETAIL:  Ready For Query received
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  slot: 0 length: 5
2016-03-23 10:46:28: pid 17500: DEBUG:  processing ReadyForQuery
2016-03-23 10:46:28: pid 17500: DETAIL:  transaction state '
2016-03-23 10:46:28: pid 17500: DEBUG:  processing frontend response
2016-03-23 10:46:28: pid 17500: DETAIL:  received kind 'Q'(51) from frontend
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  SimpleQuery
2016-03-23 10:46:28: pid 17500: DETAIL:  nodes reporting
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: setting skip reading from backends. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  processing frontend response
2016-03-23 10:46:28: pid 17500: DETAIL:  received kind 'X'(58) from frontend
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  Frontend terminated
2016-03-23 10:46:28: pid 17500: DETAIL:  received message kind 'X' from frontend
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  decide where to send the queries
2016-03-23 10:46:28: pid 17500: DETAIL:  destination = 3 for query= " DISCARD ALL"
2016-03-23 10:46:28: pid 17500: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:46:28: pid 17500: DEBUG:  waiting for query response
2016-03-23 10:46:28: pid 17500: DETAIL:  waiting for backend:0 to complete the query
2016-03-23 10:46:28: pid 17500: DEBUG:  pool_read: read 80 bytes from backend 0
2016-03-23 10:46:28: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:46:28: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:46:28: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:46:28: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:46:28: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17500: DETAIL:  parameter name: is_superuser value: "on"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17500: DETAIL:  parameter name: session_authorization value: "postgres"
2016-03-23 10:46:28: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 of 2 kind = 'C'
2016-03-23 10:46:28: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:28: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17500: DETAIL:  received kind 'C'(43) from backend
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: setting command success. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:46:28: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:28: pid 17500: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:46:28: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:28: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17500: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:46:28: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:28: pid 17500: DETAIL:  Ready For Query received
2016-03-23 10:46:28: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:28: pid 17500: DETAIL:  slot: 0 length: 5
2016-03-23 10:46:28: pid 17500: DEBUG:  processing ReadyForQuery
2016-03-23 10:46:28: pid 17500: DETAIL:  transaction state 'I'(49)
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  setting backend connection close timer
2016-03-23 10:46:28: pid 17500: DETAIL:  close time 1458726388
2016-03-23 10:46:28: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:28: pid 17500: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:29: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:29: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:46:29: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:11, data Length:0
2016-03-23 10:46:29: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:46:29: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:29: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 11
2016-03-23 10:46:29: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:46:29: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:46:29: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:46:30: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:31: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:32: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:33: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:33: pid 17472: LOG:  watchdog: lifecheck started
2016-03-23 10:46:33: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:33: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:46:33: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:33: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:33: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:33: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:33: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:33: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:33: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:33: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:33: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:33: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:33: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:33: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:33: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:33: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:33: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:33: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:33: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:34: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:35: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:35: pid 17472: DEBUG:  watchdog executing ping
2016-03-23 10:46:35: pid 17472: DETAIL:  succeed to ping serv-ew01
2016-03-23 10:46:35: pid 17472: DEBUG:  watchdog ping
2016-03-23 10:46:35: pid 17472: DETAIL:  ping data: PING serv-ew01.adm.fr.clara.net (10.129.124.41) 56(84) bytes of data.

        --- serv-ew01.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.104/0.112/0.126/0.015 ms

2016-03-23 10:46:35: pid 17472: DEBUG:  watchdog ping
2016-03-23 10:46:35: pid 17472: DETAIL:  ping data: PING serv-ew01.adm.fr.clara.net (10.129.124.41) 56(84) bytes of data.

        --- serv-ew01.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.104/0.112/0.126/0.015 ms

2016-03-23 10:46:35: pid 17472: DEBUG:  watchdog ping
2016-03-23 10:46:35: pid 17472: DETAIL:  ping data: PING serv-ea02.adm.fr.clara.net (10.129.124.44) 56(84) bytes of data.

        --- serv-ea02.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.177/0.205/0.221/0.023 ms

2016-03-23 10:46:35: pid 17468: DEBUG:  reaper handler
2016-03-23 10:46:35: pid 17468: WARNING:  watchdog lifecheck process with pid: 17472 was terminated by segmentation fault
2016-03-23 10:46:35: pid 17468: LOG:  fork a new watchdog lifecheck process with pid: 17619
2016-03-23 10:46:35: pid 17468: DEBUG:  reaper handler: exiting normally
2016-03-23 10:46:35: pid 17619: DEBUG:  I am watchdog lifecheck child with pid:17619
2016-03-23 10:46:35: pid 17469: LOG:  new IPC connection received
2016-03-23 10:46:35: pid 17619: LOG:  2 watchdog nodes are configured for lifecheck
2016-03-23 10:46:35: pid 17619: LOG:  watchdog nodes ID:0 Name:"Linux_serv-ed01_9999"
2016-03-23 10:46:35: pid 17619: DETAIL:  Host:"serv-ed01" WD Port:9000 pgpool-II port:9999
2016-03-23 10:46:35: pid 17619: LOG:  watchdog nodes ID:1 Name:"Linux_serv-ed02_9999"
2016-03-23 10:46:35: pid 17619: DETAIL:  Host:"serv-ed02" WD Port:9000 pgpool-II port:9999
2016-03-23 10:46:35: pid 17619: DEBUG:  watchdog checking life check is ready
2016-03-23 10:46:35: pid 17619: DETAIL:  pgpool:1 at "serv-ed02:9999" has not send the heartbeat signal yet
2016-03-23 10:46:36: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:36: pid 17620: LOG:  failed to create watchdog heartbeat receive socket.
2016-03-23 10:46:36: pid 17620: DETAIL:  setsockopt(SO_BINDTODEVICE) requies root privilege
2016-03-23 10:46:36: pid 17620: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:46:36: pid 17620: LOG:  creating watchdog heartbeat receive socket.
2016-03-23 10:46:36: pid 17620: DETAIL:  set SO_REUSEPORT
2016-03-23 10:46:36: pid 17621: LOG:  creating socket for sending heartbeat
2016-03-23 10:46:36: pid 17621: DETAIL:  setsockopt(SO_BINDTODEVICE) requires root privilege
2016-03-23 10:46:36: pid 17621: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:46:36: pid 17621: LOG:  creating socket for sending heartbeat
2016-03-23 10:46:36: pid 17621: DETAIL:  set SO_REUSEPORT
2016-03-23 10:46:36: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:37: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:38: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:38: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:38: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:38: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:38: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:38: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:38: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:38: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:38: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:38: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:38: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:38: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:38: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:38: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:38: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:38: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:39: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:39: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:39: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:46:39: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:12, data Length:0
2016-03-23 10:46:39: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:46:39: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:39: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 12
2016-03-23 10:46:39: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:46:39: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:46:39: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:46:40: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:40: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:41: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:41: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:42: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:42: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:43: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:43: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:43: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:43: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:46:43: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:43: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:43: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:43: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:43: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:43: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:43: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:43: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:43: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:43: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:43: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:43: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:43: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:43: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:43: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:43: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:43: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:44: pid 17500: DEBUG:  I am 17500 accept fd 7
2016-03-23 10:46:44: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:46:44: pid 17500: DETAIL:  Protocol Major: 1234 Minor: 5679 database: all
         user: all

2016-03-23 10:46:44: pid 17500: DEBUG:  selecting backend connection
2016-03-23 10:46:44: pid 17500: DETAIL:  SSLRequest from client
2016-03-23 10:46:44: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:46:44: pid 17500: DETAIL:  application_name: psql
2016-03-23 10:46:44: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:46:44: pid 17500: DETAIL:  Protocol Major: 3 Minor: 0 database: postgres user: postgres
2016-03-23 10:46:44: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:46:44: pid 17500: DETAIL:  connecting 0 backend
2016-03-23 10:46:44: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:46:44: pid 17500: DETAIL:  connecting 1 backend
2016-03-23 10:46:44: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:46:44: pid 17500: DETAIL:  skipping backend slot 1 because backend_status = 3
2016-03-23 10:46:44: pid 17500: DEBUG:  pool_read: read 331 bytes from backend 0
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  slot: 0 length: 8
2016-03-23 10:46:44: pid 17500: DEBUG:  authentication backend
2016-03-23 10:46:44: pid 17500: DETAIL:  auth kind:0
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 26
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"application_name" value:"psql"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"client_encoding" value:"UTF8"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 23
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"DateStyle" value:"ISO, MDY"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"integer_datetimes" value:"on"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 27
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"IntervalStyle" value:"postgres"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 20
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"is_superuser" value:"on"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"server_encoding" value:"UTF8"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"server_version" value:"9.5.1"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 35
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"session_authorization" value:"postgres"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 35
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"standard_conforming_strings" value:"on"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  master slot: 0 length: 26
2016-03-23 10:46:44: pid 17500: DEBUG:  process parameter status
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 name:"TimeZone" value:"Europe/Paris"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  slot: 0 length: 12
2016-03-23 10:46:44: pid 17500: DEBUG:  authentication backend
2016-03-23 10:46:44: pid 17500: DETAIL:  cp->info[i]:0x7f99568b9000 pid:17629
2016-03-23 10:46:44: pid 17500: DEBUG:  sending backend key data
2016-03-23 10:46:44: pid 17500: DETAIL:  send pid 17629 to frontend
2016-03-23 10:46:44: pid 17500: DEBUG:  selecting load balance node
2016-03-23 10:46:44: pid 17500: DETAIL:  selected backend id is 0
2016-03-23 10:46:44: pid 17500: DEBUG:  initializing session context
2016-03-23 10:46:44: pid 17500: DETAIL:  selected load balancing node: 0
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing transaction isolation. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing writing transaction. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing ignore till sync. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:44: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:46:44: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:46:44: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:44: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:44: pid 17500: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:46:44: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:44: pid 17500: DETAIL:  Ready For Query received
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  slot: 0 length: 5
2016-03-23 10:46:44: pid 17500: DEBUG:  processing ReadyForQuery
2016-03-23 10:46:44: pid 17500: DETAIL:  transaction state '
2016-03-23 10:46:44: pid 17500: DEBUG:  processing frontend response
2016-03-23 10:46:44: pid 17500: DETAIL:  received kind 'Q'(51) from frontend
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  SimpleQuery
2016-03-23 10:46:44: pid 17500: DETAIL:  nodes reporting
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: setting skip reading from backends. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  processing frontend response
2016-03-23 10:46:44: pid 17500: DETAIL:  received kind 'X'(58) from frontend
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  Frontend terminated
2016-03-23 10:46:44: pid 17500: DETAIL:  received message kind 'X' from frontend
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  decide where to send the queries
2016-03-23 10:46:44: pid 17500: DETAIL:  destination = 3 for query= " DISCARD ALL"
2016-03-23 10:46:44: pid 17500: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:46:44: pid 17500: DEBUG:  waiting for query response
2016-03-23 10:46:44: pid 17500: DETAIL:  waiting for backend:0 to complete the query
2016-03-23 10:46:44: pid 17500: DEBUG:  pool_read: read 80 bytes from backend 0
2016-03-23 10:46:44: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:46:44: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:46:44: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:46:44: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:44: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:46:44: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:44: pid 17500: DETAIL:  parameter name: is_superuser value: "on"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:44: pid 17500: DETAIL:  parameter name: session_authorization value: "postgres"
2016-03-23 10:46:44: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 of 2 kind = 'C'
2016-03-23 10:46:44: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:44: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:44: pid 17500: DETAIL:  received kind 'C'(43) from backend
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: setting command success. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:44: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:46:44: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:46:44: pid 17500: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:46:44: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:46:44: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:44: pid 17500: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:46:44: pid 17500: DEBUG:  processing backend response
2016-03-23 10:46:44: pid 17500: DETAIL:  Ready For Query received
2016-03-23 10:46:44: pid 17500: DEBUG:  reading message length
2016-03-23 10:46:44: pid 17500: DETAIL:  slot: 0 length: 5
2016-03-23 10:46:44: pid 17500: DEBUG:  processing ReadyForQuery
2016-03-23 10:46:44: pid 17500: DETAIL:  transaction state 'I'(49)
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  setting backend connection close timer
2016-03-23 10:46:44: pid 17500: DETAIL:  close time 1458726404
2016-03-23 10:46:44: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:46:44: pid 17500: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:44: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:44: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:45: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:45: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:46: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:46: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:47: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:47: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:48: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:48: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:48: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:48: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:48: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:48: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:48: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:48: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:48: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:48: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:48: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:48: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:48: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:48: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:48: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:48: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:49: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:49: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:49: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:46:49: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:13, data Length:0
2016-03-23 10:46:49: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:46:49: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:49: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 13
2016-03-23 10:46:49: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:46:49: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:46:49: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:46:50: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:50: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:51: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:51: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:52: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:52: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:53: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:53: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:53: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:53: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:46:53: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:53: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:53: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:53: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:53: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:53: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:53: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:53: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:53: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:53: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:53: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:53: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:53: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:53: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:53: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:53: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:53: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:54: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:54: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:55: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:55: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:56: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:56: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:57: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:57: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:58: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:58: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:46:58: pid 17468: DEBUG:  starting health check
2016-03-23 10:46:58: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:58: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:46:58: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:46:58: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:46:58: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:46:58: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:46:58: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:46:58: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:46:58: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:46:58: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:46:58: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:46:58: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:58: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:46:59: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:59: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:46:59: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:46:59: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:14, data Length:0
2016-03-23 10:46:59: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:46:59: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:46:59: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 14
2016-03-23 10:46:59: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:46:59: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:46:59: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:47:00: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:00: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:01: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:01: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:02: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:02: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:03: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:03: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:03: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:03: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:47:03: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:03: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:03: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:03: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:03: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:03: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:03: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:03: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:03: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:03: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:03: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:03: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:03: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:03: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:03: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:03: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:03: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:04: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:04: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:05: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:05: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:05: pid 17619: LOG:  watchdog: lifecheck started
2016-03-23 10:47:06: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:06: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:07: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:07: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog executing ping
2016-03-23 10:47:07: pid 17619: DETAIL:  succeed to ping serv-ew01
2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:07: pid 17619: DETAIL:  ping data: PING serv-ew01.adm.fr.clara.net (10.129.124.41) 56(84) bytes of data.

        --- serv-ew01.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2000ms
        rtt min/avg/max/mdev = 0.108/0.131/0.156/0.019 ms

2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog executing ping
2016-03-23 10:47:07: pid 17619: DETAIL:  succeed to ping serv-ew02
2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:07: pid 17619: DETAIL:  ping data: PING serv-ew02.adm.fr.clara.net (10.129.124.42) 56(84) bytes of data.

        --- serv-ew02.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2000ms
        rtt min/avg/max/mdev = 0.189/0.237/0.263/0.033 ms

2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog executing ping
2016-03-23 10:47:07: pid 17619: DETAIL:  succeed to ping serv-ea01
2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:07: pid 17619: DETAIL:  ping data: PING serv-ea01.adm.fr.clara.net (10.129.124.43) 56(84) bytes of data.

        --- serv-ea01.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.180/0.200/0.228/0.025 ms

2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog executing ping
2016-03-23 10:47:07: pid 17619: DETAIL:  succeed to ping serv-ea02
2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:07: pid 17619: DETAIL:  ping data: PING serv-ea02.adm.fr.clara.net (10.129.124.44) 56(84) bytes of data.

        --- serv-ea02.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.190/0.208/0.222/0.017 ms

2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog executing ping
2016-03-23 10:47:07: pid 17619: DETAIL:  succeed to ping serv-ea03
2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:07: pid 17619: DETAIL:  ping data: PING serv-ea03.adm.fr.clara.net (10.129.124.45) 56(84) bytes of data.

        --- serv-ea03.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.197/0.211/0.230/0.018 ms

2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog life checking by heartbeat
2016-03-23 10:47:07: pid 17619: DETAIL:  checking pgpool 1 (serv-ed02:9999)
2016-03-23 10:47:07: pid 17619: DEBUG:  watchdog checking if pgpool is alive using heartbeat
2016-03-23 10:47:07: pid 17619: DETAIL:  the last heartbeat from "serv-ed02:9999" received 0 seconds ago
2016-03-23 10:47:07: pid 17619: DEBUG:  checking pgpool status by heartbeat
2016-03-23 10:47:07: pid 17619: DETAIL:  OK; status OK
2016-03-23 10:47:08: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:08: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:08: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:08: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:08: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:08: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:08: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:08: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:08: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:08: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:08: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:08: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:08: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:08: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:08: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:08: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:09: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:09: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:09: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:47:09: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:15, data Length:0
2016-03-23 10:47:09: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:47:09: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:09: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 15
2016-03-23 10:47:09: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:47:09: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:47:09: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:47:10: pid 17500: DEBUG:  I am 17500 accept fd 7
2016-03-23 10:47:10: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:47:10: pid 17500: DETAIL:  Protocol Major: 1234 Minor: 5679 database: all
         user: all

2016-03-23 10:47:10: pid 17500: DEBUG:  selecting backend connection
2016-03-23 10:47:10: pid 17500: DETAIL:  SSLRequest from client
2016-03-23 10:47:10: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:47:10: pid 17500: DETAIL:  application_name: psql
2016-03-23 10:47:10: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:47:10: pid 17500: DETAIL:  Protocol Major: 3 Minor: 0 database: postgres user: postgres
2016-03-23 10:47:10: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:47:10: pid 17500: DETAIL:  connecting 0 backend
2016-03-23 10:47:10: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:47:10: pid 17500: DETAIL:  connecting 1 backend
2016-03-23 10:47:10: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:47:10: pid 17500: DETAIL:  skipping backend slot 1 because backend_status = 3
2016-03-23 10:47:10: pid 17500: DEBUG:  pool_read: read 331 bytes from backend 0
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  slot: 0 length: 8
2016-03-23 10:47:10: pid 17500: DEBUG:  authentication backend
2016-03-23 10:47:10: pid 17500: DETAIL:  auth kind:0
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 26
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"application_name" value:"psql"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"client_encoding" value:"UTF8"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 23
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"DateStyle" value:"ISO, MDY"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"integer_datetimes" value:"on"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 27
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"IntervalStyle" value:"postgres"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 20
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"is_superuser" value:"on"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"server_encoding" value:"UTF8"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"server_version" value:"9.5.1"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 35
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"session_authorization" value:"postgres"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 35
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"standard_conforming_strings" value:"on"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  master slot: 0 length: 26
2016-03-23 10:47:10: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 name:"TimeZone" value:"Europe/Paris"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  slot: 0 length: 12
2016-03-23 10:47:10: pid 17500: DEBUG:  authentication backend
2016-03-23 10:47:10: pid 17500: DETAIL:  cp->info[i]:0x7f99568b9000 pid:17669
2016-03-23 10:47:10: pid 17500: DEBUG:  sending backend key data
2016-03-23 10:47:10: pid 17500: DETAIL:  send pid 17669 to frontend
2016-03-23 10:47:10: pid 17500: DEBUG:  selecting load balance node
2016-03-23 10:47:10: pid 17500: DETAIL:  selected backend id is 0
2016-03-23 10:47:10: pid 17500: DEBUG:  initializing session context
2016-03-23 10:47:10: pid 17500: DETAIL:  selected load balancing node: 0
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing transaction isolation. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing writing transaction. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing ignore till sync. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:10: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:47:10: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:47:10: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:47:10: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:10: pid 17500: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:47:10: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:10: pid 17500: DETAIL:  Ready For Query received
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  slot: 0 length: 5
2016-03-23 10:47:10: pid 17500: DEBUG:  processing ReadyForQuery
2016-03-23 10:47:10: pid 17500: DETAIL:  transaction state '
2016-03-23 10:47:10: pid 17500: DEBUG:  processing frontend response
2016-03-23 10:47:10: pid 17500: DETAIL:  received kind 'Q'(51) from frontend
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  SimpleQuery
2016-03-23 10:47:10: pid 17500: DETAIL:  nodes reporting
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: setting skip reading from backends. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  processing frontend response
2016-03-23 10:47:10: pid 17500: DETAIL:  received kind 'X'(58) from frontend
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  Frontend terminated
2016-03-23 10:47:10: pid 17500: DETAIL:  received message kind 'X' from frontend
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  decide where to send the queries
2016-03-23 10:47:10: pid 17500: DETAIL:  destination = 3 for query= " DISCARD ALL"
2016-03-23 10:47:10: pid 17500: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:47:10: pid 17500: DEBUG:  waiting for query response
2016-03-23 10:47:10: pid 17500: DETAIL:  waiting for backend:0 to complete the query
2016-03-23 10:47:10: pid 17500: DEBUG:  pool_read: read 80 bytes from backend 0
2016-03-23 10:47:10: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:47:10: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:47:10: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:47:10: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:10: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:47:10: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:10: pid 17500: DETAIL:  parameter name: is_superuser value: "on"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:10: pid 17500: DETAIL:  parameter name: session_authorization value: "postgres"
2016-03-23 10:47:10: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 of 2 kind = 'C'
2016-03-23 10:47:10: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:47:10: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:10: pid 17500: DETAIL:  received kind 'C'(43) from backend
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: setting command success. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:10: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:47:10: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:10: pid 17500: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:47:10: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:47:10: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:10: pid 17500: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:47:10: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:10: pid 17500: DETAIL:  Ready For Query received
2016-03-23 10:47:10: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:10: pid 17500: DETAIL:  slot: 0 length: 5
2016-03-23 10:47:10: pid 17500: DEBUG:  processing ReadyForQuery
2016-03-23 10:47:10: pid 17500: DETAIL:  transaction state 'I'(49)
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  setting backend connection close timer
2016-03-23 10:47:10: pid 17500: DETAIL:  close time 1458726430
2016-03-23 10:47:10: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:10: pid 17500: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:10: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:10: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:10: pid 17619: DEBUG:  Lifecheck child reaper handler
2016-03-23 10:47:11: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:11: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:12: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:12: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:12: pid 17619: DEBUG:  watchdog executing ping
2016-03-23 10:47:12: pid 17619: DETAIL:  succeed to ping serv-ea01
2016-03-23 10:47:12: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:12: pid 17619: DETAIL:  ping data: PING serv-ea01.adm.fr.clara.net (10.129.124.43) 56(84) bytes of data.

        --- serv-ea01.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.180/0.191/0.200/0.014 ms

2016-03-23 10:47:12: pid 17619: DEBUG:  watchdog executing ping
2016-03-23 10:47:12: pid 17619: DETAIL:  succeed to ping serv-ew02
2016-03-23 10:47:12: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:12: pid 17619: DETAIL:  ping data: PING serv-ew02.adm.fr.clara.net (10.129.124.42) 56(84) bytes of data.

        --- serv-ew02.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2002ms
        rtt min/avg/max/mdev = 0.167/0.178/0.186/0.017 ms

2016-03-23 10:47:12: pid 17619: DEBUG:  watchdog executing ping
2016-03-23 10:47:12: pid 17619: DETAIL:  succeed to ping serv-ew01
2016-03-23 10:47:12: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:12: pid 17619: DETAIL:  ping data: PING serv-ew01.adm.fr.clara.net (10.129.124.41) 56(84) bytes of data.

        --- serv-ew01.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2002ms
        rtt min/avg/max/mdev = 0.097/0.122/0.151/0.022 ms

2016-03-23 10:47:12: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:12: pid 17619: DETAIL:  ping data: PING serv-ea02.adm.fr.clara.net (10.129.124.44) 56(84) bytes of data.

        --- serv-ea02.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2002ms
        rtt min/avg/max/mdev = 0.167/0.211/0.249/0.035 ms

2016-03-23 10:47:12: pid 17619: DEBUG:  watchdog ping
2016-03-23 10:47:12: pid 17619: DETAIL:  ping data: PING serv-ea02.adm.fr.clara.net (10.129.124.44) 56(84) bytes of data.

        --- serv-ea02.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2002ms
        rtt min/avg/max/mdev = 0.167/0.211/0.249/0.035 ms

2016-03-23 10:47:12: pid 17468: DEBUG:  reaper handler
2016-03-23 10:47:12: pid 17468: WARNING:  watchdog lifecheck process with pid: 17619 was terminated by segmentation fault
2016-03-23 10:47:12: pid 17468: LOG:  fork a new watchdog lifecheck process with pid: 17682
2016-03-23 10:47:12: pid 17468: DEBUG:  reaper handler: exiting normally
2016-03-23 10:47:12: pid 17682: DEBUG:  I am watchdog lifecheck child with pid:17682
2016-03-23 10:47:12: pid 17469: LOG:  new IPC connection received
2016-03-23 10:47:12: pid 17682: LOG:  2 watchdog nodes are configured for lifecheck
2016-03-23 10:47:12: pid 17682: LOG:  watchdog nodes ID:0 Name:"Linux_serv-ed01_9999"
2016-03-23 10:47:12: pid 17682: DETAIL:  Host:"serv-ed01" WD Port:9000 pgpool-II port:9999
2016-03-23 10:47:12: pid 17682: LOG:  watchdog nodes ID:1 Name:"Linux_serv-ed02_9999"
2016-03-23 10:47:12: pid 17682: DETAIL:  Host:"serv-ed02" WD Port:9000 pgpool-II port:9999
2016-03-23 10:47:12: pid 17682: DEBUG:  watchdog checking life check is ready
2016-03-23 10:47:12: pid 17682: DETAIL:  pgpool:1 at "serv-ed02:9999" has not send the heartbeat signal yet
2016-03-23 10:47:13: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:13: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:13: pid 17683: LOG:  failed to create watchdog heartbeat receive socket.
2016-03-23 10:47:13: pid 17683: DETAIL:  setsockopt(SO_BINDTODEVICE) requies root privilege
2016-03-23 10:47:13: pid 17683: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:47:13: pid 17683: LOG:  creating watchdog heartbeat receive socket.
2016-03-23 10:47:13: pid 17683: DETAIL:  set SO_REUSEPORT
2016-03-23 10:47:13: pid 17684: LOG:  creating socket for sending heartbeat
2016-03-23 10:47:13: pid 17684: DETAIL:  setsockopt(SO_BINDTODEVICE) requires root privilege
2016-03-23 10:47:13: pid 17684: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:47:13: pid 17684: LOG:  creating socket for sending heartbeat
2016-03-23 10:47:13: pid 17684: DETAIL:  set SO_REUSEPORT
2016-03-23 10:47:13: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:13: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:13: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:47:13: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:13: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:13: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:13: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:13: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:13: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:13: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:13: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:13: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:13: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:13: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:13: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:13: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:13: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:13: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:13: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:13: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:14: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:14: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:15: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:15: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:15: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:16: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:16: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:17: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:17: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:17: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:18: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:18: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:18: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:18: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:18: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:18: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:18: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:18: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:18: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:18: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:18: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:18: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:18: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:18: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:18: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:18: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:19: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:19: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:19: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:20: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:20: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:20: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:47:20: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:16, data Length:0
2016-03-23 10:47:20: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:47:20: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:20: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 16
2016-03-23 10:47:20: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:47:20: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:47:20: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:47:21: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:21: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:21: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:22: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:22: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:23: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:23: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:23: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:23: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:23: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:47:23: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:23: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:23: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:23: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:23: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:23: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:23: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:23: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:23: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:23: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:23: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:23: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:23: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:23: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:23: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:23: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:23: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:24: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:24: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:25: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:25: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:25: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:26: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:26: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:27: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:27: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:27: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:28: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:28: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:28: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:28: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:28: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:28: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:28: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:28: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:28: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:28: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:28: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:28: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:28: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:28: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:28: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:28: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:29: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:29: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:29: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:30: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:30: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:30: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:47:30: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:17, data Length:0
2016-03-23 10:47:30: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:47:30: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:30: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 17
2016-03-23 10:47:30: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:47:30: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:47:30: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:47:31: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:31: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:31: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:32: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:32: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:33: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:33: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:33: pid 17577: DEBUG:  executing recovery, finish recovery
2016-03-23 10:47:33: pid 17577: LOG:  node recovery, 1st stage is done
2016-03-23 10:47:33: pid 17577: DEBUG:  executing remote start
2016-03-23 10:47:33: pid 17577: DETAIL:  start pgpool_remote_start
2016-03-23 10:47:33: pid 17577: DEBUG:  executing remote start
2016-03-23 10:47:33: pid 17577: DETAIL:  finish pgpool_remote_start
2016-03-23 10:47:33: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:33: pid 17577: DETAIL:  trying to connect to postmaster on hostname:serv-ed02 database:postgres user:postgres (retry 0 times)
2016-03-23 10:47:33: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:33: pid 17577: DETAIL:  failed to connect to postmaster on hostname:serv-ed02 database:postgres user:postgres
2016-03-23 10:47:33: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:33: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:33: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:47:33: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:33: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:33: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:33: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:33: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:33: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:33: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:33: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:33: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:33: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:33: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:33: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:33: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:33: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:33: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:33: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:33: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:34: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:34: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:35: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:35: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:35: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:36: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:36: pid 17577: DETAIL:  trying to connect to postmaster on hostname:serv-ed02 database:postgres user:postgres (retry 1 times)
2016-03-23 10:47:36: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:36: pid 17577: DETAIL:  failed to connect to postmaster on hostname:serv-ed02 database:postgres user:postgres
2016-03-23 10:47:36: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:36: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:37: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:37: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:37: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:38: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:38: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:38: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:38: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:38: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:38: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:38: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:38: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:38: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:38: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:38: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:38: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:38: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:38: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:38: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:38: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:39: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:39: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:39: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:39: pid 17577: DETAIL:  trying to connect to postmaster on hostname:serv-ed02 database:postgres user:postgres (retry 2 times)
2016-03-23 10:47:39: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:39: pid 17577: DETAIL:  failed to connect to postmaster on hostname:serv-ed02 database:postgres user:postgres
2016-03-23 10:47:39: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:40: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:40: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:40: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:47:40: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:18, data Length:0
2016-03-23 10:47:40: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:47:40: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:40: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 18
2016-03-23 10:47:40: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:47:40: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:47:40: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:47:41: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:41: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:41: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:42: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:42: pid 17577: DETAIL:  trying to connect to postmaster on hostname:serv-ed02 database:postgres user:postgres (retry 3 times)
2016-03-23 10:47:42: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:42: pid 17577: DETAIL:  failed to connect to postmaster on hostname:serv-ed02 database:postgres user:postgres
2016-03-23 10:47:42: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:42: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:42: pid 17682: LOG:  watchdog: lifecheck started
2016-03-23 10:47:43: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:43: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:43: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:43: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:43: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:47:43: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:43: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:43: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:43: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:43: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:43: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:43: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:43: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:43: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:43: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:43: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:43: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:43: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:43: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:43: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:43: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:43: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:44: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:44: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:44: pid 17682: DEBUG:  watchdog executing ping
2016-03-23 10:47:44: pid 17682: DETAIL:  succeed to ping serv-ew01
2016-03-23 10:47:44: pid 17682: DEBUG:  watchdog ping
2016-03-23 10:47:44: pid 17682: DETAIL:  ping data: PING serv-ew01.adm.fr.clara.net (10.129.124.41) 56(84) bytes of data.

        --- serv-ew01.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.077/0.092/0.111/0.017 ms

2016-03-23 10:47:44: pid 17682: DEBUG:  watchdog executing ping
2016-03-23 10:47:44: pid 17682: DETAIL:  succeed to ping serv-ea01
2016-03-23 10:47:44: pid 17682: DEBUG:  watchdog ping
2016-03-23 10:47:44: pid 17682: DETAIL:  ping data: PING serv-ea01.adm.fr.clara.net (10.129.124.43) 56(84) bytes of data.

        --- serv-ea01.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.181/0.256/0.323/0.061 ms

2016-03-23 10:47:44: pid 17682: DEBUG:  watchdog ping
2016-03-23 10:47:44: pid 17682: DETAIL:  ping data: PING serv-ea01.adm.fr.clara.net (10.129.124.43) 56(84) bytes of data.

        --- serv-ea01.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.181/0.256/0.323/0.061 ms

2016-03-23 10:47:44: pid 17468: DEBUG:  reaper handler
2016-03-23 10:47:44: pid 17468: WARNING:  watchdog lifecheck process with pid: 17682 was terminated by segmentation fault
2016-03-23 10:47:44: pid 17468: LOG:  fork a new watchdog lifecheck process with pid: 17731
2016-03-23 10:47:44: pid 17468: DEBUG:  reaper handler: exiting normally
2016-03-23 10:47:44: pid 17731: DEBUG:  I am watchdog lifecheck child with pid:17731
2016-03-23 10:47:44: pid 17469: LOG:  new IPC connection received
2016-03-23 10:47:44: pid 17731: LOG:  2 watchdog nodes are configured for lifecheck
2016-03-23 10:47:44: pid 17731: LOG:  watchdog nodes ID:0 Name:"Linux_serv-ed01_9999"
2016-03-23 10:47:44: pid 17731: DETAIL:  Host:"serv-ed01" WD Port:9000 pgpool-II port:9999
2016-03-23 10:47:44: pid 17731: LOG:  watchdog nodes ID:1 Name:"Linux_serv-ed02_9999"
2016-03-23 10:47:44: pid 17731: DETAIL:  Host:"serv-ed02" WD Port:9000 pgpool-II port:9999
2016-03-23 10:47:44: pid 17731: DEBUG:  watchdog checking life check is ready
2016-03-23 10:47:44: pid 17731: DETAIL:  pgpool:1 at "serv-ed02:9999" has not send the heartbeat signal yet
2016-03-23 10:47:45: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:45: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:45: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:45: pid 17577: DETAIL:  trying to connect to postmaster on hostname:serv-ed02 database:template1 user:postgres (retry 0 times)
2016-03-23 10:47:45: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:45: pid 17577: DETAIL:  failed to connect to postmaster on hostname:serv-ed02 database:template1 user:postgres
2016-03-23 10:47:45: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:45: pid 17732: LOG:  failed to create watchdog heartbeat receive socket.
2016-03-23 10:47:45: pid 17732: DETAIL:  setsockopt(SO_BINDTODEVICE) requies root privilege
2016-03-23 10:47:45: pid 17732: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:47:45: pid 17732: LOG:  creating watchdog heartbeat receive socket.
2016-03-23 10:47:45: pid 17732: DETAIL:  set SO_REUSEPORT
2016-03-23 10:47:45: pid 17733: LOG:  creating socket for sending heartbeat
2016-03-23 10:47:45: pid 17733: DETAIL:  setsockopt(SO_BINDTODEVICE) requires root privilege
2016-03-23 10:47:45: pid 17733: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:47:45: pid 17733: LOG:  creating socket for sending heartbeat
2016-03-23 10:47:45: pid 17733: DETAIL:  set SO_REUSEPORT
2016-03-23 10:47:45: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:46: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:46: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:47: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:47: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:47: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:47: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:48: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:48: pid 17577: DETAIL:  trying to connect to postmaster on hostname:serv-ed02 database:template1 user:postgres (retry 1 times)
2016-03-23 10:47:48: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:48: pid 17577: DETAIL:  failed to connect to postmaster on hostname:serv-ed02 database:template1 user:postgres
2016-03-23 10:47:48: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:48: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:48: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:48: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:48: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:48: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:48: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:48: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:48: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:48: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:48: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:48: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:48: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:48: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:48: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:48: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:49: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:49: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:49: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:49: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:50: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:50: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:51: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:51: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:51: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:51: pid 17577: DETAIL:  trying to connect to postmaster on hostname:serv-ed02 database:template1 user:postgres (retry 2 times)
2016-03-23 10:47:51: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:51: pid 17577: DETAIL:  failed to connect to postmaster on hostname:serv-ed02 database:template1 user:postgres
2016-03-23 10:47:51: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:51: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:51: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:47:51: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:19, data Length:0
2016-03-23 10:47:51: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:47:51: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:51: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 19
2016-03-23 10:47:51: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:47:51: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:47:51: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:47:52: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:52: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:53: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:53: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:53: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:53: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:53: pid 17508: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:53: pid 17508: DEBUG:  authenticate kind = 0
2016-03-23 10:47:53: pid 17508: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:53: pid 17508: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:53: pid 17508: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:53: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:53: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:53: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:53: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:53: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:53: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:53: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:53: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:53: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:53: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:53: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:53: pid 17468: DEBUG:  Backend DB node 1 status is 3
2016-03-23 10:47:53: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:53: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:54: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:54: pid 17577: DETAIL:  trying to connect to postmaster on hostname:serv-ed02 database:template1 user:postgres (retry 3 times)
2016-03-23 10:47:54: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:54: pid 17577: DETAIL:  failed to connect to postmaster on hostname:serv-ed02 database:template1 user:postgres
2016-03-23 10:47:54: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:54: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:55: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:55: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:55: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:55: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:56: pid 17500: DEBUG:  I am 17500 accept fd 7
2016-03-23 10:47:56: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:47:56: pid 17500: DETAIL:  Protocol Major: 1234 Minor: 5679 database: all
         user: all

2016-03-23 10:47:56: pid 17500: DEBUG:  selecting backend connection
2016-03-23 10:47:56: pid 17500: DETAIL:  SSLRequest from client
2016-03-23 10:47:56: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:47:56: pid 17500: DETAIL:  application_name: psql
2016-03-23 10:47:56: pid 17500: DEBUG:  reading startup packet
2016-03-23 10:47:56: pid 17500: DETAIL:  Protocol Major: 3 Minor: 0 database: postgres user: postgres
2016-03-23 10:47:56: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:47:56: pid 17500: DETAIL:  connecting 0 backend
2016-03-23 10:47:56: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:47:56: pid 17500: DETAIL:  connecting 1 backend
2016-03-23 10:47:56: pid 17500: DEBUG:  creating new connection to backend
2016-03-23 10:47:56: pid 17500: DETAIL:  skipping backend slot 1 because backend_status = 3
2016-03-23 10:47:56: pid 17500: DEBUG:  pool_read: read 331 bytes from backend 0
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  slot: 0 length: 8
2016-03-23 10:47:56: pid 17500: DEBUG:  authentication backend
2016-03-23 10:47:56: pid 17500: DETAIL:  auth kind:0
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 26
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"application_name" value:"psql"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"client_encoding" value:"UTF8"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 23
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"DateStyle" value:"ISO, MDY"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"integer_datetimes" value:"on"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 27
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"IntervalStyle" value:"postgres"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 20
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"is_superuser" value:"on"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"server_encoding" value:"UTF8"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 25
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"server_version" value:"9.5.1"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 35
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"session_authorization" value:"postgres"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 35
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"standard_conforming_strings" value:"on"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  master slot: 0 length: 26
2016-03-23 10:47:56: pid 17500: DEBUG:  process parameter status
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 name:"TimeZone" value:"Europe/Paris"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  slot: 0 length: 12
2016-03-23 10:47:56: pid 17500: DEBUG:  authentication backend
2016-03-23 10:47:56: pid 17500: DETAIL:  cp->info[i]:0x7f99568b9000 pid:17760
2016-03-23 10:47:56: pid 17500: DEBUG:  sending backend key data
2016-03-23 10:47:56: pid 17500: DETAIL:  send pid 17760 to frontend
2016-03-23 10:47:56: pid 17500: DEBUG:  selecting load balance node
2016-03-23 10:47:56: pid 17500: DETAIL:  selected backend id is 0
2016-03-23 10:47:56: pid 17500: DEBUG:  initializing session context
2016-03-23 10:47:56: pid 17500: DETAIL:  selected load balancing node: 0
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing transaction isolation. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing writing transaction. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing failed transaction. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing ignore till sync. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:56: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:47:56: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:47:56: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:47:56: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:56: pid 17500: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:47:56: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:56: pid 17500: DETAIL:  Ready For Query received
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  slot: 0 length: 5
2016-03-23 10:47:56: pid 17500: DEBUG:  processing ReadyForQuery
2016-03-23 10:47:56: pid 17500: DETAIL:  transaction state '
2016-03-23 10:47:56: pid 17500: DEBUG:  processing frontend response
2016-03-23 10:47:56: pid 17500: DETAIL:  received kind 'Q'(51) from frontend
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  SimpleQuery
2016-03-23 10:47:56: pid 17500: DETAIL:  nodes reporting
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: setting skip reading from backends. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  processing frontend response
2016-03-23 10:47:56: pid 17500: DETAIL:  received kind 'X'(58) from frontend
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  Frontend terminated
2016-03-23 10:47:56: pid 17500: DETAIL:  received message kind 'X' from frontend
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: setting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  decide where to send the queries
2016-03-23 10:47:56: pid 17500: DETAIL:  destination = 3 for query= " DISCARD ALL"
2016-03-23 10:47:56: pid 17500: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:47:56: pid 17500: DEBUG:  waiting for query response
2016-03-23 10:47:56: pid 17500: DETAIL:  waiting for backend:0 to complete the query
2016-03-23 10:47:56: pid 17500: DEBUG:  pool_read: read 80 bytes from backend 0
2016-03-23 10:47:56: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:47:56: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:47:56: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:47:56: pid 17500: DEBUG:  detect error: kind: S
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing skip reading from backends. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:56: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:47:56: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:56: pid 17500: DETAIL:  parameter name: is_superuser value: "on"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:56: pid 17500: DETAIL:  parameter name: session_authorization value: "postgres"
2016-03-23 10:47:56: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 of 2 kind = 'C'
2016-03-23 10:47:56: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:47:56: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:56: pid 17500: DETAIL:  received kind 'C'(43) from backend
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: setting command success. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:56: pid 17500: DETAIL:  master node id: 0
2016-03-23 10:47:56: pid 17500: DEBUG:  reading backend data packet kind
2016-03-23 10:47:56: pid 17500: DETAIL:  backend:0 of 2 kind = 'Z'
2016-03-23 10:47:56: pid 17500: DEBUG:  read_kind_from_backend max_count:1.000000 num_executed_nodes:1
2016-03-23 10:47:56: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:56: pid 17500: DETAIL:  received kind 'Z'(5a) from backend
2016-03-23 10:47:56: pid 17500: DEBUG:  processing backend response
2016-03-23 10:47:56: pid 17500: DETAIL:  Ready For Query received
2016-03-23 10:47:56: pid 17500: DEBUG:  reading message length
2016-03-23 10:47:56: pid 17500: DETAIL:  slot: 0 length: 5
2016-03-23 10:47:56: pid 17500: DEBUG:  processing ReadyForQuery
2016-03-23 10:47:56: pid 17500: DETAIL:  transaction state 'I'(49)
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: clearing doing extended query messaging. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  setting backend connection close timer
2016-03-23 10:47:56: pid 17500: DETAIL:  close time 1458726476
2016-03-23 10:47:56: pid 17500: DEBUG:  session context: unsetting query in progress. DONE
2016-03-23 10:47:56: pid 17500: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:56: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:56: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:57: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:57: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:57: pid 17577: LOG:  checking if postmaster is started
2016-03-23 10:47:57: pid 17577: DETAIL:  trying to connect to postmaster on hostname:serv-ed02 database:template1 user:postgres (retry 4 times)
2016-03-23 10:47:57: pid 17577: LOG:  node recovery, node: 1 restarted
2016-03-23 10:47:57: pid 17577: LOG:  received failback request for node_id: 1 from pid [17577]
2016-03-23 10:47:57: pid 17469: LOG:  new IPC connection received
2016-03-23 10:47:57: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[REPLICATE VARIABLE REQUEST], Command_ID:20, data Length:88
2016-03-23 10:47:57: pid 17469: DEBUG:  received packet tyep G while need packet type
2016-03-23 10:47:57: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:57: pid 17469: DEBUG:  watchdog node "Linux_serv-ed02_9999" has replied for pgpool-II replicate command packet
2016-03-23 10:47:57: pid 17577: DEBUG:  sending 10 to the parent process with PID:17468
2016-03-23 10:47:57: pid 17468: DEBUG:  failover handler called
2016-03-23 10:47:57: pid 17468: DEBUG:  failover handler
2016-03-23 10:47:57: pid 17468: DETAIL:  starting to select new master node
2016-03-23 10:47:57: pid 17468: LOG:  starting fail back. reconnect host serv-ed02(5432)
2016-03-23 10:47:57: pid 17469: LOG:  new IPC connection received
2016-03-23 10:47:57: pid 17469: LOG:  processing sync request from IPC socket
2016-03-23 10:47:57: pid 17469: LOG:  watchdog node "Linux_serv-ed01_9999" is requesting to aquire lock for failover command start
2016-03-23 10:47:57: pid 17469: LOG:  watchdog node "Linux_serv-ed01_9999" is requesting to aquire lock for failover command start
2016-03-23 10:47:57: pid 17469: LOG:  new IPC connection received
2016-03-23 10:47:57: pid 17469: LOG:  processing sync request from IPC socket
2016-03-23 10:47:57: pid 17469: LOG:  watchdog node "Linux_serv-ed01_9999" is requesting to release lock for failover command start
2016-03-23 10:47:57: pid 17468: LOG:  Do not restart children because we are failbacking node id 1 hostserv-ed02 port:5432 and we are in streaming replication mode
2016-03-23 10:47:57: pid 17469: LOG:  new IPC connection received
2016-03-23 10:47:57: pid 17469: LOG:  processing sync request from IPC socket
2016-03-23 10:47:57: pid 17469: LOG:  watchdog node "Linux_serv-ed01_9999" is requesting to aquire lock for failover command start
2016-03-23 10:47:57: pid 17469: LOG:  watchdog node "Linux_serv-ed01_9999" is requesting to aquire lock for failover command start
2016-03-23 10:47:57: pid 17468: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2016-03-23 10:47:57: pid 17468: LOG:  find_primary_node: checking backend no 0
2016-03-23 10:47:57: pid 17469: DEBUG:  received packet tyep s while need packet type
2016-03-23 10:47:57: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:57: pid 17469: LOG:  watchdog node "Linux_serv-ed02_9999" is requesting to aquire lock for failover command start
2016-03-23 10:47:57: pid 17469: LOG:  aquire lock for failover command start request is denied to node "Linux_serv-ed02_9999"
2016-03-23 10:47:57: pid 17469: DETAIL:  node "Linux_serv-ed01_9999" is holding the lock
2016-03-23 10:47:57: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[DATA], Command_ID:8, data Length:45
2016-03-23 10:47:57: pid 17469: DEBUG:  received packet tyep s while need packet type
2016-03-23 10:47:57: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:57: pid 17469: LOG:  watchdog node "Linux_serv-ed02_9999" is requesting to check lock for failover command start
2016-03-23 10:47:57: pid 17469: LOG:  check lock for failover command start request is denied to node "Linux_serv-ed02_9999"
2016-03-23 10:47:57: pid 17469: DETAIL:  node "Linux_serv-ed01_9999" is holding the lock
2016-03-23 10:47:57: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[DATA], Command_ID:9, data Length:45
2016-03-23 10:47:57: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:57: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:57: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:57: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: extended:0 query:"SELECT pg_is_in_recovery()"
2016-03-23 10:47:57: pid 17468: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:47:57: pid 17468: DEBUG:  pool_read: read 75 bytes from backend 0
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: kind: 'T'
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: kind: 'D'
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: kind: 'C'
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:47:57: pid 17468: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:47:57: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:57: pid 17468: LOG:  find_primary_node: primary node id is 0
2016-03-23 10:47:57: pid 17468: LOG:  failover: set new primary node: 0
2016-03-23 10:47:57: pid 17468: LOG:  failover: set new master node: 0
2016-03-23 10:47:57: pid 17469: LOG:  new IPC connection received
2016-03-23 10:47:57: pid 17508: LOG:  worker process received restart request
2016-03-23 10:47:57: pid 17469: LOG:  processing sync request from IPC socket
2016-03-23 10:47:57: pid 17469: LOG:  watchdog node "Linux_serv-ed01_9999" is requesting to check lock for failover command start
2016-03-23 10:47:57: pid 17468: LOG:  failback done. reconnect host serv-ed02(5432)
2016-03-23 10:47:57: pid 17577: LOG:  recovery done
2016-03-23 10:47:57: pid 17577: DEBUG:  sending 12 to the parent process with PID:17468
2016-03-23 10:47:57: pid 17577: DEBUG:  received PCP packet
2016-03-23 10:47:57: pid 17577: DETAIL:  PCP packet type of service 'X'
2016-03-23 10:47:57: pid 17577: DEBUG:  PCP processing request, client disconnecting
2016-03-23 10:47:57: pid 17577: DETAIL:  closing PCP connection, and exiting child
2016-03-23 10:47:57: pid 17507: DEBUG:  PCP child reaper handler
2016-03-23 10:47:57: pid 17507: LOG:  PCP process with pid: 17577 exit with SUCCESS.
2016-03-23 10:47:57: pid 17507: LOG:  PCP process with pid: 17577 exits with status 0
2016-03-23 10:47:57: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:57: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:58: pid 17469: DEBUG:  received packet tyep s while need packet type
2016-03-23 10:47:58: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:58: pid 17469: LOG:  watchdog node "Linux_serv-ed02_9999" is requesting to check lock for failover command start
2016-03-23 10:47:58: pid 17469: LOG:  watchdog node "Linux_serv-ed02_9999" is requesting to check lock for failover command start
2016-03-23 10:47:58: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[DATA], Command_ID:10, data Length:45
2016-03-23 10:47:58: pid 17469: DEBUG:  received packet tyep s while need packet type
2016-03-23 10:47:58: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:58: pid 17469: LOG:  watchdog node "Linux_serv-ed02_9999" is requesting to aquire lock for failover command start
2016-03-23 10:47:58: pid 17469: LOG:  watchdog node "Linux_serv-ed02_9999" is requesting to aquire lock for failover command start
2016-03-23 10:47:58: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[DATA], Command_ID:11, data Length:45
2016-03-23 10:47:58: pid 17469: DEBUG:  received packet tyep s while need packet type
2016-03-23 10:47:58: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:47:58: pid 17469: LOG:  watchdog node "Linux_serv-ed02_9999" is requesting to check lock for failover command start
2016-03-23 10:47:58: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[DATA], Command_ID:12, data Length:45
2016-03-23 10:47:58: pid 17507: LOG:  restart request received in pcp child process
2016-03-23 10:47:58: pid 17507: DEBUG:  PCP child receives shutdown request signal 15, Forwarding to all children
2016-03-23 10:47:58: pid 17507: DEBUG:  PCP child receives smart shutdown request
2016-03-23 10:47:58: pid 17468: LOG:  PCP child 17507 exits with status 0 in failover()
2016-03-23 10:47:58: pid 17468: LOG:  fork a new PCP child pid 17774 in failover()
2016-03-23 10:47:58: pid 17774: DEBUG:  I am PCP child with pid:17774
2016-03-23 10:47:58: pid 17468: DEBUG:  reaper handler
2016-03-23 10:47:58: pid 17468: LOG:  worker child process with pid: 17508 exits with status 256
2016-03-23 10:47:58: pid 17506: LOG:  failback event detected
2016-03-23 10:47:58: pid 17506: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17498: LOG:  failback event detected
2016-03-23 10:47:58: pid 17498: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17468: LOG:  fork a new worker child process with pid: 17775
2016-03-23 10:47:58: pid 17468: DEBUG:  reaper handler: exiting normally
2016-03-23 10:47:58: pid 17468: DEBUG:  starting health check
2016-03-23 10:47:58: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:58: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:47:58: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:47:58: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:47:58: pid 17775: DEBUG:  I am 17775
2016-03-23 10:47:58: pid 17775: DEBUG:  initializing backend status
2016-03-23 10:47:58: pid 17474: LOG:  failback event detected
2016-03-23 10:47:58: pid 17474: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17497: LOG:  failback event detected
2016-03-23 10:47:58: pid 17497: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17505: LOG:  failback event detected
2016-03-23 10:47:58: pid 17505: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17490: LOG:  failback event detected
2016-03-23 10:47:58: pid 17490: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17475: LOG:  failback event detected
2016-03-23 10:47:58: pid 17475: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17496: LOG:  failback event detected
2016-03-23 10:47:58: pid 17496: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17504: LOG:  failback event detected
2016-03-23 10:47:58: pid 17504: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17489: LOG:  failback event detected
2016-03-23 10:47:58: pid 17489: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17477: LOG:  failback event detected
2016-03-23 10:47:58: pid 17477: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17495: LOG:  failback event detected
2016-03-23 10:47:58: pid 17495: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17503: LOG:  failback event detected
2016-03-23 10:47:58: pid 17503: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17478: LOG:  failback event detected
2016-03-23 10:47:58: pid 17478: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17494: LOG:  failback event detected
2016-03-23 10:47:58: pid 17494: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17502: LOG:  failback event detected
2016-03-23 10:47:58: pid 17502: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17493: LOG:  failback event detected
2016-03-23 10:47:58: pid 17493: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17501: LOG:  failback event detected
2016-03-23 10:47:58: pid 17501: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17480: LOG:  failback event detected
2016-03-23 10:47:58: pid 17480: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17492: LOG:  failback event detected
2016-03-23 10:47:58: pid 17492: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17500: LOG:  failback event detected
2016-03-23 10:47:58: pid 17500: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17481: LOG:  failback event detected
2016-03-23 10:47:58: pid 17481: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17491: LOG:  failback event detected
2016-03-23 10:47:58: pid 17491: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17499: LOG:  failback event detected
2016-03-23 10:47:58: pid 17499: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17482: LOG:  failback event detected
2016-03-23 10:47:58: pid 17482: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17488: LOG:  failback event detected
2016-03-23 10:47:58: pid 17488: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17485: LOG:  failback event detected
2016-03-23 10:47:58: pid 17485: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17483: LOG:  failback event detected
2016-03-23 10:47:58: pid 17483: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17487: LOG:  failback event detected
2016-03-23 10:47:58: pid 17487: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17484: LOG:  failback event detected
2016-03-23 10:47:58: pid 17484: DETAIL:  restarting myself
2016-03-23 10:47:58: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:58: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:47:58: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:58: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:58: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:58: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:58: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:58: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:58: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:47:58: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:58: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:47:58: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:47:58: pid 17468: LOG:  connect_inet_domain_socket: select() interrupted by certain signal. retrying...
2016-03-23 10:47:58: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:58: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:47:58: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:58: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_current_xlog_location()"
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:47:58: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:47:58: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:47:58: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:47:58: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:47:58: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:58: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:58: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:47:58: pid 17468: DEBUG:  reaper handler
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17474 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17474 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17475 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17475 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17477 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17477 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17478 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17478 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17480 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17480 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17481 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17481 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17482 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17482 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17483 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17483 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17484 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17484 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17485 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17485 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17487 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17487 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17488 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17488 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17489 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17489 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17490 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17490 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17491 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17491 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17492 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17492 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17493 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17493 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17494 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17494 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17495 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17495 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17496 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17496 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17497 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17497 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17498 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17498 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17499 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17499 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17500 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17500 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17501 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17501 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17502 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17502 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17503 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17503 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17504 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17504 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17505 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17505 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17506 exits with status 256
2016-03-23 10:47:58: pid 17468: LOG:  child process with pid: 17506 exited with success and will not be restarted
2016-03-23 10:47:58: pid 17468: DEBUG:  reaper handler: exiting normally
2016-03-23 10:47:58: pid 17775: DEBUG:  pool_read: read 91 bytes from backend 0
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_last_xlog_replay_location()"
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  pool_read: read 95 bytes from backend 0
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:47:58: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:47:58: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:58: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:47:58: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:58: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:59: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:59: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:47:59: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:47:59: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:00: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:00: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:01: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:01: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:01: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:01: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:02: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:48:02: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:21, data Length:0
2016-03-23 10:48:02: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:48:02: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:48:02: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 21
2016-03-23 10:48:02: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:48:02: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:48:02: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:48:02: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:02: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:03: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:03: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:03: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:03: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:03: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:03: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:03: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:03: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:03: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:03: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:03: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:03: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:03: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:03: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:03: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:03: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:03: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:03: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:03: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:03: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:03: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:03: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:03: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:03: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:03: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:04: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:04: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:05: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:05: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:05: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:05: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:06: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:06: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:06: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:07: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:07: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:07: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:07: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:08: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:08: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:08: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:08: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:08: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:08: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:08: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:08: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:08: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_current_xlog_location()"
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  pool_read: read 91 bytes from backend 0
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_last_xlog_replay_location()"
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  pool_read: read 95 bytes from backend 0
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:08: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:08: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:08: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:08: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:08: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:08: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:08: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:08: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:08: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:08: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:08: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:08: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:08: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:08: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:08: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:08: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:08: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:08: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:08: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:08: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:08: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:08: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:08: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:08: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:08: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:08: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:09: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:09: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:09: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:09: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:10: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:10: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:10: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:11: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:11: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:11: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:11: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:12: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:48:12: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:22, data Length:0
2016-03-23 10:48:12: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:48:12: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:48:12: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 22
2016-03-23 10:48:12: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:48:12: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:48:12: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:48:12: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:12: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:12: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:13: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:13: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:13: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:13: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:13: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:13: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:13: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:13: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:13: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:13: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:13: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:13: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:13: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:13: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:13: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:13: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:13: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:13: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:13: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:13: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:13: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:13: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:13: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:13: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:13: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:14: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:14: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:14: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:14: pid 17731: LOG:  watchdog: lifecheck started
2016-03-23 10:48:15: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:15: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:15: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:15: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:16: pid 17476: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:16: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:16: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:16: pid 17731: DEBUG:  watchdog executing ping
2016-03-23 10:48:16: pid 17731: DETAIL:  succeed to ping serv-ew02
2016-03-23 10:48:16: pid 17731: DEBUG:  watchdog ping
2016-03-23 10:48:16: pid 17731: DETAIL:  ping data: PING serv-ew02.adm.fr.clara.net (10.129.124.42) 56(84) bytes of data.

        --- serv-ew02.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.188/0.232/0.263/0.031 ms

2016-03-23 10:48:16: pid 17731: DEBUG:  watchdog executing ping
2016-03-23 10:48:16: pid 17731: DETAIL:  succeed to ping serv-ea02
2016-03-23 10:48:16: pid 17731: DEBUG:  watchdog ping
2016-03-23 10:48:16: pid 17731: DETAIL:  ping data: PING serv-ea02.adm.fr.clara.net (10.129.124.44) 56(84) bytes of data.

        --- serv-ea02.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.196/0.197/0.198/0.000 ms

2016-03-23 10:48:16: pid 17731: DEBUG:  watchdog ping
2016-03-23 10:48:16: pid 17731: DETAIL:  ping data: PING serv-ea02.adm.fr.clara.net (10.129.124.44) 56(84) bytes of data.

        --- serv-ea02.adm.fr.clara.net ping statistics ---
        3 packets transmitted, 3 received, 0% packet loss, time 2001ms
        rtt min/avg/max/mdev = 0.196/0.197/0.198/0.000 ms

2016-03-23 10:48:16: pid 17468: DEBUG:  reaper handler
2016-03-23 10:48:16: pid 17468: WARNING:  watchdog lifecheck process with pid: 17731 was terminated by segmentation fault
2016-03-23 10:48:16: pid 17468: LOG:  fork a new watchdog lifecheck process with pid: 17799
2016-03-23 10:48:16: pid 17468: DEBUG:  reaper handler: exiting normally
2016-03-23 10:48:16: pid 17799: DEBUG:  I am watchdog lifecheck child with pid:17799
2016-03-23 10:48:16: pid 17469: LOG:  new IPC connection received
2016-03-23 10:48:16: pid 17799: LOG:  2 watchdog nodes are configured for lifecheck
2016-03-23 10:48:16: pid 17799: LOG:  watchdog nodes ID:0 Name:"Linux_serv-ed01_9999"
2016-03-23 10:48:16: pid 17799: DETAIL:  Host:"serv-ed01" WD Port:9000 pgpool-II port:9999
2016-03-23 10:48:16: pid 17799: LOG:  watchdog nodes ID:1 Name:"Linux_serv-ed02_9999"
2016-03-23 10:48:16: pid 17799: DETAIL:  Host:"serv-ed02" WD Port:9000 pgpool-II port:9999
2016-03-23 10:48:16: pid 17799: DEBUG:  watchdog checking life check is ready
2016-03-23 10:48:16: pid 17799: DETAIL:  pgpool:1 at "serv-ed02:9999" has not send the heartbeat signal yet
2016-03-23 10:48:17: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:17: pid 17732: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:17: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:17: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:17: pid 17800: LOG:  failed to create watchdog heartbeat receive socket.
2016-03-23 10:48:17: pid 17800: DETAIL:  setsockopt(SO_BINDTODEVICE) requies root privilege
2016-03-23 10:48:17: pid 17800: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:48:17: pid 17800: LOG:  creating watchdog heartbeat receive socket.
2016-03-23 10:48:17: pid 17800: DETAIL:  set SO_REUSEPORT
2016-03-23 10:48:17: pid 17801: LOG:  creating socket for sending heartbeat
2016-03-23 10:48:17: pid 17801: DETAIL:  setsockopt(SO_BINDTODEVICE) requires root privilege
2016-03-23 10:48:17: pid 17801: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:48:17: pid 17801: LOG:  creating socket for sending heartbeat
2016-03-23 10:48:17: pid 17801: DETAIL:  set SO_REUSEPORT
2016-03-23 10:48:17: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:18: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:18: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:18: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:18: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:18: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:18: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:18: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:18: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:18: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_current_xlog_location()"
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  pool_read: read 91 bytes from backend 0
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_last_xlog_replay_location()"
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  pool_read: read 95 bytes from backend 0
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:18: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:18: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:18: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:18: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:18: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:18: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:18: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:18: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:18: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:18: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:18: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:18: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:18: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:18: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:18: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:18: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:18: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:18: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:18: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:18: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:18: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:18: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:18: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:18: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:18: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:18: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:19: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:19: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:19: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:19: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:19: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:20: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:20: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:20: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:21: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:21: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:21: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:21: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:21: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:22: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:22: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:22: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:22: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:48:22: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:23, data Length:0
2016-03-23 10:48:22: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:48:22: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:48:22: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 23
2016-03-23 10:48:22: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:48:22: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:48:22: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:48:23: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:23: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:23: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:23: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:23: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:23: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:23: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:23: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:23: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:23: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:23: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:23: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:23: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:23: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:23: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:23: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:23: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:23: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:23: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:23: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:23: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:23: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:23: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:23: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:23: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:23: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:24: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:24: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:24: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:25: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:25: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:25: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:25: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:25: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:26: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:26: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:26: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:27: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:27: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:27: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:27: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:27: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:28: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:28: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:28: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:28: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:28: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:28: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:28: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:28: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:28: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_current_xlog_location()"
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  pool_read: read 91 bytes from backend 0
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_last_xlog_replay_location()"
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  pool_read: read 95 bytes from backend 0
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:28: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:28: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:28: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:28: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:28: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:28: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:28: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:28: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:28: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:28: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:28: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:28: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:28: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:28: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:28: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:28: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:28: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:28: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:28: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:28: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:28: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:28: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:28: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:28: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:28: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:28: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:29: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:29: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:29: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:29: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:29: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:30: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:30: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:30: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:31: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:31: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:31: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:31: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:31: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:32: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:32: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:32: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:32: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:48:32: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:24, data Length:0
2016-03-23 10:48:32: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:48:32: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:48:32: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 24
2016-03-23 10:48:32: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:48:32: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:48:32: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:48:33: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:33: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:33: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:33: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:33: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:33: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:33: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:33: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:33: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:33: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:33: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:33: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:33: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:33: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:33: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:33: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:33: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:33: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:33: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:33: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:33: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:33: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:33: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:33: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:33: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:33: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:34: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:34: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:34: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:35: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:35: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:35: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:35: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:35: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:36: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:36: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:36: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:37: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:37: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:37: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:37: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:37: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:38: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:38: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:38: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:38: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:38: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:38: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:38: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:38: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:38: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:38: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_current_xlog_location()"
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  pool_read: read 91 bytes from backend 0
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_last_xlog_replay_location()"
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  pool_read: read 95 bytes from backend 0
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:38: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:38: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:38: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:38: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:38: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:38: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:38: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:38: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:38: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:38: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:38: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:38: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:38: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:38: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:38: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:38: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:38: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:38: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:38: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:38: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:38: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:38: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:38: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:38: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:38: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:38: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:39: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:39: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:39: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:39: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:39: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:40: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:40: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:40: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:40: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:41: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:41: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:41: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:41: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:41: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:42: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:42: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:42: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:42: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:42: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = MASTER
2016-03-23 10:48:42: pid 17469: DEBUG:  sending watchdog packet Socket:8, Type:[IAM COORDINATOR], Command_ID:25, data Length:0
2016-03-23 10:48:42: pid 17469: DEBUG:  received packet tyep I while need packet type
2016-03-23 10:48:42: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:48:42: pid 17469: DEBUG:  Watchdog node "Linux_serv-ed02_9999" has replied for command id 25
2016-03-23 10:48:42: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = MASTER
2016-03-23 10:48:42: pid 17469: DEBUG:  I am the cluster leader node command finished with status:[ALL NODES REPLIED]
2016-03-23 10:48:42: pid 17469: DETAIL:  The command was sent to 1 nodes and 1 nodes replied to it
2016-03-23 10:48:43: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:43: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:43: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:43: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:43: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:43: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:43: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:43: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:43: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:43: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:43: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:43: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:43: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:43: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:43: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:43: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:43: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:43: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:43: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:43: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:43: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:43: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:43: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:43: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:43: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:43: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:44: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:44: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:44: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:44: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:45: pid 17800: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:45: pid 17683: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:45: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:45: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:45: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:46: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:46: pid 17620: DEBUG:  received heartbeat signal from "serv-ed02:9999"
2016-03-23 10:48:46: pid 17469: DEBUG:  received packet tyep X while need packet type
2016-03-23 10:48:46: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = MASTER
2016-03-23 10:48:46: pid 17469: DEBUG:  STATE MACHINE INVOKED WITH EVENT = REMOTE NODE LOST Current State = MASTER
2016-03-23 10:48:46: pid 17469: LOG:  remote node "Linux_serv-ed02_9999" is shutting down
2016-03-23 10:48:46: pid 17469: DEBUG:  We have lost the node "Linux_serv-ed02_9999" but quorum still holds
2016-03-23 10:48:46: pid 17469: LOG:  read from socket failed, remote end closed the connection
2016-03-23 10:48:46: pid 17469: LOG:  read from socket failed, remote end closed the connection
2016-03-23 10:48:46: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:46: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:46: pid 17799: LOG:  watchdog: lifecheck started
2016-03-23 10:48:47: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:47: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:47: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:48: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:48: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:48: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:48: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:48: pid 17775: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:48: pid 17775: DEBUG:  authenticate kind = 0
2016-03-23 10:48:48: pid 17775: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:48: pid 17775: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_current_xlog_location()"
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:48: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:48: pid 17775: DEBUG:  pool_read: read 91 bytes from backend 0
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: extended:0 query:"SELECT pg_last_xlog_replay_location()"
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  pool_write: to backend: kind:Q
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  pool_read: read 95 bytes from backend 0
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: kind: 'T'
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: received ROW DESCRIPTION ('T')
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: row description: num_fileds: 1
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: kind: 'D'
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: received DATA ROW ('D')
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: kind: 'C'
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: received COMMAND COMPLETE ('C')
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: kind: 'Z'
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  do_query: received READY FOR QUERY ('Z')
2016-03-23 10:48:48: pid 17775: CONTEXT:  while checking replication time lag
2016-03-23 10:48:48: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:48: pid 17775: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:48: pid 17468: DEBUG:  reaper handler
2016-03-23 10:48:48: pid 17468: WARNING:  watchdog lifecheck process with pid: 17799 was terminated by segmentation fault
2016-03-23 10:48:48: pid 17468: LOG:  fork a new watchdog lifecheck process with pid: 17838
2016-03-23 10:48:48: pid 17468: DEBUG:  reaper handler: exiting normally
2016-03-23 10:48:48: pid 17468: DEBUG:  starting health check
2016-03-23 10:48:48: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:48: pid 17468: DEBUG:  doing health check against database:postgres user:postgres
2016-03-23 10:48:48: pid 17468: DEBUG:  Backend DB node 0 status is 2
2016-03-23 10:48:48: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 0 having status 2
2016-03-23 10:48:48: pid 17838: DEBUG:  I am watchdog lifecheck child with pid:17838
2016-03-23 10:48:48: pid 17469: LOG:  new IPC connection received
2016-03-23 10:48:48: pid 17838: LOG:  2 watchdog nodes are configured for lifecheck
2016-03-23 10:48:48: pid 17838: LOG:  watchdog nodes ID:0 Name:"Linux_serv-ed01_9999"
2016-03-23 10:48:48: pid 17838: DETAIL:  Host:"serv-ed01" WD Port:9000 pgpool-II port:9999
2016-03-23 10:48:48: pid 17838: LOG:  watchdog nodes ID:1 Name:"Linux_serv-ed02_9999"
2016-03-23 10:48:48: pid 17838: DETAIL:  Host:"serv-ed02" WD Port:9000 pgpool-II port:9999
2016-03-23 10:48:48: pid 17838: DEBUG:  watchdog checking life check is ready
2016-03-23 10:48:48: pid 17838: DETAIL:  pgpool:1 at "serv-ed02:9999" has not send the heartbeat signal yet
2016-03-23 10:48:48: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:48: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:48: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:48: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:48: pid 17468: DEBUG:  persistent DB connection to backend node 0 having status 2 is successful
2016-03-23 10:48:48: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:48: pid 17468: DEBUG:  Backend DB node 1 status is 1
2016-03-23 10:48:48: pid 17468: DEBUG:  Trying to make persistent DB connection to backend node 1 having status 1
2016-03-23 10:48:48: pid 17468: DEBUG:  pool_read: read 327 bytes from backend 0
2016-03-23 10:48:48: pid 17468: DEBUG:  authenticate kind = 0
2016-03-23 10:48:48: pid 17468: DEBUG:  authenticate backend: key data received
2016-03-23 10:48:48: pid 17468: DEBUG:  authenticate backend: transaction state: I
2016-03-23 10:48:48: pid 17468: DEBUG:  persistent DB connection to backend node 1 having status 1 is successful
2016-03-23 10:48:48: pid 17468: DEBUG:  pool_write: to backend: kind:X
2016-03-23 10:48:48: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:48: pid 17468: DEBUG:  health check: clearing alarm
2016-03-23 10:48:49: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:49: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:49: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:49: pid 17840: LOG:  failed to create watchdog heartbeat receive socket.
2016-03-23 10:48:49: pid 17840: DETAIL:  setsockopt(SO_BINDTODEVICE) requies root privilege
2016-03-23 10:48:49: pid 17840: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:48:49: pid 17840: LOG:  creating watchdog heartbeat receive socket.
2016-03-23 10:48:49: pid 17840: DETAIL:  set SO_REUSEPORT
2016-03-23 10:48:49: pid 17841: LOG:  creating socket for sending heartbeat
2016-03-23 10:48:49: pid 17841: DETAIL:  setsockopt(SO_BINDTODEVICE) requires root privilege
2016-03-23 10:48:49: pid 17841: LOG:  set SO_REUSEPORT option to the socket
2016-03-23 10:48:49: pid 17841: LOG:  creating socket for sending heartbeat
2016-03-23 10:48:49: pid 17841: DETAIL:  set SO_REUSEPORT
2016-03-23 10:48:49: pid 17841: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:50: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:50: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:51: pid 17684: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:51: pid 17733: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:51: pid 17801: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:51: pid 17841: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:52: pid 17621: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:52: pid 17479: DEBUG:  watchdog heartbeat: send heartbeat signal to serv-ed02:9694
2016-03-23 10:48:52: pid 17479: DEBUG:  watchdog heartbeat sender child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17801: DEBUG:  watchdog heartbeat sender child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17774: DEBUG:  PCP child receives shutdown request signal 2, Forwarding to all children
2016-03-23 10:48:52: pid 17840: DEBUG:  watchdog heartbeat receiver child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17774: DEBUG:  PCP child receives fast shutdown request
2016-03-23 10:48:52: pid 17684: DEBUG:  watchdog heartbeat sender child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17469: LOG:  Watchdog is shutting down
2016-03-23 10:48:52: pid 17800: DEBUG:  watchdog heartbeat receiver child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17621: DEBUG:  watchdog heartbeat sender child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17842: LOG:  watchdog: de-escalation started
2016-03-23 10:48:52: pid 17468: LOG:  received fast shutdown request
2016-03-23 10:48:52: pid 17468: LOG:  shutdown request. closing listen socket
2016-03-23 10:48:52: pid 17476: DEBUG:  watchdog heartbeat receiver child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17774: DEBUG:  PCP child receives shutdown request signal 2, Forwarding to all children
2016-03-23 10:48:52: pid 17774: DEBUG:  PCP child receives fast shutdown request
2016-03-23 10:48:52: pid 17620: DEBUG:  watchdog heartbeat receiver child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17838: DEBUG:  lifecheck child receives shutdown request signal 2, Forwarding to all children
2016-03-23 10:48:52: pid 17838: DEBUG:  lifecheck child receives fast shutdown request
2016-03-23 10:48:52: pid 17732: DEBUG:  watchdog heartbeat receiver child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17683: DEBUG:  watchdog heartbeat receiver child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17841: DEBUG:  watchdog heartbeat sender child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17733: DEBUG:  watchdog heartbeat sender child receives shutdown request signal 2
2016-03-23 10:48:52: pid 17842: DEBUG:  watchdog exec interface up/down command: 'pgp_ip_addr.sh del $_IP_$/24 eth0' succeeded
2016-03-23 10:48:55: pid 17842: DEBUG:  watchdog executing ping
2016-03-23 10:48:55: pid 17842: DETAIL:  failed to ping "10.129.124.50" exit code: 1
2016-03-23 10:48:55: pid 17842: LOG:  watchdog bringing down delegate IP
2016-03-23 10:48:55: pid 17842: DETAIL:  if_down_cmd succeeded