[pgpool-general: 8080] Re: CLIENT_IDLE_LIMIT>0 --> ERROR message
Bo Peng
pengbo at sraoss.co.jp
Tue Apr 12 17:58:16 JST 2022
Hello,
On Mon, 11 Apr 2022 18:13:39 +0300
"Nikolay Mastilo (HM)" <nikm71 at hotmail.com> wrote:
> Hello,
>
> In our pgpool configuration we set parameter CLIENT_IDLE_LIMIT=300.
>
> As a result of that, our app developers periodically receive the
> following messages in the log:
>
> 2021-11-17 13:49:51: pid 471: ERROR: unable to read data
> 2021-11-17 13:49:51: pid 471: DETAIL: child connection forced to
> terminate due to client_idle_limit:300 is reached
> 2021-11-17 13:49:51: pid 20: LOG: child process with pid: 457 exits with
> status 256
> 2021-11-17 13:49:51: pid 20: LOG: fork a new child process with pid: 516
>
> So they see an ERROR message and it confuses them.
>
> Could you tell me if this is really an error or if it can be ignored?
>
> If this is NOT a really error, why is it displayed so suspicious?
Thank you for pointing it out.
It means the child process is terminated due to client_idle_limit.
I think it can be ignored.
Your application may get an error message when it tries to send request to Pgpool-II next time.
We will think about if we should downgrade this LOG.
--
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan
http://www.sraoss.co.jp/
More information about the pgpool-general
mailing list