Re: Service pgpool
Hi, > below my problem about daemon : > > Jun 07 14:06:45 vm02 systemd[1]: Failed to start SYSV: Starts and stops the > pgpool daemon. > Jun 07 14:06:45 vm02 systemd[1]: Unit pgpool-II-10.service entered failed > state. > Jun 07 14:06:45 vm02 systemd[1]: pgpool-II-10.service failed. Could you show more error messages about systemd? As a common case, starting Pgpool-II failed due to missing the socket file directory which is specified in pgpool.conf. By the way as Joshua has already suggested, probably It would better to make questions in the Pgpool-II dedicated mailing list. On Thu, 7 Jun 2018 20:16:19 +0200 Jean Claude wrote: > Hi all, > > below my problem about daemon : > > Jun 07 14:06:45 vm02 systemd[1]: Failed to start SYSV: Starts and stops the > pgpool daemon. > Jun 07 14:06:45 vm02 systemd[1]: Unit pgpool-II-10.service entered failed > state. > Jun 07 14:06:45 vm02 systemd[1]: pgpool-II-10.service failed. > > Can you help me? > > Thanks a lot -- Bo Peng SRA OSS, Inc. Japan
Re: Service pgpool
Hi, > Jun 08 04:40:17 asa-pgpool02 pgpool-II-10[30787]: Starting pgpool-II-10 > service: pgpool is already running with pid 4285 [FAILED] It seemed like Pgpool-II is already started. Did you start Pgpool-II twice? Also may I ask some questions? - How did you install Pgpool-II, using source code or RPM packages? - If you installed Pgpool-II by using RPM packages, did you use the RPM packages from PGDG repository provided by PostgreSQL community or from pgpool yum repository provided by Pgpool-II community? - Could you provide the RPM package name? - How did you start Pgpool-II? It seemed like you started Pgpool-II with systemd, but the init script is used. Normally on RHEL 7.x the systemd service is used to start a service. On Fri, 8 Jun 2018 10:47:34 +0200 Jean Claude wrote: > Hi Bo Peng, > > Thank you for your feedback. > > You can find the status of my service below : > > [root@asa-pgpool02 tmp]# systemctl status pgpool-II-10.service > ● pgpool-II-10.service - SYSV: Starts and stops the pgpool daemon >Loaded: loaded (/etc/rc.d/init.d/pgpool-II-10; bad; vendor preset: > disabled) >Active: failed (Result: exit-code) since Fri 2018-06-08 04:40:17 EDT; > 5min ago > Docs: man:systemd-sysv-generator(8) > Process: 30787 ExecStart=/etc/rc.d/init.d/pgpool-II-10 start > (code=exited, status=1/FAILURE) > > Jun 08 04:40:17 asa-pgpool02 systemd[1]: Starting SYSV: Starts and stops > the pgpool daemon... > Jun 08 04:40:17 asa-pgpool02 pgpool-II-10[30787]: Starting pgpool-II-10 > service: pgpool is already running with pid 4285 [FAILED] > Jun 08 04:40:17 asa-pgpool02 systemd[1]: pgpool-II-10.service: control > process exited, code=exited status=1 > Jun 08 04:40:17 asa-pgpool02 systemd[1]: Failed to start SYSV: Starts and > stops the pgpool daemon. > Jun 08 04:40:17 asa-pgpool02 systemd[1]: Unit pgpool-II-10.service entered > failed state. > Jun 08 04:40:17 asa-pgpool02 systemd[1]: pgpool-II-10.service failed. > [root@asa-pgpool02 tmp]# > > Thanks > > > > 2018-06-08 4:22 GMT+02:00 Bo Peng : > > > Hi, > > > > > below my problem about daemon : > > > > > > Jun 07 14:06:45 vm02 systemd[1]: Failed to start SYSV: Starts and stops > > the pgpool daemon. > > > Jun 07 14:06:45 vm02 systemd[1]: Unit pgpool-II-10.service entered > > failed state. > > > Jun 07 14:06:45 vm02 systemd[1]: pgpool-II-10.service failed. > > > > Could you show more error messages about systemd? > > > > As a common case, starting Pgpool-II failed due to > > missing the socket file directory which is specified > > in pgpool.conf. > > > > By the way as Joshua has already suggested, probably It > > would better to make questions in the Pgpool-II dedicated > > mailing list. > > > > On Thu, 7 Jun 2018 20:16:19 +0200 > > Jean Claude wrote: > > > > > Hi all, > > > > > > below my problem about daemon : > > > > > > Jun 07 14:06:45 vm02 systemd[1]: Failed to start SYSV: Starts and stops > > the > > > pgpool daemon. > > > Jun 07 14:06:45 vm02 systemd[1]: Unit pgpool-II-10.service entered failed > > > state. > > > Jun 07 14:06:45 vm02 systemd[1]: pgpool-II-10.service failed. > > > > > > Can you help me? > > > > > > Thanks a lot > > > > > > -- > > Bo Peng > > SRA OSS, Inc. Japan > > > > -- Bo Peng SRA OSS, Inc. Japan
Re: Add to watchdog cluster request is rejected by node
Hi, I think it would be better to make questions in the Pgpool-II dedicated mailing list pgpool-gene...@pgpool.net. > 3240: WARNING: checking setuid bit of if_up_cmd > Jun 11 08:57:04 asa-pgpool02 pgpool[3240]: [1-2] 2018-06-11 08:57:04: pid > 3240: DETAIL: ifup[/sbin/ip] doesn't have setuid bit It seems like that the parameters "if_up_cmd" and "if_down_cmd" are not set correctly Please make sure you set correct network interface name. For example, if your network interface name is "ens192", you need set that like: --- if_up_cmd = 'ip addr add $_IP_$/24 dev ens192 label ens192:0' if_down_cmd = 'ip addr del $_IP_$/24 dev ens192' arping_cmd = 'arping -U $_IP_$ -w 1 -I ens192' --- On Mon, 11 Jun 2018 15:06:35 +0200 Jean Claude wrote: > Hi, > > The following error is a bug ? > > Jun 11 08:57:04 asa-pgpool02 pgpool[3240]: [1-1] 2018-06-11 08:57:04: pid > 3240: WARNING: checking setuid bit of if_up_cmd > Jun 11 08:57:04 asa-pgpool02 pgpool[3240]: [1-2] 2018-06-11 08:57:04: pid > 3240: DETAIL: ifup[/sbin/ip] doesn't have setuid bit > Jun 11 08:57:04 asa-pgpool02 pgpool[3240]: [2-1] 2018-06-11 08:57:04: pid > 3240: WARNING: checking setuid bit of if_down_cmd > Jun 11 08:57:04 asa-pgpool02 pgpool[3240]: [2-2] 2018-06-11 08:57:04: pid > 3240: DETAIL: ifdown[/sbin/ip] doesn't have setuid bit > Jun 11 08:57:04 asa-pgpool02 pgpool[3240]: [3-1] 2018-06-11 08:57:04: pid > 3240: LOG: waiting for watchdog to initialize > Jun 11 08:57:04 asa-pgpool02 pgpool[3241]: [3-1] 2018-06-11 08:57:04: pid > 3241: LOG: setting the local watchdog node name to " > asa-pgpool02.adm.cacc.ch:5432 Linux asa-pgpool02" > Jun 11 08:57:04 asa-pgpool02 pgpool[3241]: [4-1] 2018-06-11 08:57:04: pid > 3241: LOG: watchdog cluster is configured with 1 remote nodes > Jun 11 08:57:04 asa-pgpool02 pgpool[3241]: [5-1] 2018-06-11 08:57:04: pid > 3241: LOG: watchdog remote node:0 on asa-pgpool01.adm.cacc.ch:9000 > Jun 11 08:57:04 asa-pgpool02 pgpool[3241]: [6-1] 2018-06-11 08:57:04: pid > 3241: LOG: interface monitoring is disabled in watchdog > Jun 11 08:57:04 asa-pgpool02 pgpool[3241]: [7-1] 2018-06-11 08:57:04: pid > 3241: LOG: watchdog node state changed from [DEAD] to [LOADING] > Jun 11 08:57:04 asa-pgpool02 pgpool[3241]: [8-1] 2018-06-11 08:57:04: pid > 3241: LOG: new outbound connection to asa-pgpool01.adm.cacc.ch:9000 > Jun 11 08:57:04 asa-pgpool02 pgpool[3241]: [9-1] 2018-06-11 08:57:04: pid > 3241: *FATAL: Add to watchdog cluster request is rejected by node > "asa-pgpool01.adm.cacc.ch:9000 <http://asa-pgpool01.adm.cacc.ch:9000>"* > > pgpool-II version : > pgpool-II version 3.7.3 (amefuriboshi) > > Thanks. -- Bo Peng SRA OSS, Inc. Japan
Re: HA setup with pg pool in docker
Hello, On Wed, 22 Jul 2020 13:29:31 +0800 Vasu Madhineni wrote: > We are planning to build a HA setup with pgpool in docker, Could you please > let us know prerequisites for it. > > 1. How many servers are needed for this?, can we plan with 2 servers like > below config. >Primary instance and pgpool in two different docker containers in server > 1 and standby instance in docker container server 2. It depends on your requirements. You can create 3 containers (pgpool, primary and standby) on one server or on different servers. > 2. User requirement: any user needs password less authentication between > nodes. It is possible by configuring pool_hba.conf (Pgpool-II) and pg_hba.conf (PostgreSQL). > 3. Port or firewall rules between servers. Pgpool port and PostgreSQL port need to be accessible. > 4. If planning to create a network bridge between all docker containers > between 2 servers will be any prerequisites for that. You need to make sure all containers can connect to each other. -- Bo Peng SRA OSS, Inc. Japan
Re: Pgpool in docker container
Hello, > Hi All, > > Planning to build standalone postgres and with pgpool as connection pooler > in docker containers. > Shall we try option like installing pgpool in one docker container and > postgres in another docker container, is it possible? Yes. It is possible to install Pgpool-II and PostgreSQL in different containers. > Thanks in advance. > > Regards, > Vasu Madhineni -- Bo Peng SRA OSS, Inc. Japan
Re: Pgpool2 Service Won't Start
Hi, On Fri, 16 Oct 2020 14:33:33 -0700 (MST) alanhi wrote: > Hi, > > Hi, my pgpool status indicates that it failed even after trying to restart > the service. What can I check to see what configurations may be causing > this? Thanks. > > Alan > > ● pgpool2.service - pgpool-II >Loaded: loaded (/lib/systemd/system/pgpool2.service; enabled; vendor > preset: enabled) >Active: failed (Result: exit-code) since Fri 2020-10-16 10:16:21 HST; > 10min ago > Docs: man:pgpool(8) > Process: 20052 ExecStart=/usr/sbin/pgpool -n (code=exited, status=3) > Main PID: 20052 (code=exited, status=3) You may go to https://www.pgpool.net/mailman/listinfo/pgpool-general to ask questions. Could you share the result of "systemctl status pgpool" and pgpool log? > -- > Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html > > -- Bo Peng SRA OSS, Inc. Japan
Re: [pgpool-general: 9132] Pgpool delegate IP is not reachable from the remote host
Hi, The default value of "if_up_cmd" is: /usr/bin/sudo /sbin/ip addr add $_IP_$/24 dev eth0 label eth0:0 If the network interface "eth0" exists on Pgpool-II servers, the command may run successfully. I think the default value of "if_up_cmd" was executed to bring up the VIP. > Hello everyone. > > We have a pgpool & postgres setup made as per the given example > <https://www.pgpool.net/docs/latest/en/html/example-cluster.html> > > We haven't configured the *if_up_cmd, if_down_cmd & **arping_cmd* in > pgpool.conf > (we commented it out on purpose). We enabled the *delegate_ip* and assigned > a unused IP. > > While we bringing up the pgpool the log shows VIP is successfully UP via > if_up_cmd, how is this happening? any default way is considering the > if_up_cmd to bring the VIP? > > > > *2024-06-18 08:27:02.735: watchdog_utility pid 102493: LOG: successfully > acquired the delegate IP:"10.127.1.20"2024-06-18 08:27:02.735: > watchdog_utility pid 102493: DETAIL: 'if_up_cmd' returned with > success2024-06-18 08:27:02.735: watchdog pid 102378: LOG: watchdog > escalation process with pid: 102493 exit with SUCCESS.* > > NOTE: We run into some situation so that we disabled the if_* commands in > the configuration and started pgpool, but VIP is getting acquired by the > leader pgpool node even the if_* commands are not used in pgpool.conf file. > > Can anyone explain how the VIP works in pgpool watchdog > > Thank you > Regards > Mukesh Tanuku -- Bo Peng SRA OSS LLC TEL: 03-5979-2701 FAX: 03-5979-2702 URL: https://www.sraoss.co.jp/
Re: Proposed Chinese Translation of Community Code of Conduct
Hello, The Chinese translation looks good. regards, Bo Peng On Fri, 21 May 2021 09:58:12 -0700 Stacey Haysler wrote: > The PostgreSQL Community Code of Conduct Committee has received a draft of > the Chinese translation of the Code of Conduct Policy updated August 18, 2020 > for review. > The English version of the Policy is at: > https://www.postgresql.org/about/policies/coc/ > <https://www.postgresql.org/about/policies/coc/> > > The translation was created by: > Wensheng Zhang (张文升) > The translation was reviewed by: > Yandong Yao (姚延栋) > > The proposed translation is attached as a both a text file and a PDF to this > message. > > If you have any comments or suggestions for the translation, please bring > them to our attention no later than 5:00 PM Pacific Time on May 28, 2021. > > Thank you. > > Regards, > Stacey > > Stacey Haysler > Chair > PostgreSQL Community Code of Conduct Committee > > -- Bo Peng SRA OSS, Inc. Japan
