| Thread Previous • Date Previous • Date Next • Thread Next |
Thanks, that does indeed seem to point towards a systemd issue, I've
added a systemd task, Martin should be able to pick things up from
there.
Can you also tell us what version of the kernel you're using? We've seen
some weird behavior with systemd on some specific kernel releases in the
past.
Also, does "journalctl" in the container after attempting a shutdown
print any useful information or error messages?
Thanks!
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxd (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
[systemd] SIGPWR doesn't always lead to shutdown
Status in lxd package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
New
Bug description:
This is a follow-up on this issue here:
https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container
gently and as it seems the issue lies within ubuntu/systemd which does
not handle SIGPWR correctly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
