Not wanting to be impatient, but I'm very concerned about this
problem, since its impossible to predict when it will occur. Is there
additional information that I can provide to investigate this further?
thanks
On Tue, Nov 22, 2011 at 10:11 AM, Lonni J Friedman netll...@gmail.com wrote:
This
Not wanting to be impatient, but I'm very concerned about this
problem, since its impossible to predict when it will occur. Is there
additional information that I can provide to investigate this further?
I really need to know where pgpool is looping.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
On Wed, Nov 23, 2011 at 10:42 PM, Tatsuo Ishii is...@sraoss.co.jp wrote:
Not wanting to be impatient, but I'm very concerned about this
problem, since its impossible to predict when it will occur. Is there
additional information that I can provide to investigate this further?
I really need
On Wed, Nov 23, 2011 at 10:42 PM, Tatsuo Ishii is...@sraoss.co.jp wrote:
Not wanting to be impatient, but I'm very concerned about this
problem, since its impossible to predict when it will occur. Is there
additional information that I can provide to investigate this further?
I really need
This hadn't reproduced in a long time, but we ugpraded to pgpool-3.1 a
week ago, and this morning I found a pgpool process that was consuming
100% CPU, and had been running for a week (although wasn't consuming
100% CPU the entire time). Something else weird is that it showed an
active, idle
I tried to do that, but pgpool refuses to start reporting:
-bash: /usr/lib/debug/usr/sbin/pgpool.debug: bad ELF interpreter: No
such file or directory
I'm puzzled why it fails, as it was built on the same server where I
built the (working) release build of pgpool.
$ file
This happened again. I ran the gdb command that you requested,
however it occurred to me that the output may not be all that useful
since I'm not running a debug build of pgpool:
###
# gdb pgpool 2343
GNU gdb (GDB) Red Hat Enterprise Linux (7.1-29.el6)
Copyright (C) 2010 Free Software
This problem has returned yet again:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
29191 postgres 20 0 80192 14m 1544 R 89.8 0.2 51:15.91 pgpool
postgres 29191 3.4 0.1 80192 14728 ?RSep13 51:40
pgpool: lfriedman nightly 10.31.96.84(61698) idle
I'd
Thanks for your reply. I'll do this the next time this happens (which
will likely be within a few days based on history).
On Wed, Sep 14, 2011 at 3:57 PM, Tatsuo Ishii is...@sraoss.co.jp wrote:
Please use gdb. For example,
become postgres user (or root user)
gdb pgpool 29191
bt
cont
bt
