Your message dated Tue, 2 Dec 2014 06:06:58 +0100
with message-id <20141202050658.gb2...@piware.de>
and subject line Re: Bug#771723: systemd: systemd: kernel panic as /sbin/init
cannot load libapparmor1.so
has caused the Debian Bug report #771723,
regarding systemd: systemd: kernel panic as /sbin/init cannot load
libapparmor1.so
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 ow...@bugs.debian.org
immediately.)
--
771723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 217-1
Severity: critical
Justification: breaks the whole system
Somehow I eneded up with an unusable system due to /sbin/init was not booting.
After installing sysvinit-core the system booted normal. Sorry, but I did not
get reportbug to report bugs from the console when I booted with
“init=/bin/bash”.
The problem is related to libapparmor1, which cannot be found as it seems to be
installed in /usr/lib and not in /lib. And /usr is mounted after starting init
as usual.
So trying to load systemd the kornel is not able to load the shared libraries
and crashes with a kernel panic.
I might be out of date, but as far as I know no files that are needed at boot
must occur below /usr.
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'oldstable-updates'),
(500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
mingw64-windows
mingw64-x86v64
mingw64-amd64
mingw64-i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-58
ii libacl1 2.2.52-2
ii libapparmor1 2.9.0-2
ii libaudit1 1:2.4-1
ii libblkid1 2.25.2-3
ii libc6 2.19-13
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-3
ii libgcrypt20 1.6.2-4
ii libkmod2 18-3
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 217-1
ii mount 2.25.2-3
ii sysv-rc 2.88dsf-58
ii udev 215-7
ii util-linux 2.25.2-3
Versions of packages systemd recommends:
ii dbus 1.8.12-1
ii libpam-systemd 217-1
Versions of packages systemd suggests:
pn systemd-ui <none>
-- Configuration Files:
/etc/systemd/resolved.conf 886b81674c4697d8949d0fba0e21907d [Errno 2] Datei
oder Verzeichnis nicht gefunden: u'/etc/systemd/resolved.conf
886b81674c4697d8949d0fba0e21907d'
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: forcemerge 771652 -1
Hello Tobias,
Tobias Schlemmer [2014-12-01 22:33 +0100]:
> The problem is related to libapparmor1, which cannot be found as it seems to
> be
> installed in /usr/lib and not in /lib. And /usr is mounted after starting init
> as usual.
This was fixed yesterday in 172-2, see #771652.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
--- End Message ---
