apacheds.service script not running from systemctl correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apache-directory-server (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hello,
I'm not sure if this is more of a general bug with Systemd/systemctl, but the apacheds.service file doesn't seem to read the EnvironmentFile variable, or at least doesn't act upon the variable therein.
While trying to start the apacheds service from systemctl I get the following errors:
----
bswan@ds:
Failed to start apacheds.service: Unit apacheds.service is not loaded properly: Invalid argument.
See system logs and 'systemctl status apacheds.service' for details.
bswan@ds:
● apacheds.service - Apache Directory Server
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
Nov 30 08:17:18 ds systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Nov 30 08:17:45 ds systemd[1]: [/lib/systemd/
Nov 30 08:17:45 ds systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Nov 30 08:29:27 ds systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Nov 30 08:30:50 ds systemd[1]: [/lib/systemd/
Nov 30 08:30:50 ds systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Nov 30 08:35:54 ds systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Nov 30 08:49:04 ds systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Nov 30 08:59:28 ds systemd[1]: [/lib/systemd/
Nov 30 08:59:28 ds systemd[1]: apacheds.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
----
After much experimentation the work-around to get it working is to just copy the environment variables from /etc/default/
Status changed to 'Confirmed' because the bug affects multiple users.