[pgpool-general: 7014] Re: Pgpool-II-4.1.1 and Ubuntu 20.04
Wolf Schwurack
wolf at uen.org
Tue May 12 00:26:31 JST 2020
Hello
I'm not using IPv6
I attached pgpool.conf file and all pgpool processes running after I started pgpool
Start pgpool command
# /usr/local/bin/pgpool -n -D -f /usr/local/etc/pgpool.conf > /var/log/pgpool/pgpool.log 2>&1 &
This shows no watchdog IP after starting pgpool
root at pgtest-01:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:50:56:b3:d3:58 brd ff:ff:ff:ff:ff:ff
inet 10.11.0.205/24 brd 10.11.0.255 scope global ens160
valid_lft forever preferred_lft forever
If I try to connect to postgres using watchdog IP
postgres at pgtest-01:~$ psql -h 10.11.0.204 -p 9999 -U postgres
psql: error: could not connect to server: could not connect to server: Connection refused
Is the server running on host "10.11.0.204" and accepting
TCP/IP connections on port 9999?
Now I add watchdog IP from command line
root at pgtest-01:~# ip addr add 10.11.0.204/24 dev ens160 label ens160:1
root at pgtest-01:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:50:56:b3:d3:58 brd ff:ff:ff:ff:ff:ff
inet 10.11.0.205/24 brd 10.11.0.255 scope global ens160
valid_lft forever preferred_lft forever
inet 10.11.0.204/24 scope global secondary ens160:1
valid_lft forever preferred_lft forever
I can connect to postgres after entering watchdog IP from command line
root at pgtest-01:~# su - postgres
postgres at pgtest-01:~$ psql -h 10.11.0.204 -p 9999 -U postgres
psql (12.2 (Ubuntu 12.2-4))
Type "help" for help.
postgres=#
On 5/11/20, 12:41 AM, "Bo Peng" <pengbo at sraoss.co.jp> wrote:
Hello,
On Mon, 11 May 2020 14:59:42 +0900
Bo Peng <pengbo at sraoss.co.jp> wrote:
> Hello,
>
> On Thu, 7 May 2020 18:10:20 +0000
> Wolf Schwurack <wolf at uen.org> wrote:
>
> > I have setup some new Ubunut 20.04 hosts with Pgpool-II-4.1.1 using watchdog but unable to get watchdog to work on Ubuntu 20.04
> >
> >
> > 2020-05-07 11:50:11: pid 7727: LOG: Setting up socket for :::9999
> >
> > 2020-05-07 11:50:11: pid 7727: LOG: perhaps failed to create INET domain socket
> >
> > 2020-05-07 11:50:11: pid 7727: DETAIL: socket(::) failed: "Address family not supported by protocol"
>
> Pgpool-II watchdog doesn't support for IPv6.
> It is not pgpool's issue.
> You need to check your network setting.
Sorry. The error above doesn't cause this watchdog issue.
It seems that watchdog wasn't started.
Could you send more log including watchdog process.
> > 2020-05-07 11:50:11: pid 7727: LOG: find_primary_node_repeatedly: waiting for finding a primary node
> >
> > 2020-05-07 11:50:11: pid 7727: LOG: find_primary_node: primary node is 0
> >
> > 2020-05-07 11:50:11: pid 7727: LOG: find_primary_node: standby node is 1
> >
> > 2020-05-07 11:50:11: pid 7727: LOG: pgpool-II successfully started. version 4.1.1 (karasukiboshi)
> > …
> >
> > 2020-05-07 11:50:23: pid 7731: LOG: Watchdog is shutting down
> >
> > I check for the IP with # ip a – No watchdog started
> >
> >
> > 2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
> >
> > link/ether 00:50:56:b3:d3:58 brd ff:ff:ff:ff:ff:ff
> >
> > inet 10.11.0.205/24 brd 10.11.0.255 scope global ens160
> >
> > valid_lft forever preferred_lft forever
> >
> > To start the secondary IP from the command line I can use
> >
> > ip addr add 10.11.0.204/24 dev ens160 label ens160:1
> >
> > if I put this command in pgpool.conf it doesn’t start watchdog
> >
> > But If I run the command from the command line, It creates the secondary IP for watchdog
> >
> > 2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
> >
> > link/ether 00:50:56:b3:d3:58 brd ff:ff:ff:ff:ff:ff
> >
> > inet 10.11.0.205/24 brd 10.11.0.255 scope global ens160
> >
> > valid_lft forever preferred_lft forever
> >
> > inet 10.11.0.204/24 scope global secondary ens160:1
> >
> > I comment out if_up_cmd and and if_down_cmd in pgpool.conf
> >
> > Then I start pgpool, still get this in pgpool.log
> >
> > 2020-05-07 12:02:12: pid 8130: LOG: perhaps failed to create INET domain socket
> >
> > 2020-05-07 12:02:12: pid 8130: DETAIL: socket(::) failed: "Address family not supported by protocol"
> > but no message that watchdog is down
> >
> > Then I test the connection, it work
> >
> > $ psql -h wd-pgtest -p 9999 -U postgres
> >
> > psql (12.2 (Ubuntu 12.2-4))
> >
> > Type "help" for help.
> >
> >
> >
> > postgres=#
> >
> > My question is why can’t I get the command to work in pgpool.conf?
> >
> > Wolfgang Schwurack
> > Database/System Administrator
> > Utah Education Network
> > 801-587-9444
> > wolf at uen.org<mailto:wolf at uen.org>
> >
>
>
> --
> Bo Peng <pengbo at sraoss.co.jp>
> SRA OSS, Inc. Japan
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
--
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool.conf
Type: application/octet-stream
Size: 43946 bytes
Desc: pgpool.conf
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20200511/e114fe2a/attachment-0001.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: process.txt
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20200511/e114fe2a/attachment-0001.txt>
More information about the pgpool-general
mailing list