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#28913 - [systemd-arch-units] postgresql.service fails to start

Attached to Project: Community Packages
Opened by Wieland Hoffmann (Mineo) - Wednesday, 14 March 2012, 17:49 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 14 April 2012, 14:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I guess the problem is the PGROOT variable in https://projects.archlinux.org/svntogit/packages.git/tree/trunk/postgresql.confd?h=packages/postgresql causing the symlinking to fail.

Additional info:
* package version(s)
local/systemd-arch-units 20120311-1
Arch specific Systemd unit files
local/postgresql 9.1.3-1
A sophisticated object-relational DBMS

Steps to reproduce:
» sudo systemctl start postgresql.service
Job failed. See system journal and 'systemctl status' for details.

» sudo systemctl status postgresql.service
postgresql.service - PostgreSQL database server
Loaded: loaded (/lib/systemd/system/postgresql.service; disabled)
Active: failed (Result: exit-code) since Wed, 14 Mar 2012 18:45:33 +0100; 7s ago
Process: 9913 ExecStartPre=/lib/systemd/scripts/postgresql-initdb (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/postgresql.service

Mar 14 18:45:33 slartibartfass postgres[9913]: Creating symlink /var/lib/postgres ->
Mar 14 18:45:33 slartibartfass postgres[9913]: [85B blob data]
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 14 April 2012, 14:10 GMT
Reason for closing:  Won't fix
Additional comments about closing:  See comments
Comment by Dave Reisner (falconindy) - Thursday, 15 March 2012, 19:21 GMT
Right, so what's the problem? Sounds to me like you didn't uncomment the var and set it...
Comment by Wieland Hoffmann (Mineo) - Thursday, 15 March 2012, 21:11 GMT
The postgresql script in /etc/rc.d works around this by defaulting to the /var/lib/postgresql, that's why postgresql.install also doesn't say anything about modifying the conf file. I would expect the systemd unit to be on par with the file provided by the postgresql package itself, especially if I do not actually want to modify the location.

(One reason for reporting this here and not on github is that I'm not sure if the solution might be as easy as uncommenting the line by default)
Comment by Gereon Schomber (IncredibleLaser) - Friday, 13 April 2012, 18:38 GMT
  • Field changed: Percent Complete (100% → 0%)
The reason for failing is not only due to the variables not being enabled by default, but also because of an error in postgresql.service: it contains "ExecStartPre=/lib/systemd/scripts/postgresql-initdb", however the script is located at "/usr/lib/systemd/scripts/postgresql-initdb". Changing this in postgresql.service enables postgresql to start.
Comment by Dave Reisner (falconindy) - Friday, 13 April 2012, 23:15 GMT
Why was this reopened? systemd-arch-units-20120410 references the correct path...
Comment by Jelle van der Waa (jelly) - Saturday, 14 April 2012, 09:26 GMT
@IncredibleLaser pacman -Q systemd-arch-units
Comment by Wieland Hoffmann (Mineo) - Saturday, 14 April 2012, 09:32 GMT
Even if what IncredibleLaser describes is still a problem, I opened this bug report for something completely different (I still think solving the original problem I described is worth doing, especially if the unit file will be shipped with the postgresl package after the current discussion on arch-dev-pub).
Comment by Dave Reisner (falconindy) - Saturday, 14 April 2012, 14:10 GMT
Please open a separate bug report if this is actually a problem (it isn't).

Loading...