[Pgpool-general] Why pgpool II always refuses connections?

[Zhidong She]

pgpool can accept new connection from psql,  and can finish pgbench test
without "-C" option.
I also can run "-C" again without restart pgpool, but it always refused new
connection after 28232 tries.

Just now I setup a new pgpool platform in our lab, we got same failure with
pgbench -C.
Thanks very much for your care.

On Tue, Dec 21, 2010 at 5:35 PM, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> After failure of pgbench -C, does pgpool still accept connections from
> psql?
> Or does it become unusable until restarting?
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese: http://www.sraoss.co.jp
>
> > No any error on message or pgpool log.
> > Our platform is centos5.8
> > Kernel is: 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64
> x86_64
> > x86_64 GNU/Linux
> >
> > On Tue, Dec 21, 2010 at 5:27 PM, Tatsuo Ishii <ishii at sraoss.co.jp>
> wrote:
> >
> >> Is there any error message in pgpool log or /var/log/messages?
> >> What is the platform are you running on?
> >> --
> >> Tatsuo Ishii
> >> SRA OSS, Inc. Japan
> >> English: http://www.sraoss.co.jp/index_en.php
> >> Japanese: http://www.sraoss.co.jp
> >>
> >> > Hi all,
> >> >
> >> > We are testing pgpool II by pgbench, when we use below command to do
> the
> >> > test, the pgpool runs ok.
> >> > /opt/PostgreSQL/8.4/bin/pgbench -t 2000 -c 20 -h 172.17.3.10 -p 9999
> -U
> >> > postgres pgbench
> >> >
> >> > But if we add "-C" option, which means to establish new connection for
> >> every
> >> > transaction, the pgpool II will always refuse the connections after
> about
> >> > 28230 successful connection.
> >> > /opt/PostgreSQL/8.4/bin/pgbench -t 2000 -C -c 20 -h 172.17.3.10 -p
> 9999
> >> -U
> >> > postgres pgbench
> >> >
> >> > I tried many times, and the number of transactions actually processed
> is
> >> > always at 28232 or so.
> >> >
> >> > Please see below the detail infomation, any pgpool arguments need to
> be
> >> > adjusted to avoid this issue?
> >> >
> >> > Thanks very much for your help!!!
> >> >
> >> >
> >>
> =======================================================================================
> >> > [root at ucs09 shell]# /opt/PostgreSQL/8.4/bin/pgbench -C -t 2000 -c 20
> -h
> >> > 172.17.3.10 -p 9999 -U postgres pgbench
> >> > starting vacuum...end.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 12 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 13 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 3 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 0 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 16 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 8 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 4 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 5 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 1 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 9 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 10 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 2 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 6 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 11 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 15 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 14 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 7 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 17 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 18 aborted in establishing connection.
> >> > Connection to database "pgbench" failed:
> >> > could not connect to server: Cannot assign requested address
> >> >         Is the server running on host "172.17.3.10" and accepting
> >> >         TCP/IP connections on port 9999?
> >> > Client 19 aborted in establishing connection.
> >> > transaction type: TPC-B (sort of)
> >> > scaling factor: 20
> >> > query mode: simple
> >> > number of clients: 20
> >> > number of transactions per client: 2000
> >> > number of transactions actually processed: 28232/40000
> >> > tps = 841.807364 (including connections establishing)
> >> > tps = 2069.595197 (excluding connections establishing)
> >>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pgfoundry.org/pipermail/pgpool-general/attachments/20101221/4a78a698/attachment.html>