Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

graysky · 2013-05-07 21:28:04

Nothing in my journalctl but I get the following when I reboot; system up-to-date with [testing] enabled. Do others see this as well?

[   OK   ] Reached target Shutdown.
systemd-cgroups-agent[1186]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/system/private: Connection refused
systemd-cgroups-agent[1187]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/system/private: Connection refused
systemd-cgroups-agent[1188]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/system/private: Connection refused
systemd-cgroups-agent[1189]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/system/private: Connection refused
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Hardware watchgod ` INCANT' , version 0
Unmounting file systems.
All filesystem unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
All loop devices detached.
Detaching DM devices.
All DM devices detacthed.
Storage is finalized
mei 0000:00:16.0: stop

Journal:

$ sudo journalctl
...
May 07 17:20:23 larch sudo[1036]: pam_unix(sudo:session): session closed for user root
May 07 17:20:30 larch sudo[1060]: facade : TTY=pts/0 ; PWD=/home/facade ; USER=root ; COMMAND=/sbin/reboot
May 07 17:20:30 larch sudo[1060]: pam_unix(sudo:session): session opened for user root by facade(uid=0)
May 07 17:20:30 larch systemd[1]: Stopping Sound Card.
May 07 17:20:30 larch systemd[1]: Stopped target Sound Card.
May 07 17:20:30 larch systemd[1]: Stopping Authorization Manager...
May 07 17:20:30 larch systemd[1]: Stopping OpenSSH Per-Connection Daemon...
May 07 17:20:30 larch systemd[1]: Stopping Graphical Interface.
May 07 17:20:30 larch systemd[1]: Stopped target Graphical Interface.
May 07 17:20:30 larch systemd[1]: Stopping Multi-User System.
May 07 17:20:30 larch systemd[1]: Stopped target Multi-User System.
May 07 17:20:30 larch systemd[1]: Stopping Apply cpupower configuration...
May 07 17:20:30 larch systemd[1]: Stopped Apply cpupower configuration.
May 07 17:20:30 larch systemd[1]: Stopping Network Time Service...
May 07 17:20:30 larch systemd[1]: Stopped D-Bus System Message Bus.
May 07 17:20:30 larch systemd[1]: Stopped Getty on tty1.
May 07 17:20:30 larch sudo[1060]: pam_unix(sudo:session): session closed for user root
May 07 17:20:30 larch ntpd[946]: ntpd exiting on signal 15
May 07 17:20:30 larch NetworkManager[769]: <warn> disconnected by the system bus.
May 07 17:20:30 larch NetworkManager[769]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 byte
May 07 17:20:30 larch systemd[1]: Stopped Authorization Manager.
May 07 17:20:30 larch systemd[1]: Stopped Network Time Service.
May 07 17:20:30 larch systemd[1]: Stopping Network.
May 07 17:20:30 larch systemd[1]: Stopped target Network.
May 07 17:20:30 larch systemd[1]: Stopping Network Manager...
May 07 17:20:30 larch NetworkManager[769]: <info> caught signal 15, shutting down normally.
May 07 17:20:30 larch NetworkManager[769]: <info> (wlan0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
May 07 17:20:30 larch NetworkManager[769]: <info> Writing DNS information to /usr/sbin/resolvconf
May 07 17:20:30 larch systemd[1]: Stopped Initialize hardware monitoring sensors.
May 07 17:20:30 larch systemd[1]: Stopped OpenSSH Per-Connection Daemon.
May 07 17:20:30 larch NetworkManager[769]: <info> exiting (success)
May 07 17:20:30 larch systemd[1]: Stopped Virtual console mouse server.
May 07 17:20:30 larch systemd[1]: Stopped Login Service.
May 07 17:20:30 larch systemd[1]: Stopped Network Manager.
May 07 17:20:32 larch systemd[1]: Stopped LXDE Display Manager.
May 07 17:20:32 larch systemd[1]: Stopping Permit User Sessions...
May 07 17:20:32 larch systemd[1]: Stopped Permit User Sessions.
May 07 17:20:32 larch systemd[1]: Stopping Remote File Systems.
May 07 17:20:32 larch systemd[1]: Stopped target Remote File Systems.
May 07 17:20:36 larch systemd[1]: Stopped 32-bit chroot.
May 07 17:20:36 larch systemd[1]: Stopping Basic System.
May 07 17:20:36 larch systemd[1]: Stopped target Basic System.
May 07 17:20:36 larch systemd[1]: Stopping Paths.
May 07 17:20:36 larch systemd[1]: Stopped target Paths.
May 07 17:20:36 larch systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
May 07 17:20:36 larch systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
May 07 17:20:36 larch systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
May 07 17:20:36 larch systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
May 07 17:20:36 larch systemd[1]: Stopping Timers.
May 07 17:20:36 larch systemd[1]: Stopped target Timers.
May 07 17:20:36 larch systemd[1]: Stopping Daily Cleanup of Temporary Directories.
May 07 17:20:36 larch systemd[1]: Stopped Daily Cleanup of Temporary Directories.
May 07 17:20:36 larch systemd[1]: Stopping Sockets.
May 07 17:20:36 larch systemd[1]: Stopped target Sockets.
May 07 17:20:36 larch systemd[1]: Stopping sshd.socket.
May 07 17:20:36 larch systemd[1]: Closed sshd.socket.
May 07 17:20:36 larch systemd[1]: Stopping /dev/initctl Compatibility Named Pipe.
May 07 17:20:36 larch systemd[1]: Closed /dev/initctl Compatibility Named Pipe.
May 07 17:20:36 larch systemd[1]: Stopping Delayed Shutdown Socket.
May 07 17:20:36 larch systemd[1]: Closed Delayed Shutdown Socket.
May 07 17:20:36 larch systemd[1]: Stopping Device-mapper event daemon FIFOs.
May 07 17:20:36 larch systemd[1]: Closed Device-mapper event daemon FIFOs.
May 07 17:20:36 larch systemd[1]: Stopping D-Bus System Message Bus Socket.
May 07 17:20:36 larch systemd[1]: Closed D-Bus System Message Bus Socket.
May 07 17:20:36 larch systemd[1]: Stopping udev Control Socket.
May 07 17:20:36 larch systemd[1]: Closed udev Control Socket.
May 07 17:20:36 larch systemd[1]: Stopping System Initialization.
May 07 17:20:36 larch systemd[1]: Stopped target System Initialization.
May 07 17:20:36 larch systemd[1]: Stopping Apply Kernel Variables...
May 07 17:20:36 larch systemd[1]: Stopped Apply Kernel Variables.
May 07 17:20:36 larch systemd[1]: Unmounting Huge Pages File System...
May 07 17:20:36 larch systemd[1]: Stopping Encrypted Volumes.
May 07 17:20:36 larch systemd[1]: Stopped target Encrypted Volumes.
May 07 17:20:36 larch systemd[1]: Stopping Setup Virtual Console...
May 07 17:20:36 larch systemd[1]: Stopped Setup Virtual Console.
May 07 17:20:36 larch systemd[1]: Stopping Arbitrary Executable File Formats File System Automount Point.
May 07 17:20:36 larch systemd[1]: Unset automount Arbitrary Executable File Formats File System Automount Point.
May 07 17:20:36 larch systemd[1]: Unmounting POSIX Message Queue File System...
May 07 17:20:36 larch systemd[1]: Unmounting Configuration File System...
May 07 17:20:36 larch systemd[1]: Unmounting Debug File System...
May 07 17:20:36 larch systemd[1]: Stopping Swap.
May 07 17:20:36 larch systemd[1]: Stopped target Swap.
May 07 17:20:36 larch systemd[1]: Stopping Local File Systems.
May 07 17:20:36 larch systemd[1]: Stopped target Local File Systems.
May 07 17:20:36 larch systemd[1]: Unmounting /boot...
May 07 17:20:36 larch systemd[1]: Unmounting Temporary Directory...
May 07 17:20:36 larch systemd[1]: Stopping Journal Service...
May 07 17:20:36 larch systemd-journal[123]: Journal stopped
-- Reboot --

The reboot is successful; googling found many results dating back to 2010 and many not relevant.

https://bbs.archlinux.org/viewtopic.php?id=142514 (not the case on my system)
https://bbs.archlinux.org/viewtopic.php?id=151756 (no solution)
http://www.mail-archive.com/systemd-dev … 10707.html (I do not have the corresponding entries in my logs)

Last edited by graysky (2013-05-08 22:24:40)

graysky · 2013-05-08 22:24:59

...problem still present using linux-3.9.1-1-ARCH.

bangkok_manouel · 2013-05-09 14:41:10

I'm seeing this - sometimes only - since the very first day I switched to systemd (not running Arch so at least we know it's not distro specific. OTOH I'm the one who ported systemd so packaging mistakes on my side are definitely a possibility). journald says systemd was v199 and kernel 3.9.0-rc5+. Are you sure it's the kernel upgrade that triggered those messages?

graysky · 2013-05-09 15:02:40

Yes, if I downgrade to 3.8.11-1-ARCH the errors go away.

bangkok_manouel · 2013-05-09 15:09:43

OK thanks. I'll try latest 3.8 and see if I can reproduce it. If not, I'll try to bisect it if you don't beat me to it.

graysky · 2013-05-11 19:50:51

I got nothing, very interested in what you come up with.

WonderWoofy · 2013-05-11 20:43:25

For me too, this also has shown up only recently (as of 3.9.*). Though froom everything that I can tell, it seems harmless. But I also have not looked into it at all.

TtTFQN · 2013-05-12 18:11:40

I'm also affected on kernel 3.9.2

ozar · 2013-05-12 18:15:10

Updated to the 3.9.2 kernel today (not using testing repo) and now getting the same error/failure messages but can't figure out the cause. Didn't see any bug reports or forum solutions for this issue but will take another look around while watching this thread in case the solution appears here. Thanks...

Potomac · 2013-05-13 00:19:52

same error also with the 3.9.2 kernel,

I am not using testing packages, only stable packages

it would be helpfull if someone can create a bug report here :

https://bugs.archlinux.org/

Last edited by Potomac (2013-05-13 00:21:54)

graysky · 2013-05-13 19:47:41

Not clear to me that this is an Arch bug report... probably better to open upstream, but then again, we do have some talented devs and users highly capable of fixing such things to then submit an upstream report + fix.

TtTFQN · 2013-05-15 04:31:01

I've opened a new Report: https://bugs.archlinux.org/task/35296

tom.ty89 · 2013-05-15 07:29:08

I am getting similar message with kernel 3.9.2-1. It's "systemd1" instead of "system". And I mostly get one only instead of multiple lines of that.
By the way, how can I capture / where can I find the message shows while shutting down? For now I have to use a camera to record it down. LOL

vassie · 2013-05-15 10:30:24

Mine says systemd1 too

Run the following to output system messages to a file

sudo journalctl >> ~/journal.log

Makes it easier to find things

mynis01 · 2013-05-15 11:41:19

I'm getting the same error with 3.9.2, except my system actually hangs and has to be powered down hard. Nothing related shows up in journalctl. This happens with both the ck and stock arch kernels, and I'm not using any testing packages. I might be able to use alt-sysreq keys, haven't tried yet.

Storage is finalized
mei 0000:00:16.0: stop

Last edited by mynis01 (2013-05-15 11:41:58)

graysky · 2013-05-15 14:07:30

I am glad to see that this is affecting you on both the ck and arch kernels. If you read on ck's blog, the BFS is actually pretty good at finding these bugs due to the race conditions it scheduling can force.

einhard · 2013-05-15 14:37:05

I had this message (systemd-cgroups-agent[1186]) but also sudo didn't work in my case. It all started with 3.9.1(now 3.9.2) upgrade. When I've tried to reinstall sudo I got "already in filesystem" error for all files. This was very weird, so I forced reinstalling (I was too lazy to do it properly). Maybe it was data corruption, maybe something else but now sudo works and no systemd-cgroups-agent errors.

mynis01 · 2013-05-15 15:43:34

One thing really interesting about this bug: it is only caused by "systemctl reboot" and not "systemctl poweroff."

C6M6 · 2013-05-15 17:05:05

same problem here on shutdown and reboot, the problem came with the kernel 3.9.x, don't know if it's related but dmesg show also this...

systemd-journald[121]: Failed to read ACL on /var/log/journal/225f1ed791fb4315862e5832z1c28423/user-1000.journal, ignoring: Operation not supported

tom.ty89 · 2013-05-15 18:53:43

By the way, I got two installations of Arch on different machines. The one installed more recently does not have the problem.

Last edited by tom.ty89 (2013-05-15 20:04:00)

bocki · 2013-05-15 20:23:45

i've got the same problem, including the acl error message. just did a fresh install yesterday, tried a few kernels, 3.9.2-arch, 3.9.1-pf and just for fun i've also tested 3.10-rc1-mainline, results are the same.

tom.ty89 · 2013-05-15 23:48:38

But is it really something to do with the kernel? I mean systemd also got several updates recently.

graysky · 2013-05-16 08:39:28

Easy way to test this is to disable systemd and use another init system. Any takers? I might have a go when I get some free time. I have see Upstart recommended for users not wanting to use systemd. Others? Selection criteria would be: easy to configure.

WonderWoofy · 2013-05-16 15:14:42

There is that entire thread on OpenRC. From reading through it, it seems that those making it available are trying to make it more or less a drop in replacement. There is also that entire thread to help you get and idea of what needs to be done to get it going. And I juct checked, and there is a pretty thorough wiki page as well.

Also, there was that thread not too long ago about using busybox as your init system. It sounded not too terribly complicated, but also sounded like the actual removal of systemd/udev was necessary.

falconindy · 2013-05-16 15:20:29

I'd be curious to know why people think this is a problem. The error is harmless -- the agent is triggered because a cgroup ran empty, but systemd is already gone and won't respond. Any response it would provide would simply be for internal bookkeeping which it doesn't need to do -- the system is shutting down.

Upstream isn't going to be fixing this specifically -- kdbus is the answer.

Arch Linux

#1 2013-05-07 21:28:04

Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#2 2013-05-08 22:24:59

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#3 2013-05-09 14:41:10

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#4 2013-05-09 15:02:40

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#5 2013-05-09 15:09:43

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#6 2013-05-11 19:50:51

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#7 2013-05-11 20:43:25

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#8 2013-05-12 18:11:40

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#9 2013-05-12 18:15:10

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#10 2013-05-13 00:19:52

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#11 2013-05-13 19:47:41

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#12 2013-05-15 04:31:01

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#13 2013-05-15 07:29:08

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#14 2013-05-15 10:30:24

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#15 2013-05-15 11:41:19

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#16 2013-05-15 14:07:30

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#17 2013-05-15 14:37:05

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#18 2013-05-15 15:43:34

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#19 2013-05-15 17:05:05

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#20 2013-05-15 18:53:43

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#21 2013-05-15 20:23:45

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#22 2013-05-15 23:48:38

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#23 2013-05-16 08:39:28

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#24 2013-05-16 15:14:42

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

#25 2013-05-16 15:20:29

Re: Linux 3.9.1-1 throws errors on reboot - systemd-cgroups-agent

Board footer