Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31600 - [systemd-arch-units] systemd init script for PostgreSQL fails if PGROOT is unset

Attached to Project: Community Packages
Opened by Moritz Bunkus (mbunkus) - Tuesday, 18 September 2012, 13:57 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 18 September 2012, 14:04 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Installing PostgreSQL and systemd works well. However, the default PostgreSQL installation leaves the PGROOT variable in /etc/conf.d/postgresql commented out with the comment that "/var/lib/postgres" is the default setting anyway.

Unfortunately the systemd script that tries to initialize the PostgreSQL database, /usr/lib/systemd/scripts/postgresql-initdb, doesn't know about that and uses $PGROOT as-is resulting in empty symlink target when the postgres.service is started.

Additional info:

* systemd-arch-units 20120704-5
* postgresql 9.1.4-1
* Default content in /etc/conf.d/postgres, meaning these lines:

## Default data directory location
#PGROOT="/var/lib/postgres"

Steps to reproduce:

On a clean system:
- install systemd, systemd-arch-units, postgresql
- start PostgreSQL with "systemctl start postgresql.service"
- watch it fail and observe the failed symlink due to an empty target in "systemctl status postgresql.service"
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 18 September 2012, 14:04 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#30262 

Loading...