pgpool does not create run /var/run/postgresql directory on reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pgpool2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: pgpool2
I'm a running pgpool2 on an application server which does not itself run PostgreSQL server (the server is on a separate machine). After installing pgpool2, it creates a dir /var/run/postgresql which is owned by the postgres user. The default configuration (/etc/pgpool.conf) looks for the pid file in this directory. However, on system reboot, this directory is destroyed and never recreated which prevent the pgpool2 process from starting. If I can get a patch working for the init script (cribbing from the /etc/init.
Edit: I thought that since I was posting the bug from the /ubuntu/intrepid/ page that it would automatically note that I'm using Intrepid, but in case it's not obvious, I'm using the default pgpool2 v1.3-2 with Intrepid Server.
description: | updated |
description: | updated |
Changed in pgpool2 (Ubuntu): | |
status: | New → Fix Released |
Applying the attached patch to /etc/init.d/pgpool2 seems to fix the problem for me.