<div dir="ltr"><div class="gmail_default"><font face="monospace, monospace">Muhammad,</font><br></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">Excellent news! Thank you for getting that corrected so quickly. Is there any way of knowing how long it will take for that change to be reflected in pgpool pacakge in the pgdg yum repositories, or is that out of the pgpool developers' scope of influence?</font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">MN</font></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><font face="monospace, monospace" size="2"><br></font><div><font face="monospace, monospace" size="2">Mike Neir</font></div><div><font face="monospace, monospace" size="2">Infrastructure Administrator</font></div><div><font face="monospace, monospace" size="2">Liquid Web, Inc.</font></div><div><br></div></div></div></div></div></div><div class="gmail_quote">On Mon, Mar 7, 2016 at 10:47 AM, Muhammad Usama <span dir="ltr"><<a href="mailto:m.usama@gmail.com" target="_blank">m.usama@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Mike<div><br></div><div>Thanks for pointing out this out, The problem was caused by the logical mistake in the latest version of pgpool-II and I have pushed the fix for it.</div><div><br></div><div><a href="http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=e2f822fae9a4956f210bccafd0eade26642c90fa" target="_blank">http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=e2f822fae9a4956f210bccafd0eade26642c90fa</a></div><div><br></div><div>Regards</div><div>Muhammad Usama</div><div><br></div><div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Sat, Mar 5, 2016 at 5:43 AM, Mike Neir <span dir="ltr"><<a href="mailto:mike@liquidweb.com" target="_blank">mike@liquidweb.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div><font face="monospace, monospace">Greetings pgpool devs and users,</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">I am attempting to re-create a postgres 9.2 + pgpool setup that a former co-worker created so that I may become more familiar with the setup process and so it can be properly documented. I am configuring a two-node test lab using streaming replication, where the postgres WAL sender handles writes, and both the WAL sender and receiver can handle reads. </font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">I believe I have everything configured properly except for one vexing issue. When running queries through pgpool, even simple status queries, the workers will eventually die, having reached their internal connection limit. This is expected, but pgpool does not seem to be forking another worker to replace it, and that behavior eventually results in pgpool not being able to handle queries due to a lack of workers. This manifests in the logs as follows:</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">2016-03-04 18:27:50: pid 8754: FATAL: child exiting, 500 connections reached</font></div><div><font face="monospace, monospace">2016-03-04 18:27:50: pid 8303: LOG: child process with pid: 8754 exits with status 512</font></div><div><font face="monospace, monospace">2016-03-04 18:27:50: pid 8303: LOG: child process with pid: 8754 exited with success and will not be restarted</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">I have not yet got to the point of importing data into postgres. I can manifest this condition with repeated execution of the following command:</font></div><div><font face="monospace, monospace"> $ psql -h localhost -U monitor postgres -c "SHOW pool_nodes;"</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">The behavior is the same on both nodes, regardless of whether it is a WAL sender or recevier.</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">I've attempted to dig through the sources to find the scenario that would tell pgpool that not forking a replacement worker is proper behavior, but my C is *very* rusty, and I ran out of patience long before I understood what leads to that condition.</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">In short, I'm looking for insight on what configuration directives could lead to that behavior, and how to correct it. </font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">Environment Details:</font></div><div><font face="monospace, monospace">- Each node is a VM running CentOS 6.7, 64-bit</font></div><div><font face="monospace, monospace">- Each node is running postgres 9.2.15 (latest version available), installed via pgdg92 yum repository</font></div><div><font face="monospace, monospace">- Each node is running pgpool-II-92 3.5.0-1 (latest version available), installed via pgdg92 yum repository</font></div><div><font face="monospace, monospace">- I can provide the pgpool or postgres configurations if need be, but since they are lengthy, I will wait until they're requested. </font></div></div><span><font color="#888888"><div><div><div dir="ltr"><div dir="ltr"><font face="monospace, monospace" size="2"><br></font><div><font face="monospace, monospace" size="2">Mike Neir</font></div><div><font face="monospace, monospace" size="2">Infrastructure Administrator</font></div><div><font face="monospace, monospace" size="2">Liquid Web, Inc.</font></div><div><br></div></div></div></div></div>
</font></span></div>
<br></div></div>_______________________________________________<br>
pgpool-general mailing list<br>
<a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
<a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" rel="noreferrer" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
<br></blockquote></div><br></div></div></div>
</blockquote></div><br></div></div>