<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Sorry, this was my error... the
recovery_timeout on that server had been 'temporarily' set to 0.
Mind you, the documentation doesn't say recovery_timeout is used
to control the wait for existing connections to close.
Nevertheless it was my mistake.<br>
<br>
Thanks,<br>
Sean<br>
<br>
On 14-04-03 08:43 AM, Sean Hogan wrote:<br>
</div>
<blockquote cite="mid:533D425D.6080506@compusult.net" type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Can someone tell me what the following logging means?<br>
<br>
2014-04-02 17:05:05 LOG: pid 9415: 1st stage is done<br>
2014-04-02 17:05:05 LOG: pid 9415: starting 2nd stage<br>
2014-04-02 17:05:05 LOG: pid 12418: pool_process_query: child
connection forced to terminate due to client_idle_limitis -1<br>
2014-04-02 17:05:05 LOG: pid 12418: pool_process_query: child
connection forced to terminate due to client_idle_limitis -1<br>
2014-04-02 17:05:05 LOG: pid 12154: pool_process_query: child
connection forced to terminate due to client_idle_limitis -1<br>
2014-04-02 17:05:05 LOG: pid 12154: pool_process_query: child
connection forced to terminate due to client_idle_limitis -1<br>
2014-04-02 17:05:05 LOG: pid 12813: pool_process_query: child
connection forced to terminate due to client_idle_limitis -1<br>
2014-04-02 17:05:05 LOG: pid 12813: pool_process_query: child
connection forced to terminate due to client_idle_limitis -1<br>
<b>2014-04-02 17:05:05 ERROR: pid 9415: wait_connection_closed:
existing connections did not close in 0 sec.</b><b><br>
</b><b>2014-04-02 17:05:05 ERROR: pid 9415: start_recovery:
timeover for waiting connection closed</b><br>
2014-04-02 17:05:05 LOG: pid 9662: pool_process_query: child
connection forced to terminate due to client_idle_limitis -1<br>
2014-04-02 17:05:05 LOG: pid 12641: pool_process_query: child
connection forced to terminate due to client_idle_limitis -1<br>
...<br>
2014-04-02 17:05:05 LOG: pid 17997: pool_process_query: child
connection forced to terminate due to client_idle_limitis -1<br>
<br>
I don't see any parameter set to 0 that would control how long
pgpool waits for existing connections to be closed. Here are the
Online Recovery parameters from pgpool.conf:<br>
<br>
recovery_user = 'postgres'<br>
# Online recovery user<br>
recovery_password = ''<br>
# Online recovery password<br>
recovery_1st_stage_command = 'do-base-backup.sh'<br>
# Executes a command in first
stage<br>
recovery_2nd_stage_command = 'pgpool_recovery_pitr.sh'<br>
# Executes a command in second
stage<br>
recovery_timeout = 120<br>
# Timeout in seconds to wait
for the<br>
# recovering node's postmaster
to start up<br>
# 0 means no wait<br>
client_idle_limit_in_recovery = -1<br>
# Client is disconnected after
being idle<br>
# for that many seconds in the
second stage<br>
# of online recovery<br>
# 0 means no disconnection<br>
# -1 means immediate
disconnection<br>
<br>
Thanks,<br>
Sean<br>
</blockquote>
<br>
</body>
</html>