[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2017-03-09 Thread Launchpad Bug Tracker
This bug was fixed in the package init-system-helpers - 1.29ubuntu4 --- init-system-helpers (1.29ubuntu4) xenial; urgency=medium * script/invoke-rc.d: backport change from 1.36 so that logs showing a failure to start a service with systemd will include the necessary informat

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2017-03-01 Thread Steve Langasek
** Description changed: [SRU Justification] Currently if a systemd unit fails to start in a non-interactive upgrade and all you have is a log, it's impossible to debug. Fix this so that logs contain the actual details of the unit failure. [Test case] 1. Get a root shell. 2. Run "se

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-11-30 Thread Chris J Arges
Hello Steve, or anyone else affected, Accepted init-system-helpers into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/init- system-helpers/1.29ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new pa

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-11-29 Thread Steve Langasek
** Description changed: + [SRU Justification] + Currently if a systemd unit fails to start in a non-interactive upgrade and all you have is a log, it's impossible to debug. Fix this so that logs contain the actual details of the unit failure. + + [Test case] + + [Regression potential] + Minim

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-11-28 Thread Martin Pitt
** Changed in: init-system-helpers (Ubuntu Xenial) Assignee: Martin Pitt (pitti) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596056 Title: output of invoke-rc.d for systemd u

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-08-02 Thread Robie Basak
** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596056 Title: output of invoke-rc.d for systemd units un-debuggable on failure To manage notifications about this bug go to

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-06-30 Thread Launchpad Bug Tracker
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

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-06-29 Thread Martin Pitt
Robie suggested that this would be helpful to backport to xenial, adding task. ** Also affects: init-system-helpers (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: init-system-helpers (Ubuntu Xenial) Status: New => Triaged ** Changed in: init-system-helpers (Ubu

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-06-29 Thread Martin Pitt
Yes, I believe it would, marking as a duplicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596056 Title: output of invoke-rc.d for systemd units un-debuggable on failure To manage notification

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-06-29 Thread Robie Basak
Would this fix also solve bug 1587791? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596056 Title: output of invoke-rc.d for systemd units un-debuggable on failure To manage notifications about th

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-06-28 Thread Martin Pitt
http://anonscm.debian.org/cgit/collab-maint/init-system- helpers.git/commit/?id=740c8150662 ** Changed in: init-system-helpers (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https:

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-06-28 Thread Martin Pitt
** Changed in: init-system-helpers (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596056 Title: output of invoke-rc.d for systemd units un

[Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2016-06-28 Thread Martin Pitt
Seems fine to me at first sight. I'd vote for "systemctl status", as that also shows running and exited services with exit codes etc., and the journal tail. We have this shiny new technology now, so let's use it :-) Just checking with the other init folks. ** Changed in: init-system-helpers (Ubun