Your message dated Tue, 19 May 2015 11:43:38 +0200
with message-id <555b05ca.9070...@kvr.at>
and subject line Re: Bug#785484: systemd: on Raspberry pi B+, several essential
services fail, including systemd-logind
has caused the Debian Bug report #785484,
regarding cgroup-bin: breaks boot with systemd
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.)
--
785484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-17
Severity: important
Dear Maintainer,
This concerns Raspbian upgraded to Jessie on the Raspberry Pi B+ (Model 1)
Here, several services fail if systemd is being used, most essentially dbus
takes very long to start and later fails silently. Subsequently,
systemd-logind
fails, making local and SSH login impossible.
Several users have reported similar issues, see
https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=104314&p=759634
and
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=94840&p=759627
Here is the kind of error I see:
-- Logs begin at Fr 2015-05-15 21:21:49 UTC, end at Fr 2015-05-15
21:23:35 UTC. --
Mai 15 21:22:03 raspbian systemd[1]: Starting Login Service...
Mai 15 21:22:29 raspbian systemd-logind[430]: Failed to add match for
NameOwnerChanged: Connection timed out
Mai 15 21:22:29 raspbian systemd-logind[430]: Failed to fully start up
daemon: Connection timed out
Mai 15 21:22:55 raspbian systemd[1]: systemd-logind.service: main
process exited, code=exited, status=1/FAILURE
Mai 15 21:22:55 raspbian systemd[1]: Failed to start Login Service.
Mai 15 21:22:55 raspbian systemd[1]: Unit systemd-logind.service entered
failed state.
Mai 15 21:22:55 raspbian systemd[1]: systemd-logind.service has no
holdoff time, scheduling restart.
Here are the other failed services:
May 15 22:20:04 raspbian systemd[1]: Failed to start LSB: triggerhappy
hotkey daemon.
May 15 22:20:04 raspbian systemd[1]: Unit triggerhappy.service entered
failed state.
May 15 22:20:04 raspbian systemd[1]: wicd.service: control process
exited, code=exited status=219
May 15 22:20:04 raspbian systemd[1]: Failed to start LSB: Starts and
stops Wicd.
May 15 22:20:04 raspbian systemd[1]: Unit wicd.service entered failed state.
May 15 22:20:04 raspbian systemd[1]: dbus.service: main process exited,
code=exited, status=219/CGROUP
May 15 22:20:04 raspbian systemd[1]: Unit dbus.service entered failed state.
May 15 22:20:04 raspbian systemd[1]: rsyslog.service: main process
exited, code=exited, status=219/CGROUP
May 15 22:20:04 raspbian systemd[1]: Failed to start System Logging Service.
May 15 22:20:04 raspbian systemd[1]: Unit rsyslog.service entered failed
state.
May 15 22:20:04 raspbian systemd[1]: systemd-user-sessions.service: main
process exited, code=exited, status=219/CGROUP
May 15 22:20:04 raspbian systemd[1]: Failed to start Permit User Sessions.
May 15 22:20:04 raspbian systemd[1]: Unit systemd-user-sessions.service
entered failed state.
May 15 22:20:04 raspbian systemd[1]: systemd-logind.service has no
holdoff time, scheduling restart.
May 15 22:20:05 raspbian systemd[1]: rsyslog.service holdoff time over,
scheduling restart.
-- Package-specific info:
-- System Information:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
Architecture: armv6l
Kernel: Linux 3.18.11+ (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-59
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1
ii libblkid1 2.25.2-6
ii libc6 2.19-18
ii libcap2 1:2.24-8
ii libcap2-bin 1:2.24-8
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.3-2
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 215-17
ii mount 2.25.2-6
ii sysv-rc 2.88dsf-59
ii udev 215-17
ii util-linux 2.25.2-6
Versions of packages systemd recommends:
ii dbus 1.8.16-1
pn libpam-systemd <none>
Versions of packages systemd suggests:
pn systemd-ui <none>
-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
Storage=persistent
-- no debconf information
==> /var/lib/systemd/deb-systemd-helper-enabled/fake-hwclock.service.dsh-also
<==
/etc/systemd/system/sysinit.target.wants/fake-hwclock.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.ModemManager1.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/cgproxy.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/cgproxy.service
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/ssh.socket
==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <==
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/ssh.service
/etc/systemd/system/sshd.service
==> /var/lib/systemd/deb-systemd-helper-enabled/saned.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/saned.socket
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ModemManager.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cron.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/sysinit.target.wants/fake-hwclock.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/cron.service
==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <==
==> /var/lib/systemd/deb-systemd-helper-enabled/cgmanager.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/cgmanager.service
==> /var/lib/systemd/deb-systemd-helper-enabled/mopidy.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/mopidy.service
==> /var/lib/systemd/deb-systemd-helper-enabled/ModemManager.service.dsh-also
<==
/etc/systemd/system/multi-user.target.wants/ModemManager.service
/etc/systemd/system/dbus-org.freedesktop.ModemManager1.service
0 overridden configuration files found.
--- End Message ---
--- Begin Message ---
On 2015-05-19 02:03, Bernhard Übelacker wrote:
> Am 19.05.2015 um 01:17 schrieb Christian Kastner:
>> But TTBOMK, cgroup-bin never shipped an /etc/init.d/cgroup-bin file. See
>> for example its contents in wheezy [1], or the TODO item [2] created by
>> the previous maintainer.
>
> I think I found it here:
> $ dget
> http://archive.raspberrypi.org/debian/pool/main/libc/libcgroup/libcgroup_0.38-1+rpi1.dsc
> $ dpkg-source -x libcgroup_0.38-1+rpi1.dsc
> $ cd libcgroup-0.38/
> $ grep "Kernel lacks cgroups" . -R -i
> ./debian/cgroup-bin.init: log_warning_msg "Kernel lacks
> cgroups or memory controller not available, not starting cgroups."
Yep, so it's a customized version of the cgroup-bin package.
> These 2 version do not contain this file:
> dget
> http://mirrordirector.raspbian.org/raspbian/pool/main/libc/libcgroup/libcgroup_0.41-6.dsc
> dget
> http://mirrordirector.raspbian.org/raspbian/pool/main/libc/libcgroup/libcgroup_0.38-1.dsc
>
> As Debian never shipped this file, no actions on Debian side
> could be taken to remove this old file?
I'm afraid not. It goes against Debian principles to modify local
configuration in such a way. It's complicated enough between different
versions of the same package within Debian.
Say Debian's package removes it. What happens if the upgrade fails? What
happens if the user had deliberate changes in that init script?
Therefore, I am closing this bug on the Debian side.
> So it seems this is just a Raspbian issue.
> (And if an upgrade from Raspbian-Wheezy to Raspbian-Jessie will be
> supported, the removal of this file has to be taken care of on Raspbian side?)
That is correct, although as Michael pointed out, this appears to be a
raspberrypi.org issue, and not a raspian.org one.
Regards,
Christian
signature.asc
Description: OpenPGP digital signature
--- End Message ---
