<div dir="ltr">Hi<div><br></div><div>Health check timed out warning normally means that pgpool-II health check is not able to connect to backend within the health_check_timeout period. So can you verify if you are getting some network glitches and/or errors in PG server log that related to the connection failure.</div><div><br></div><div>I have also found a possible issue that can cause the same where some signal other than health check alarm if received while the pgpool health check is waiting for the data could be mistakenly considered as the health check timed out signal, and I have just pushed the fix for that in 3.4, 3.5 and master branches.</div><div><br></div><div><a href="https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=861a71b740a546848bcad581cc0777abfae79ddc">https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=861a71b740a546848bcad581cc0777abfae79ddc</a><br></div><div><br></div><div>Can you try building from the source if you still face the same problem.</div><div><br></div><div>Thanks</div><div>Best regards</div><div>Muhammad Usama</div><div> <br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 8, 2016 at 12:18 PM, Shay Cohavi <span dir="ltr"><<a href="mailto:cohavisi@gmail.com" target="_blank">cohavisi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<div>after upgardig pgpool to 3.5.3 version I keep getting these errors via pgpool log massages:</div><div><br></div><div><div>2016-08-08 10:15:59: pid 14964: LOG: child process with pid: 22056 exits with status 256</div><div>2016-08-08 10:15:59: pid 14964: LOG: fork a new child process with pid: 22128</div><div>2016-08-08 10:16:00: pid 14964: LOG: child process with pid: 22032 exits with status 256</div><div>2016-08-08 10:16:00: pid 14964: LOG: fork a new child process with pid: 22138</div><div><b>2016-08-08 10:16:00: pid 14964: WARNING: health check timed out while waiting for reading data</b></div><div><b>2016-08-08 10:16:00: pid 14964: ERROR: unable to read data from DB node 0</b></div><div><b>2016-08-08 10:16:00: pid 14964: DETAIL: pool_check_fd call failed with an error "Interrupted system call"</b></div><div>2016-08-08 10:16:00: pid 14964: LOG: child process with pid: 22033 exits with status 256</div><div>2016-08-08 10:16:00: pid 14964: LOG: fork a new child process with pid: 22140</div><div>2016-08-08 10:16:00: pid 14964: LOG: child process with pid: 22065 exits with status 256</div></div><div><br></div><div><br></div><div>healthcheck parameters:</div><div><br></div><div><div>health_check_period=1</div><div># Health check period</div><div># Disabled (0) by default</div><div>health_check_timeout=20</div><div># Health check timeout</div><div># 0 means no timeout</div><div>health_check_user='postgres'</div><div># Health check user</div><div>health_check_password='<wbr>postgres'</div><div># Password for health check user</div><div>health_check_database=''</div><div># Database name for health check. If '', tries 'postgres' frist, then 'template1'</div><div><br></div><div>health_check_max_retries=2</div><div># Maximum number of times to retry a failed health check before giving up.</div><div>health_check_retry_delay=1</div></div><div><br></div><div><br></div><div>please advice..</div><div><br></div><div>Thanks,</div><div>cohavisi</div><div></div></div>
<br>______________________________<wbr>_________________<br>
pgpool-general mailing list<br>
<a href="mailto:pgpool-general@pgpool.net">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>
<br></blockquote></div><br></div></div></div>