This bug was fixed in the package init-system-helpers - 1.36
---------------
init-system-helpers (1.36) unstable; urgency=medium
[ Martin Pitt ]
* init: Don't depend on sysvinit-core when building on/for Ubuntu and
derivatives.
* init: Drop "essential" from the package description as it is not essential
any more.
* invoke-rc.d: Quiesce error message if "runlevel" does not exist, which is
now the case in chroots since init stopped being essential.
(Closes: #827376)
* update-rc.d: Testing for /etc/init.d/mountkernfs.sh is not sufficient as
initscripts might only be unpacked but not configured yet (during
debootstrap). Thus test if /etc/rcS.d/S??mountkernfs.sh exists. Thanks to
Felipe Sateler for the idea! (Closes: #824804)
* init-system-helpers: Ship README.invoke-rc.d and README.policy-rc.d.
* invoke-rc.d.8: Update the SEE ALSO link to README.policy-rc.d.
(Closes: #358496)
* service.8: Document that this starts systemd units as well.
(Closes: #758139)
* invoke-rc.d: Show "systemctl status" on a failed (re)start if running
under systemd. This makes logs with failed package installations much more
useful, and human users will most likely do exactly that anyway.
(LP: #1596056)
[ Luca Boccassi ]
* dh_systemd_enable: Add support for installing templated service units.
(Closes: #770344)
* dh_systemd_enable: Add support for installing path units.
(Closes: #768609)
-- Martin Pitt <mp...@debian.org> Tue, 28 Jun 2016 22:10:37 +0200
** Changed in: init-system-helpers (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1596056
Title:
output of invoke-rc.d for systemd units un-debuggable on failure
Status in init-system-helpers package in Ubuntu:
Fix Released
Status in init-system-helpers source package in Xenial:
Triaged
Bug description:
When invoke-rc.d is called on a systemd system, if the unit fails to
start, you get output like:
Created symlink
/etc/systemd/system/multi-user.target.wants/openafs-fileserver.service →
/lib/systemd/system/openafs-fileserver.service.
Job for openafs-fileserver.service failed because the control process exited
with error code.
See "systemctl status openafs-fileserver.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript openafs-fileserver, action "start" failed.
dpkg: error processing package openafs-fileserver (--configure):
subprocess installed post-installation script returned error exit status 1
The output shown here comes from systemctl itself, and is usually
fine. The admin who ran systemctl can run those other commands to
debug.
However, when called by invoke-rc.d, this output is usually seen only
in a log file; maybe submitted in a bug report, maybe attached to
something like an autopkgtest:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-yakkety/yakkety/armhf/o/openafs/20160624_174535@/log.gz
By the time someone looks at this log output, it is often too late to
run those commands in order to debug the failure.
invoke-rc.d should call these commands for us on systemd unit failure,
so that the relevant debugging information is included in the log
where it can help.
We don't want to call 'journalctl -xe', which might leak information
into the log from other jobs, but 'journalctl -x -u <this_unit>' may
be appropriate.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1596056/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
