touch-packages team mailing list archive

Thread
Date

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

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Martin Pitt <martin.pitt@xxxxxxxxxx>
Date: Mon, 07 Dec 2015 17:07:28 -0000
Reply-to: Bug 1519499 <1519499@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Ah, thanks! This finally revealed something interesting. So pretty much
everything is shut down already, but the last step triggers an
assertion:

Dec 01 17:23:49 test systemd[1600]: systemd-poweroff.service: Executing: /bin/systemctl --force poweroff
Dec 01 17:23:49 test systemd[1]: [1;31mAssertion 'sd_id128_randomize(&id) >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.[0m
Dec 01 17:23:50 test systemd[1]: [1;31mCaught <ABRT>, dumped core as pid 1612.[0m
Dec 01 17:23:50 test systemd[1]: [1;31mFreezing execution.[0m

** Changed in: systemd (Ubuntu)
       Status: Incomplete => New

** Summary changed:

- [systemd] SIGPWR doesn't always lead to shutdown
+ Shutdown failure: Assertion 'sd_id128_randomize(&id) >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

-- 
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:
  Shutdown failure: Assertion 'sd_id128_randomize(&id) >= 0' failed at
  ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

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