[pgpool-general: 5015] Problem connecting to pgpool

[Etienne Journet]

Hello,

I have, quite frequently, a problem connecting to pgpool. The application seems to not be able to allow other connections but doesn’t reject them, it makes them hang forever.
It does not affect existing connection, but sometimes when I want to restart my front office I have to restart the pgpool service to make it work and allow connections.

Here are the logs at the moment (with my restart) :

2016-09-21 17:49:20: pid 1939: LOG:  child process with pid: 10496 exits with status 512
2016-09-21 17:49:20: pid 1939: LOG:  fork a new child process with pid: 10922
2016-09-21 17:49:30: pid 1939: LOG:  child process with pid: 10841 exits with status 512
2016-09-21 17:49:30: pid 1939: LOG:  fork a new child process with pid: 10923
2016-09-21 17:51:21: pid 1939: LOG:  child process with pid: 10877 exits with status 512
2016-09-21 17:51:21: pid 1939: LOG:  fork a new child process with pid: 10931
2016-09-21 17:52:01: pid 1939: LOG:  child process with pid: 10897 exits with status 512
2016-09-21 17:52:01: pid 1939: LOG:  fork a new child process with pid: 10934
2016-09-21 17:54:58: pid 10977: LOG:  stop request sent to pgpool. waiting for termination...
2016-09-21 17:54:58: pid 1939: LOG:  received fast shutdown request
2016-09-21 17:52:01: pid 1939: LOG:  fork a new child process with pid: 10934
2016-09-21 17:54:58: pid 10977: LOG:  stop request sent to pgpool. waiting for termination...
2016-09-21 17:54:58: pid 1939: LOG:  received fast shutdown request
.2016-09-21 17:54:58: pid 1939: LOG:  shutdown request. closing listen socket
2016-09-21 17:54:58: pid 10819: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10922: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10598: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10934: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10846: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10904: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10605: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10900: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 6935: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10852: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10714: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10868: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10888: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10913: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10687: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10903: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10883: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10918: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10919: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10538: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10742: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10912: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10908: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10923: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10905: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10909: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10685: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10871: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10544: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10931: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10896: LOG:  child process received shutdown request signal 2
2016-09-21 17:54:58: pid 10853: LOG:  child process received shutdown request signal 2
done.
2016-09-21 17:54:59: pid 11016: LOG:  reading status file: 0 th backend is set to down status
2016-09-21 17:54:59: pid 11016: LOG:  Setting up socket for 0.0.0.0:9999
2016-09-21 17:54:59: pid 11016: LOG:  Setting up socket for :::9999
2016-09-21 17:54:59: pid 11016: LOG:  pgpool-II successfully started. version 3.4.5 (tataraboshi)


I’m not using health check because my infrastructure handles it 'by itself ». I’m joining you my conf : 

Is this a known bug ?
Etienne Journet
Administrateur Système & Réseaux - Société AFS2R
(+33)(0)9 72 53 50 87
etienne.journet at afs2r.fr






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20160922/39ffffd2/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool.conf
Type: application/octet-stream
Size: 33422 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20160922/39ffffd2/attachment-0001.obj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20160922/39ffffd2/attachment-0003.html>