[pgpool-general: 5071] Re: Problem connecting to pgpool

Tue Oct 25 16:51:27 JST 2016

Hey,

I got the problem today again :
2016-10-25 08:57:31: pid 19184: LOG:  fork a new child process with pid: 10960
2016-10-25 08:57:31: pid 19184: LOCATION:  pgpool_main.c:2165
2016-10-25 08:58:29: pid 19184: LOG:  child process with pid: 10918 exits with status 512
2016-10-25 08:58:29: pid 19184: LOCATION:  pgpool_main.c:2107
2016-10-25 08:58:29: pid 19184: LOG:  fork a new child process with pid: 10963
2016-10-25 08:58:29: pid 19184: LOCATION:  pgpool_main.c:2165
2016-10-25 08:58:39: pid 19184: LOG:  child process with pid: 10919 exits with status 512
2016-10-25 08:58:39: pid 19184: LOCATION:  pgpool_main.c:2107
2016-10-25 08:58:39: pid 19184: LOG:  fork a new child process with pid: 10964
2016-10-25 08:58:39: pid 19184: LOCATION:  pgpool_main.c:2165

My parameters are : 
max_connections = 100	
#superuser_reserved_connections = 3 (commented out)

I’m running pgpool and postgresql on different servers. This behavior happens literally anytime...

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

> Le 22 sept. 2016 à 12:20, Avi Weinberg <AviW at gilat.com> a écrit :
> 
> What is your postgres configuration for max_connections and superuser_reserved_connections?  Do you run pgpool and postgres on the same machine?  
>  
> I have the same problem.  I posted my connection problem on Monday in mail titled "Postgres / pgpool connection configuration".  Every few days the connection with port 9999 wait forever and at the same time connection with port 5432 work right-a-way.  It might be related to the fact that we test failover and resets on the setup.
>  
>  
>  
>  
>  
> From: pgpool-general-bounces at pgpool.net [mailto:pgpool-general-bounces at pgpool.net] On Behalf Of Etienne Journet
> Sent: Thursday, September 22, 2016 10:32 AM
> To: pgpool-general at pgpool.net
> Subject: [pgpool-general: 5015] Problem connecting to pgpool
>  
> 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 : 
> IMPORTANT - This email and any attachments is intended for the above named addressee(s), and may contain information which is confidential or privileged. If you are not the intended recipient, please inform the sender immediately and delete this email: you should not copy or use this e-mail for any purpose nor disclose its contents to any person. _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general