Errors on cleaning up cgroups

Bug #1353989 reported by bugproxy
54
This bug affects 12 people
Affects Status Importance Assigned to Milestone
systemd-shim (Debian)
New
Unknown
systemd-shim (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

Problem Description
--------------------------------------
Lot of systemd failure messages pops up on console as well as seen in dmesg

---uname output---
Linux u10vm14 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = Power 8

---Debugger---
A debugger is not configured

Steps to Reproduce
----------------------------------
1) Install Ubuntu 14.10 August 6th build
2) After the installation while logging in seen multiple systemd failed messages on console and on dmesg

Failed messages:
[ 58.564179] systemd-logind[1420]: Failed to enable subscription: No such method 'Subscribe'
[ 58.576888] systemd-logind[1420]: New seat seat0.
[ 58.580312] systemd-logind[1420]: Failed to start unit user@1000.service: Unknown unit: user@1000.service
[ 58.581059] systemd-logind[1420]: Failed to start user service: Unknown unit: user@1000.service
[ 58.584561] systemd-logind[1420]: New session c1 of user ubuntu.
[11293.015056] init: hvc0 main process ended, respawning
[11293.045923] systemd-logind[1420]: Failed to abandon scope session-c1.scope
[11293.046499] systemd-logind[1420]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope
[17818.110774] systemd-logind[1420]: Failed to start unit user@0.service: Unknown unit: user@0.service
[17818.111944] systemd-logind[1420]: Failed to start user service: Unknown unit: user@0.service
[17818.115571] systemd-logind[1420]: New session c2 of user root.
[18812.879680] systemd-logind[1420]: New session 22 of user root.
[18814.620794] systemd-logind[1420]: Failed to abandon scope session-22.scope
[18814.622186] systemd-logind[1420]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2d22_2escope

bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-114370 severity-medium targetmilestone-inin---
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1353989/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
tags: added: utopic
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Luciano Chavez (lnx1138)
affects: ubuntu → systemd (Ubuntu)
bugproxy (bugproxy)
tags: added: targetmilestone-inin1410
removed: targetmilestone-inin---
Revision history for this message
Martin Pitt (pitti) wrote :

Missing API in systemd-shim.

affects: systemd (Ubuntu) → systemd-shim (Ubuntu)
Changed in systemd-shim (Ubuntu):
status: Confirmed → Triaged
summary: - systemd failure messages pop up on console as well as seen in dmesg
+ Errors on cleaning up cgroups
Revision history for this message
Martin Pitt (pitti) wrote :

Bug 1348039 already exists about the missing Subscribe(), retitling for the other issues.

Changed in systemd-shim (Debian):
status: Unknown → New
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2014-10-06 05:26 EDT-------
Any updates on the issue ?

Revision history for this message
David Lee (ramchyld) wrote :

I'd like to confirm that this is still happening with today's RC.

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2014-10-28 10:50 EDT-------
Installed Oct 6th Ubuntu 14.10 daily build and seen below messages after installation.

[ 15.281766] systemd-logind[940]: New seat seat0.
[ 15.287253] systemd-logind[940]: Failed to start unit user@1000.service: Unknown unit: user@1000.service
[ 15.287398] systemd-logind[940]: Failed to start user service: Unknown unit: user@1000.service
[ 15.292195] systemd-logind[940]: New session c1 of user ubuntu.
[ 136.784909] random: nonblocking pool is initialized

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2014-10-28 14:53 EDT-------
Yes. I updated our machines to current 14.10 package levels yesterday (Monday, October 27th) and I'm still seeing the messages on those machines.

I plan to do a fresh install of release-level 14.10 this morning, so I should be able to report whether the messages appear there, too.

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2014-10-28 16:32 EDT-------
Just confirming that I _do_ still see these messages on a fresh install of the released Ubuntu 14.10.

I installed a new system from the current ISO and set up a default user. Upon logging in from the console for the first time:

[ 77.358238] systemd-logind[2499]: Failed to start unit user@1000.service: Unknown unit: user@1000.service
[ 77.358325] systemd-logind[2499]: Failed to start user service: Unknown unit: user@1000.service

bugproxy (bugproxy)
tags: added: targetmilestone-inin1504
removed: targetmilestone-inin1410
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2014-12-15 08:49 EDT-------
This message also occures on Vivid.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.