Your message dated Sat, 17 Dec 2016 01:33:38 +0000
with message-id <[email protected]>
and subject line Bug#818978: fixed in systemd 232-8
has caused the Debian Bug report #818978,
regarding systemd crashes in lxc on container stop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
818978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818978
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-17+deb8u3
Tags: patch fixed-upstream
User: [email protected]
Usertags: jessie-backport
We are currently testing LXC 2.0 beta with unprivileged containers on Ubuntu
16.04/testing and hit a already fixed systemd bug when testing with
Debian/Jessie based containers.
Currently systemd crashes with an assert in the shutdown path right after
unmounting all devices:
# lxc stop test02
# ps axf
21568 ? Ss 0:00 [lxc monitor] /var/lib/lxd/containers test02
21584 ? Ss 6:55 \_ /sbin/init
22588 ? Ss 1:10 \_ /lib/systemd/systemd-journald
17093 ? Zs 0:00 \_ [systemctl] <defunct>
Attached is a log file with the journalctl output, showing the assert:
systemd[1]: Assertion 'sd_id128_randomize(&id) >= 0' failed at
../src/core/dbus.c:688, function bus_on_connection(). Aborting.
systemd[1]: Caught <ABRT>, dumped core as pid 15711.
systemd[1]: Freezing execution.
systemctl[15703]: Failed to execute operation: Connection reset by peer
The bug has been reported upstream and fixed in Systemd 219, and we would like
to request to include the patch[1] into Jessie.
It currently doesn’t affect LXC on a Jessie host, but any platforms on LXC 2.0
with unprivileged containers will run into this issue.
In respect of how long Jessie is still going to be around, and the upcoming
release of Ubuntu 16.04 this bugfix is important.
I’m attaching a link[2] to the initial discussion between Stéphane Graber and
Lennart Poettering, and a link[1] to applied patch. Also this[3] seems to be
the initial bug report for Ubuntu’s systemd package.
Best,
Stefan.
[1]
https://lists.freedesktop.org/archives/systemd-devel/2015-January/027323.html
[2]
https://github.com/systemd/systemd/commit/874d3404cbf2363604106c8f86683db4082691ea
[3] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499
journalctl.log
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 232-8
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <[email protected]> (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 17 Dec 2016 01:54:18 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-8
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<[email protected]>
Changed-By: Michael Biebl <[email protected]>
Description:
libnss-myhostname - nss module providing fallback resolution for the current
hostname
libnss-mymachines - nss module to resolve hostnames for local container
instances
libnss-resolve - nss module to resolve names via systemd-resolved
libnss-systemd - nss module providing dynamic user and group name resolution
libpam-systemd - system and service manager - PAM module
libsystemd-dev - systemd utility library - development files
libsystemd0 - systemd utility library
libudev-dev - libudev development files
libudev1 - libudev shared library
libudev1-udeb - libudev shared library (udeb)
systemd - system and service manager
systemd-container - systemd container/nspawn tools
systemd-coredump - tools for storing and retrieving coredumps
systemd-journal-remote - tools for sending and receiving remote journal logs
systemd-sysv - system and service manager - SysV links
udev - /dev/ and hotplug management daemon
udev-udeb - /dev/ and hotplug management daemon (udeb)
Closes: 756109 756604 818978 837999
Changes:
systemd (232-8) unstable; urgency=medium
.
[ Martin Pitt ]
* Drop systemd dependency from libnss-myhostname again.
This NSS module is completely independent from systemd, unlike the other
three.
* Install 71-seat.rules into the initrd.
This helps plymouth to detect applicable devices. (Closes: #756109)
* networkd: Fix crash when setting routes.
* resolved: Drop removal of resolvconf entry on stop.
This leads to timeouts on shutdown via the resolvconf hooks and does not
actually help much -- /etc/resolv.conf would then just be empty instead of
having a nonexisting 127.0.0.53 nameserver, so manually stopping resolved
in a running system is broken either way. (LP: #1648068)
* Keep RestrictAddressFamilies on amd64.
This option and libseccomp currently work on amd64 at least, so let's make
sure it does not break there as well, and benefit from the additional
protection at least on this architecture.
* Explicitly set D-Bus policy dir.
This is about to change upstream in
https://github.com/systemd/systemd/pull/4892, but as explained in commit
2edb1e16fb12f4 we need to keep the policies in /etc/ until stretch+1.
.
[ Michael Biebl ]
* doc: Clarify NoNewPrivileges in systemd.exec(5). (Closes: #756604)
* core: Rework logic to determine when we decide to add automatic deps for
mounts. This adds a concept of "extrinsic" mounts. If mounts are
extrinsic we consider them managed by something else and do not add
automatic ordering against umount.target, local-fs.target,
remote-fs.target. (Closes: #818978)
* rules: Add persistent links for nbd devices. (Closes: #837999)
Checksums-Sha1:
d6cfa7ec7edbb3dce39f9451c5f5f365616ce0e9 4653 systemd_232-8.dsc
1b26f509c3b7f3b355db00bcadab2177fa270a80 131676 systemd_232-8.debian.tar.xz
Checksums-Sha256:
3ca60d621830e7df68aff42fcd7e09ad3eeca54ce15cade2f5190ad5d9208581 4653
systemd_232-8.dsc
5dcb0e19e7a33e15ad5cea4b9806c4705b78ebe87a0478fbdf7d85c20fc29bab 131676
systemd_232-8.debian.tar.xz
Files:
b01af8a35f918408571da8473dfb5f25 4653 admin optional systemd_232-8.dsc
3eef4a6e45f03ac77181592576cc08ee 131676 admin optional
systemd_232-8.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlhUknUACgkQauHfDWCP
ItwbvQ/9Gt18eR75LIRWma626sFC6tW0goC0r+VFrESjgoLx5LdYJpArTlKK6srl
JxoLcvTWIfNroiPs63Rs/DhHcPisoJOSfmZ5y8KL6Nbphmx1A9fqkEb8tTbVosgw
FpfXRUcN2tQaTt8xi5doGZ2lBhLz728NIxxBkZOZMFi0zT+RU426ew9m1fNvOj//
2yg9DHhcQezCcRIaCATLpMihQxmvACNt440xFLn+yNIj5za7xcqP9RXLzOC4lqCr
voGE9AgO+i0v0O5KNnzSDjnNMtGelu3GZGENIP22ZF9+/qqfLu4hWJpifaW/75q/
MDlM5xWqVa5Naie8nxoq+bmP8OXXW0K+tl5b5VgESA/P2umNOTT7bHXDTodwyzj/
YnyaN5UXCmCHVFO2j9X65pQWt9ZNkuKJ9N0+EmzLgiTuD6hZ/lMOAWWvkbtftdZo
VPXYKh2T2HSUGFny2NxwdRWsS4xnNqUgGxT1WBTqZlDHfA0Fo6KwMl+e3Y6kmLny
TK8yoouCiLqxrpDbIX8DhGQEw0IATOf77qreP32ZA74QpOKgBokrbsUrO/pY+7Hs
/azo2EAH0/2lqU6yYTBr6/OPe4OR+S8F6gfTDXhHyZH0KesPthhrE03+VQHbfFwn
o7+RTiVgEeJjGP97Zw8zNdHPPpDT8HQnw04g7wIKcuPHq7h3XY8=
=2DPH
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
