<div dir="ltr">Hi<div><br></div><div>Please share the <span id="gmail-a0768fe4-7e20-41e6-83db-bb0c275dfa19" class="gmail-GINGER_SOFTWARE_mark">pgpool.conf</span> and log files., Pgpool-II log should have the information why Pgpool is detaching the <span id="gmail-d1faa674-ad67-414f-bae4-0da80828b2e9" class="gmail-GINGER_SOFTWARE_mark">backend</span> node. </div><div><br></div><div>Thanks</div><div>Best regards</div><div>Muhammad Usama</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 25, 2017 at 1:47 PM, Simon Windsor <span dir="ltr"><<a href="mailto:simon.windsor@cornfield.me.uk" target="_blank">simon.windsor@cornfield.me.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
We are testing pgPool with two Postgres 9.5 nodes, and using pgPool to manage the replication of data to the two databases.<br>
<br>
Every few days, one of the nodes goes from status 2 to 3, until we re-atach the node. There doesn't appear to be anything that triggers this. Is this a known issue that we can handle automatically, if so how, or is there some logging I must enable to track the root casue?<br>
<br>
Thank you<br>
<br>
Simon<br>
<br>
-- <br>
Simon Windsor<br>
<br>
Eml: <a href="mailto:simon.windsor@cornfield.me.uk" target="_blank">simon.windsor@cornfield.me.uk</a><br>
Tel: 01454 617689<br>
Mob: 0755 197 9733<br>
<br>
<br>
“There is nothing in the world that some man cannot make a little worse and sell a little cheaper, and he who considers price only is that man's lawful prey.”<br>
<br>
______________________________<wbr>_________________<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/<wbr>listinfo/pgpool-general</a><br>
</blockquote></div><br></div>