View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000788 | Pgpool-II | Bug | public | 2023-02-23 07:27 | 2023-03-02 14:50 |
| Reporter | Cidy Long | Assigned To | pengbo | ||
| Priority | high | Severity | major | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Platform | Linux | OS | Centos Stream | OS Version | 9 |
| Product Version | 4.4.2 | ||||
| Summary | 0000788: pgpool can't access /var/run directory to open pid file and create watchdog command server socket after reboot | ||||
| Description | Compile and install pgpool-II 4.4.2 with PostgreSQL 15.2 and openssl Configure every thing by following [https://www.pgpool.net/docs/44/en/html/example-cluster.html] create and update pgpool.service to support custom configure (/usr/local/bin), enable and start system service by run [systemctl start pgpool.service] not started properly, error found as: FATAL: could not open pid file "/var/run/pgpool/pgpool.pid" FATAL: failed to create watchdog command server socket DETAIL: bind on "/var/run/postgresql/.s.PGPOOLWD_CMD.9000" failed with reason: "No such file or directory" manually create directory under /var/run/pgpool and /var/run/postgresql and change their owner to postgres restart pgpool system service pgpool started properly but after reboot servers, pgpool not start again. Check error. previous manually created directories /var/run/postgresql and /var/run/pgpool disappeared. This is make sense as those directories were created dynamically when system reload. | ||||
| Steps To Reproduce | Compile and install pgpool-II 4.4.2 with PostgreSQL 15.2 and openssl Configure every thing by following [https://www.pgpool.net/docs/44/en/html/example-cluster.html] create and update pgpool.service to support custom configure (/usr/local/bin), enable and start system service by run [systemctl start pgpool.service] not started properly, error found as: FATAL: could not open pid file "/var/run/pgpool/pgpool.pid" FATAL: failed to create watchdog command server socket DETAIL: bind on "/var/run/postgresql/.s.PGPOOLWD_CMD.9000" failed with reason: "No such file or directory" manually create directory under /var/run/pgpool and /var/run/postgresql and change their owner to postgres restart pgpool system service pgpool started properly but after reboot servers, pgpool not start again. Check error. previous manually created directories /var/run/postgresql and /var/run/pgpool disappeared. This is make sense as those directories were created dynamically when system reload. | ||||
| Additional Information | My question is: IS this a bug from pgpool (not enable user postgres to write /var/run) or we can configure Centos Stream 9 to let user postgres to with /var/run directory when they need? Please advise! | ||||
| Tags | No tags attached. | ||||
|
|
No. It is not a bug. If you are installing from source code, you need to create /run/pgpool and create the file under /usr/lib/tmpfiles.d/ to prevent /run/pgpool from disappearing after reboot. For example: # mkdir /run/pgpool # chown postgres:postgres /run/pgpool # cat /usr/lib/tmpfiles.d/pgpool.conf ------ d /run/pgpool 0755 postgres postgres - ------ |
