[pgpool-general: 2926] Re: Connections stuck in CLOSE_WAIT, again
Juan Jose Perez
jperez at oteara.com
Thu Jun 19 01:37:38 JST 2014
We are facing this same problem, and as I see it remains unsolved
(or perhaps they didn't report the solution).
We are using pgpool 3.3.3, with two postgres 9.1 in streaming
replication. The OS is Debian 3.2.54-2 (64bits).
The log shows messages like this:
ProcessFrontendResponse: failed to read kind from frontend.
frontend abnormally exited
I'm not sure but it looks like one for each connection left unclosed.
Also, a ps -ef returns a lot of pgpool children in DISCARD state.
And the netstat -anp, gives the correspondent TCP connection in
The developer has checked the client process is closing the
connections and we try connecting directly to the postgres and it worked
When you say "to attach debugger", do you mean change log_statment
= true or debug_level to a value other than 0 or any other procedure?
El 02/04/14 01:05, Tatsuo Ishii escribió:
>> We have a client on 3.3 experiencing the the problem noted here:
>> strace is showing the child processes at:
>> clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fcf659f3a10) = 6258
>> I didn't see any resolution of that issue; is there data we can gather to assist?
> I followed the old 2012 posting with:
>> That means pgpool does not close the socket connected to by your
>> applications. Is it possible to attach debugger to such that pgpool
>> process to see what pgpool is doing?
> But I got no response until now. Can you please do this?
> Best regards,
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese: http://www.sraoss.co.jp
> pgpool-general mailing list
> pgpool-general at pgpool.net
More information about the pgpool-general