touch-packages team mailing list archive

Thread
Date
[Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: "Sven R. Kunze" <srkunze@xxxxxxx>
Date: Mon, 30 Nov 2015 21:05:34 -0000
Reply-to: Bug 1519499 <1519499@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
>>> uname -a
Linux mexico 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>>> lxc exec test -- uname -a
Linux test 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux


journalctl only shows messages related to container startup:


>>> lxc exec test -- journalctl
-- Logs begin at Mon 2015-11-30 21:03:37 UTC, end at Mon 2015-11-30 21:03:53 UTC. --
Nov 30 21:03:37 test systemd-journal[223]: Runtime journal (/run/log/journal/) is currently using 8.0M.
                                           Maximum allowed usage is set to 799.2M.
                                           Leaving at least 1.1G free (of currently available 7.7G of space).
                                           Enforced usage limit is thus 799.2M.
Nov 30 21:03:37 test systemd-journal[223]: Runtime journal (/run/log/journal/) is currently using 8.0M.
                                           Maximum allowed usage is set to 799.2M.
                                           Leaving at least 1.1G free (of currently available 7.7G of space).
                                           Enforced usage limit is thus 799.2M.
Nov 30 21:03:37 test systemd-journal[223]: Journal started
Nov 30 21:03:37 test systemd-remount-fs[108]: /bin/mount for / exited with exit status 1.
Nov 30 21:03:37 test systemd-remount-fs[108]: mount: can't find LABEL=cloudimg-rootfs
Nov 30 21:03:37 test mount[133]: mount: permission denied
Nov 30 21:03:37 test loadkeys[145]: Couldn't get a file descriptor referring to the console
Nov 30 21:03:37 test apparmor[157]: lxc
Nov 30 21:03:37 test apparmor[157]: * Not starting AppArmor in container
Nov 30 21:03:37 test apparmor[157]: ...done.
Nov 30 21:03:37 test systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE
Nov 30 21:03:37 test systemd[1]: console-setup.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: console-setup.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: Failed to start Set console keymap.
Nov 30 21:03:37 test systemd[1]: console-setup.service: Unit entered failed state.
Nov 30 21:03:37 test systemd-journal[223]: Forwarding to syslog missed 1 messages.
Nov 30 21:03:37 test systemd[1]: console-setup.service: Failed with result 'exit-code'.
Nov 30 21:03:37 test systemd[1]: Started LSB: AppArmor initialization.
Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Nov 30 21:03:37 test systemd[1]: Started Load/Save Random Seed.
Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: Started Clean up any mess left by 0dns-up.
Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on /lxc/test/system.slice/resolvconf.service: Permission denied
Nov 30 21:03:37 test systemd[1]: Starting Nameserver information manager...
Nov 30 21:03:37 test sh[185]: Segmentation fault (core dumped)
Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on /lxc/test/system.slice/systemd-journal-flush.service: Permission denied
Nov 30 21:03:37 test systemd[1]: Starting Flush Journal to Persistent Storage...
Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on /lxc/test/system.slice/systemd-random-seed.service: Permission denied
Nov 30 21:03:37 test systemd-journal[223]: Runtime journal (/run/log/journal/) is currently using 8.0M.
                                           Maximum allowed usage is set to 799.2M.
                                           Leaving at least 1.1G free (of currently available 7.7G of space).
                                           Enforced usage limit is thus 799.2M.
Nov 30 21:03:37 test systemd[1]: Started Flush Journal to Persistent Storage.
Nov 30 21:03:37 test systemd[1]: Started Nameserver information manager.
Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on /lxc/test/system.slice/systemd-journal-flush.service: Permission denied

-- 
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