pgpool does not create run /var/run/postgresql directory on reboot

Bug #314837 reported by John-Scott Atlakson
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pgpool2 (Ubuntu)
Fix Released
Undecided
Unassigned
Declined for Intrepid by Daniel T Chen

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.d/postgresql-8.3 script) I'll attach that.

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
Revision history for this message
John-Scott Atlakson (john-scott-atlakson) wrote :

Applying the attached patch to /etc/init.d/pgpool2 seems to fix the problem for me.

description: updated
Revision history for this message
John-Scott Atlakson (john-scott-atlakson) wrote :

Sigh. Now I see that I've submitted this bug against 'pgpool' and not 'pgpool2'. Not clear to me from this interface if I can change this, but trust someone can figure it out.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

You can change the package by clicking on the arrow next to it. I've done taht for you ;)

Revision history for this message
Preston Hunt (me-prestonhunt) wrote :

Patch works great. Recommend updating the package to implement this patch as soon as possible. Without the patch, pgpool fails completely on any system that doesn't have Postgres installed. In addition to failing to start, the init.d script reports "OK", even though the script has failed.

Revision history for this message
Marc Gariépy (mgariepy) wrote :

I am also affected by this issue, i have integrated the patch in the init script and had the package rebuild.

It is now avalaible in my ppa for hardy. if someone need it to be build for another distro, just ask I will be glad to do it.

https://launchpad.net/~mgariepy/+archive/ppa

Revision history for this message
Elliot Murphy (statik) wrote :

It looks like this issue was probably fixed in Ubuntu 9.10, in pgpool2 (2.2.3-0ubuntu2)

Daniel T Chen (crimsun)
Changed in pgpool2 (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.