[pgpool-general: 4790] Pgpool

Tue Jul 19 06:01:39 JST 2016

HI Support,

I am trying to implement pgpool database/creation and replication with 3 different server, Master/slave and class server.

I am not able to create a database, I am getting the following errors . Your help is much appreciated.
I have changed the pg_hba.conf to the following 

2016-07-18 13:49:57: pid 2974: DETAIL:  Protocol Major: 3 Minor: 0 database: template1 user: openplatform
2016-07-18 13:49:57: pid 2974: DEBUG:  creating new connection to backend
2016-07-18 13:49:57: pid 2974: DETAIL:  connecting 0 backend
2016-07-18 13:49:57: pid 2974: DEBUG:  creating new connection to backend
2016-07-18 13:49:57: pid 2974: DETAIL:  connecting 1 backend
2016-07-18 13:49:57: pid 2974: DEBUG:  creating new connection to backend
2016-07-18 13:49:57: pid 2974: DETAIL:  skipping backend slot 1 because backend_status = 3
2016-07-18 13:49:57: pid 2974: DEBUG:  creating new connection to backend
2016-07-18 13:49:57: pid 2974: DETAIL:  connecting 2 backend
2016-07-18 13:49:57: pid 2974: DEBUG:  SSL is requested but SSL support is not available
2016-07-18 13:49:57: pid 2974: DEBUG:  SSL is requested but SSL support is not available
2016-07-18 13:49:57: pid 2974: DEBUG:  pool_read: read 13 bytes from backend 0
2016-07-18 13:49:57: pid 2974: DEBUG:  pool_read: read 13 bytes from backend 2
2016-07-18 13:49:57: pid 2974: DEBUG:  reading message length
2016-07-18 13:49:57: pid 2974: DETAIL:  slot: 0 length: 12
2016-07-18 13:49:57: pid 2974: DEBUG:  reading message length
2016-07-18 13:49:57: pid 2974: DETAIL:  slot: 2 length: 12
2016-07-18 13:49:57: pid 2974: DEBUG:  authentication backend
2016-07-18 13:49:57: pid 2974: DETAIL:  auth kind:5
2016-07-18 13:49:57: pid 2974: ERROR:  failed to authenticate with backend
2016-07-18 13:49:57: pid 2974: DETAIL:  MD5 authentication is not supported in replication and master-slave modes.
2016-07-18 13:49:57: pid 2974: HINT:  check pg_hba.conf settings on backend node

# If you want to allow non-local connections, you need to add more
# "host" records. In that case you will also need to make pgpool listen
# on a non-local interface via the listen_addresses configuration parameter.
# TYPE  DATABASE    USER        CIDR-ADDRESS          METHOD
# "local" is for Unix domain socket connections only
#local   all             postgres              md5
local   all                  all               trust
# IPv4 local connections:
host    all              postgres            127.0.0.1/32       ident
#host    all              all               ::1/128              md5
host      all             all               100.114.116.68/32    ident
host      all             all               100.114.116.69/32    ident

# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                peer
host    replication     postgres        127.0.0.1/32            ident
#host    replication     postgres        ::1/128                 ident
host     replication     postgres       100.114.116.68/32       ident
host    replication     postgres        100.114.116.69/32        ident

Thanks !
sai

-----Original Message-----
From: pgpool-general-bounces at pgpool.net [mailto:pgpool-general-bounces at pgpool.net] On Behalf Of pgpool-general-request at pgpool.net
Sent: Wednesday, July 13, 2016 8:00 PM
To: pgpool-general at pgpool.net
Subject: pgpool-general Digest, Vol 57, Issue 15

Send pgpool-general mailing list submissions to
	pgpool-general at pgpool.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://www.sraoss.jp/mailman/listinfo/pgpool-general
or, via email, send a message with subject or body 'help' to
	pgpool-general-request at pgpool.net

You can reach the person managing the list at
	pgpool-general-owner at pgpool.net

When replying, please edit your Subject line so it is more specific than "Re: Contents of pgpool-general digest..."

Today's Topics:

   1. [pgpool-general: 4786] Re: listen backlog overflowing
      (Travis Kirstine)

----------------------------------------------------------------------

Message: 1
Date: Wed, 13 Jul 2016 15:54:52 +0000
From: Travis Kirstine <tkirstine at firstbasesolutions.com>
To: Tatsuo Ishii <ishii at postgresql.org>
Cc: "pgpool-general at pgpool.net" <pgpool-general at pgpool.net>
Subject: [pgpool-general: 4786] Re: listen backlog overflowing
Message-ID:
	<7db378c7c1094c1f822920e49f3ea8e1 at MBX12B-IAD3.mex08.mlsrvr.com>
Content-Type: text/plain; charset="us-ascii"

-----Original Message-----
From: Tatsuo Ishii [mailto:ishii at postgresql.org]
Sent: July-12-16 6:56 PM
To: Travis Kirstine <tkirstine at firstbasesolutions.com>
Cc: pgpool-general at pgpool.net
Subject: Re: [pgpool-general: 4782] listen backlog overflowing

> What can cause the backlog to overflow?

Have you actually seen something like this?

535 times the listen queue of a socket overflowed

Yes, I get the message

> I've increased the somaxconn and max_backlog  sysctl parameters.
> 
> net.core.somaxconn = 16384
> net.core.netdev_max_backlog = 16384
> 
> pgpool  conf
> 
> listen_backlog_multiplier = 5
> num_init_children = 40
> max_pool = 5
> child_life_time = 300
> child_max_connections = 0
> connection_life_time = 0
> client_idle_limit = 600
> 
> Any ideas would be great!!!

If so, strange... is the server dedicated for pgpool-II? or do you have another software running on the same server which could use the listen queue?

No the server is not dedicated to pgpool only, postgresql is running on it as well.

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
http://www.pgpool.net/mailman/listinfo/pgpool-general

End of pgpool-general Digest, Vol 57, Issue 15
**********************************************