quasselcore.service systemd unit does not depend on PostgreSQL, causing the core to fail to start if it is configured to use PostgreSQL
Bug #1432161 reported by
Michael Marley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
quassel (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
quasselcore's current systemd unit file does not have Wants or After entries for PostgreSQL, so Quassel will usually/always be started before PostgreSQL is running. If the core is configured to use PostgreSQL for storage, this causes the core to fail to start.
I have attached a debdiff that fixes the problem. The systemd documentation indicates (and I have proven with experimentation) that a Wants or After entry on a non-existent unit will not keep the unit from starting, so this won't cause any problems for people who don't have PostgreSQL installed.
To post a comment you must log in.
Here is a new patch that fixes a couple more issues I found.
First, the systemd unit file did not have Restart=on-failure, which differed from the behavior of the upstart script.
Second, neither the systemd unit file nor the upstart script had support for the DAEMON_OPTS variable from /etc/default/ quasselcore. This made it difficult for administrators to add extra arguments, which is especially true on systemd since the unit file is silently overwritten every time the package is updated.