Greetings,
I have a 3 node PostgreSQL-9.0.4 cluster (1 master, 2 standbys) setup
with streaming replication enabled & verified functional. I'm in the
process of setting up pgpool-II-3.0.4 (for the first time), where all
I care about is the load balancing functionality, such that all the
read-only
Greetings,
I just deployed a postgresql-9.0.4 cluster (1 master, 2 hot
standby's), with pgpool-II-3.0.4 (all running on Linux-x86_64
servers). I'm currently only using pgpool for load balancing, and its
working fine. However, I'm see tons (dozens every minute) of the
following in my postgresql se
No one has any ideas or suggestions?
On Fri, Sep 2, 2011 at 6:44 PM, Lonni J Friedman wrote:
> Greetings,
> I just deployed a postgresql-9.0.4 cluster (1 master, 2 hot
> standby's), with pgpool-II-3.0.4 (all running on Linux-x86_64
> servers). I'm currently only using pgp
and that you can connect from the server running
> pgpool.
>
> On Sep 4, 2011 7:22 PM, "Lonni J Friedman" wrote:
>> No one has any ideas or suggestions?
>>
>> On Fri, Sep 2, 2011 at 6:44 PM, Lonni J Friedman
>> wrote:
>>> Greetings,
>>
On Sun, Sep 4, 2011 at 5:36 PM, Rosser Schwarz wrote:
> "Unexpected EOF" doesn't mean a postgres backend is failing; it
> typically means that a client has disconnected from its backend
> without closing out the session. (E.g., connect via psql, then kill
> the psql process -- not the backend! --
Greetings,
I'm running pgpool-3.0.4 on a Linux-x86_64 server serving as a load
balancer for a three server postgresql-9.0.4 cluster (1 master, 2
standby). I'm seeing strange behavior where a single pgpool process
seems to hang after some period of time, and then consume 100% of the
CPU. I've seen
On Thu, Sep 8, 2011 at 5:30 AM, Toshihiro Kitagawa
wrote:
> - Change the lock method of insert_lock. The previous insert_lock uses
> row locking against the sequence relation, but the current one uses
> row locking against pgpool_catalog.insert_lock table. The reason is
> that PostgreSQL core d
No one else has experienced this or has suggestions how to debug it?
On Wed, Sep 7, 2011 at 12:49 PM, Lonni J Friedman wrote:
> Greetings,
> I'm running pgpool-3.0.4 on a Linux-x86_64 server serving as a load
> balancer for a three server postgresql-9.0.4 cluster (1 master, 2
&g
On Mon, Sep 12, 2011 at 3:34 AM, Toshihiro Kitagawa
wrote:
> Hi,
>
>> However, I'm see tons (dozens every minute) of the
>> following in my postgresql server logs:
>> LOG: unexpected EOF on client connection
>
> I found recently that it occurs if you specify the role that needs a
> password to he
Greetings,
I've got a 3 node postgresql-9.0.4 cluster (1 master, two standby, all
running on Linux-x86_64. I had a hardware problem on one of the
standby's, and had to bring it down to swap out the bad HW. I got it
synced back up with the mater successfully, and I can successfully
manually run SQ
-
>> boun...@pgfoundry.org] On Behalf Of Lonni J Friedman
>> Sent: Monday, September 12, 2011 1:14 PM
>> To: pgpool-general@pgfoundry.org
>> Subject: [Pgpool-general] pgpool thinks a backend is down even though
>> its not
>>
>> Greetings,
>> I've g
On Mon, Sep 12, 2011 at 4:16 PM, Tatsuo Ishii wrote:
>> Yes, all connections defined in pool_hba.conf are trust auth.
>> However, I also have
>> health_check_period = 0
>> in pgpool.conf, so I'd assume that no health checks are being performed?
>
> Have you changed child_life_time or something fro
On Mon, Sep 12, 2011 at 5:14 PM, Tatsuo Ishii wrote:
>> On Mon, Sep 12, 2011 at 4:16 PM, Tatsuo Ishii wrote:
Yes, all connections defined in pool_hba.conf are trust auth.
However, I also have
health_check_period = 0
in pgpool.conf, so I'd assume that no health checks are being
On Mon, Sep 12, 2011 at 6:39 PM, Tatsuo Ishii wrote:
>>> I couldn't find anything possibly related to your problem at a first
>>> grance(in theory client_idle_limit and authentication_timeout are not
>>> related but you might want to change them to see anything could be
>>> changed).
>>
>> OK, I'l
On Mon, Sep 12, 2011 at 6:47 PM, Lonni J Friedman wrote:
> On Mon, Sep 12, 2011 at 6:39 PM, Tatsuo Ishii wrote:
>>>> I couldn't find anything possibly related to your problem at a first
>>>> grance(in theory client_idle_limit and authentication_timeout are not
&g
On Tue, Sep 13, 2011 at 8:48 PM, Tatsuo Ishii wrote:
>> On Mon, Sep 12, 2011 at 6:47 PM, Lonni J Friedman wrote:
>>> On Mon, Sep 12, 2011 at 6:39 PM, Tatsuo Ishii wrote:
>>>>>> I couldn't find anything possibly related to your problem at a first
>>
x27;d really appreciate some input on how to debug this.
On Fri, Sep 9, 2011 at 8:11 AM, Lonni J Friedman wrote:
> No one else has experienced this or has suggestions how to debug it?
>
> On Wed, Sep 7, 2011 at 12:49 PM, Lonni J Friedman wrote:
>> Greetings,
>> I'm running
On Wed, Sep 14, 2011 at 3:56 PM, Tatsuo Ishii wrote:
>> On Tue, Sep 13, 2011 at 8:48 PM, Tatsuo Ishii wrote:
>>>> On Mon, Sep 12, 2011 at 6:47 PM, Lonni J Friedman
>>>> wrote:
>>>>> On Mon, Sep 12, 2011 at 6:39 PM, Tatsuo Ishii wrote:
>>>&
>>
>>
>> I'd really appreciate some input on how to debug this.
>>
>>
>> On Fri, Sep 9, 2011 at 8:11 AM, Lonni J Friedman wrote:
>>> No one else has experienced this or has suggestions how to debug it?
>>>
>>> On Wed, Sep 7, 2011 at 1
On Wed, Sep 14, 2011 at 4:22 PM, Tatsuo Ishii wrote:
I'm pretty sure that's not the case as the messages stop whenever
pgpool isn't running, they were not present prior to using pgpool, and
pg_hba.conf is setup such that the database servers only accept
connections from each ot
On Wed, Sep 14, 2011 at 6:00 PM, Tatsuo Ishii wrote:
>> On Wed, Sep 14, 2011 at 4:22 PM, Tatsuo Ishii wrote:
>> I'm pretty sure that's not the case as the messages stop whenever
>> pgpool isn't running, they were not present prior to using pgpool, and
>> pg_hba.conf is setup such that
On Thu, Sep 15, 2011 at 8:57 AM, Johnny Tan wrote:
> On Wed, Sep 14, 2011 at 9:12 PM, Lonni J Friedman wrote:
>> On Wed, Sep 14, 2011 at 6:00 PM, Tatsuo Ishii wrote:
>>>> On Wed, Sep 14, 2011 at 4:22 PM, Tatsuo Ishii wrote:
>>>>>>>> I'm pr
gt; PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ 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 ? R Sep13 51:40
>> pgpool: lfriedman nightly 10.31.96.84(61698) idle
>
6 0x in ?? ()
>> (gdb) cont
>> Continuing.
>>
>> ###
>>
>> The entire session completely hung at the end there.
>>
>>
>> On Wed, Sep 14, 2011 at 3:57 PM, Tatsuo Ishii wrote:
>>> Please use gdb. For exa
Nevermind, I figured out what I was doing wrong. Now I just need for
this to hang again.
On Tue, Sep 20, 2011 at 9:08 AM, Lonni J Friedman wrote:
> I tried to do that, but pgpool refuses to start reporting:
> -bash: /usr/lib/debug/usr/sbin/pgpool.debug: bad ELF interpreter: No
> suc
Greetings,
I'm running pgpool-II-3.0.4 on a Linux-x86_64 server, which is load
balancing for a cluster of 3 PostgreSQL-9.0.4 servers (1 master, 2
standby). I'm using pgpool for load balancing only (not managing
streaming replication or failover). Last night, pgpool started
segfaulting repeatedly,
On Thu, Sep 22, 2011 at 8:58 AM, Tatsuo Ishii wrote:
>> Greetings,
>> I'm running pgpool-II-3.0.4 on a Linux-x86_64 server, which is load
>> balancing for a cluster of 3 PostgreSQL-9.0.4 servers (1 master, 2
>> standby). I'm using pgpool for load balancing only (not managing
>> streaming replicat
On Thu, Sep 22, 2011 at 5:18 PM, Tatsuo Ishii wrote:
>> I checked a second of the coredumps, and it has the same backtrace.
>> Let me know if you need anything else. thanks!
>
> Thanks. Can you show me pgpool log when DNS failed and pgpool died in
> segfaulting?
2011-09-21 16:23:00 ERROR: pid 26
On Fri, Sep 23, 2011 at 7:29 AM, Tatsuo Ishii wrote:
>> On Thu, Sep 22, 2011 at 5:18 PM, Tatsuo Ishii wrote:
I checked a second of the coredumps, and it has the same backtrace.
Let me know if you need anything else. thanks!
>>>
>>> Thanks. Can you show me pgpool log when DNS failed and
On Fri, Sep 23, 2011 at 3:43 PM, Tatsuo Ishii wrote:
>>> Ok. I think this is the cause of the problem:
>>>
2011-09-21 16:23:11 LOG: pid 23588: find_primary_node:
pgpool_walrecrunning does not exist
>>>
>>> I think you did not install pgpool_walrecrunning() on DB node 2. In
>>> this cas
On Fri, Sep 23, 2011 at 4:24 PM, Tatsuo Ishii wrote:>
> No. Just try:
>
> $ psql -h cuda-db0 -U postgres -d postgres -c "select pgpool_walrecrunning();"
>
> If it succeeds, you are done.
Returned true. thanks for your help!
___
Pgpool-general mailing l
Greetings,
I'm using pgpool-3.0.4 to load balance queries between 3 PostgreSQL
servers. I'm occasionally seeing some "unable to parse the query'
errors in the pgpool log for queries that are malformed from a client.
The problem is that pgpool doesn't log the client IP or hostname, so
its rather d
On Sun, Nov 6, 2011 at 5:58 PM, Tatsuo Ishii wrote:
>> Greetings,
>> I'm using pgpool-3.0.4 to load balance queries between 3 PostgreSQL
>> servers. I'm occasionally seeing some "unable to parse the query'
>> errors in the pgpool log for queries that are malformed from a client.
>> The problem i
On Sun, Nov 20, 2011 at 4:27 AM, Tatsuo Ishii wrote:
By enabling "log_connections" you have your client IP and pgpool child
pid in your log. Since the log for "unable parse..." includes pgpool
child pid, you can get client IP by checking pgpool child pid.
LOG: pid 4327:
t main.c:549
(gdb) cont
Continuing.
On Tue, Sep 20, 2011 at 9:25 AM, Lonni J Friedman wrote:
> Nevermind, I figured out what I was doing wrong. Now I just need for
> this to hang again.
>
> On Tue, Sep 20, 2011 at 9:08 AM, Lonni J Friedman wrote:
>> I tried to do tha
Greetings,
I'm running PostgreSQL-9.0.4 on a Linux-x86_64 cluster with 1 master,
and two streaming replication slaves. Since late yesterday, the load
on the server has been noticably higher (5.00+) than normal (generally
under 1.00). I investigated, and found that for the past ~18 hours,
there's
Thanks for your reply. No, I do not regularly schedule any vacuum
cronjobs, as I was led to believe that this was no longer necessary
from past discussions on this and other mailing lists. I had been
running vacuum full as frequently as twice/month earlier this year,
but it was basically making t
*sigh* I thought that I did, but clearly I did not. Sorry about the noise.
On Tue, Nov 22, 2011 at 6:16 PM, Tatsuo Ishii wrote:
> I think you'd better post to pgsql-general since your question is
> nothing related to pgpool.
___
Pgpool-general mailing
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 wrote:
> This hadn'
On Wed, Nov 23, 2011 at 10:42 PM, Tatsuo Ishii 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 to know wher
40 matches
Mail list logo
