invoke-rc.d doesn't start freshly installed services which only have an init.d script
Bug #1429035 reported by
Martin Pitt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| sysvinit (Debian) |
Fix Released
|
Unknown
|
|||
| sysvinit (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Bug Description
On a fresh and minimal vivid installation running systemd, install apache2. It won't be running after starting:
$ sudo sh -x /usr/sbin/
+ systemctl --quiet is-system-running
+ sctl_args=
+ systemctl --quiet is-enabled apache2.service
+ [ start = start ]
+ exit 0
That's because of our patch in invoke-rc.d to not start disabled systemd services. But this fails here as after a fresh installation the sysv-generator didn't run yet, so there is no apache2.service. Even after reboot, is-enabled & friends don't take generated units into account.
Related branches
| Changed in sysvinit (Ubuntu): | |
| importance: | Undecided → High |
| milestone: | none → ubuntu-15.03 |
| assignee: | nobody → Martin Pitt (pitti) |
| Changed in sysvinit (Ubuntu): | |
| status: | New → Fix Committed |
| description: | updated |
| Changed in sysvinit (Debian): | |
| status: | Unknown → New |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in sysvinit (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Changed in sysvinit (Debian): | |
| status: | New → Fix Committed |
| Changed in sysvinit (Debian): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package sysvinit - 2.88dsf-
---------------
sysvinit (2.88dsf-
* invoke-rc.d: There are two cases when "systemctl is-enabled" fails: Either
the unit exists and is disabled, or if the unit doesn't exist (or only in
a generator output dir). In the latter case we do not want to prevent the
startup of a unit. (LP: #1429035)
-- Martin Pitt <email address hidden> Fri, 06 Mar 2015 10:55:49 +0100