FS#31304 - [postgresql] can't start after switching to systemd

Attached to Project: Arch Linux
Opened by ajes (ajes) - Monday, 27 August 2012, 10:31 GMT
Last edited by Dan McGee (toofishes) - Saturday, 15 September 2012, 16:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
After swtiching to systemd, postgres don't start.
# systemctl status postgresql.service
postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled)
Active: failed (Result: exit-code) since Mon, 27 Aug 2012 12:27:39 +0200; 12s ago
Process: 3877 ExecStart=/bin/su - postgres -m -c /usr/bin/pg_ctl -s -D /var/lib/postgres/data start (code=exited, status=0/SUCCESS)
Process: 3931 ExecStartPre=/usr/lib/systemd/scripts/postgresql-initdb (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/postgresql.service

Aug 27 12:27:39 msi postgres[3931]: Creating symlink /var/lib/postgres ->
Aug 27 12:27:39 msi postgres[3931]: ln: failed to create symbolic link ‘/var/lib/postgres’ -> ‘’:...ct

From journalctl:
Aug 27 12:27:39 msi postgres[3931]: Creating symlink /var/lib/postgres ->
Aug 27 12:27:39 msi postgres[3931]: ln: failed to create symbolic link ‘/var/lib/postgres’ -> ‘’: No such file or directory
Aug 27 12:27:39 msi systemd[1]: postgresql.service: control process exited, code=exited status=1
Aug 27 12:27:39 msi systemd[1]: Unit postgresql.service entered failed state.


Additional info:
systemd 189-2
postgresql 9.1.4-2

Steps to reproduce:
Switch to systemd.
# systemctl enable postgresql.service
# systemctl start postgresql.service
This task depends upon

Closed by  Dan McGee (toofishes)
Saturday, 15 September 2012, 16:44 GMT
Reason for closing:  Won't fix
Additional comments about closing:  New strategy in latest built package, not using this script anymore.
Comment by ajes (ajes) - Monday, 27 August 2012, 10:34 GMT
Ok, fixed by uncommenting PGROOT in /etc/conf.d/postgresql
Comment by Alen Skondro (alesko) - Wednesday, 29 August 2012, 22:20 GMT
I had the same error. this helped me! Thank you.

Loading...