[vivid] Failed to reset devices.list

Bug #1413193 reported by dino99
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Vivid i386 booted with systemd

from syslog:

 dbus[668]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
 systemd[1]: Starting Hostname Service...
 systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
 systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument
 dbus[668]: [system] Successfully activated service 'org.freedesktop.hostname1'
 systemd[1]: Started Hostname Service.

sys/fs/cgroup/devices/system.slice owned by root and set 'read-only'
sys/fs/cgroup/devices/user.slice " " "

(all the files are 0 bytes)

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 218-3ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
Uname: Linux 3.19.0-2-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.15.1-0ubuntu2
Architecture: i386
BootDmesg: (Nothing has been logged yet.)
CurrentDesktop: GNOME
Date: Wed Jan 21 13:23:53 2015
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

Revision history for this message
dino99 (9d9) wrote :
description: updated
Martin Pitt (pitti)
Changed in systemd (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :
Changed in systemd (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
dino99 (9d9) wrote :

That problem is gone with 218-10

Changed in systemd (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Yes, I know, but -10 isn't in vivid yet; this bug will be auto-closed once it migrates from vivid-proposed.

Changed in systemd (Ubuntu):
status: Fix Released → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (7.6 KiB)

This bug was fixed in the package systemd - 218-10ubuntu1

---------------
systemd (218-10ubuntu1) vivid; urgency=medium

  [ Martin Pitt ]
  * Merge with Debian unstable. Remaining Ubuntu changes:
    - Hack to support system-image read-only /etc, and modify files in
      /etc/writable/ instead.
    - Keep our much simpler udev maintainer scripts (all platforms must
      support udev, no debconf).
    - initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
      with wait-for-root. Will get applicable to Debian once Debian gets
      wait-for-root in initramfs-tools.
    - initramfs init-bottom: If LVM is installed, settle udev,
      otherwise we get missing LV symlinks. Workaround for LP #1185394.
    - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
      dependencies to "lvm2" which is handled with udev rules in Ubuntu.
    - Provide shutdown fallback for upstart. (LP: #1370329)
    - debian/extra/ifup@.service: Additionally run for "auto" class. We don't
      really support "allow-hotplug" in Ubuntu at the moment, so we need to
      deal with "auto" devices appearing after "/etc/init.d/networking start"
      already ran. (LP: #1374521) Also, check if devices are actually defined
      in /etc/network/interfaces as we don't use Debian's net.agent.
    - ifup@.service: Drop dependency on networking.service (i. e.
      /etc/init.d/networking), and merely ensure that /run/network exists.
      This avoids unnecessary dependencies/waiting during boot and dependency
      cycles if hooks wait for other interfaces to come up (like ifenslave
      with bonding interfaces). (LP: #1414544)
    - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
      Ubuntu we currently keep the setting whether the RTC is in local or UTC
      time in /etc/default/rcS "UTC=yes|no", instead of /etc/adjtime.
      (LP: #1377258)
    - Put session scopes into all cgroup controllers. This makes unprivileged
      user LXC containers work under systemd. (LP: #1346734)
    - Lower Breaks: to plymouth version which has the udev inotify fix in
      Ubuntu.
    - Lower libappamor1 dep to the Ubuntu version where it moved to /lib.
    - Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
      This currently fails when being triggered by Jenkins, but is totally
      unreproducible when running this manually on the exact same machine.

    Upgrade fixes, keep until 16.04 LTS release:
    - systemd Conflicts/Replaces/Provides systemd-services.
    - Remove obsolete systemd-logind upstart job.
    - Clean up obsolete /etc/udev/rules.d/README.

  * ifup@.service: Fix syntax error. (LP: #1421556, #1420601)

  [ Didier Roche ]
  * Add systemd-fsckd multiplexer and feed its output to plymouth. This
    provides an aggregate progress report of running file system checks and
    also allows cancelling them with ^C.
    (LP: #1316796; Closes: #775093, #758902)

systemd (218-10) experimental; urgency=medium

  * Pull latest keymaps from upstream git. (LP: #1334968, #1409721)
  * rules: Fix by-path of mmc RPMB partitions and don't blkid them. Avoids
    kernel buffer I/O errors and timeouts. (LP: #1333140...

Read more...

Changed in systemd (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
David Favor (davidfavor) wrote :
Download full text (5.0 KiB)

Still broken in systemd 219.

If someone knows how to fix this, please update this ticket. Thanks.

rmt-net8# lxc-create --version
1.1.2

rmt-net8# lxcfs --version
FUSE library version: 2.9.2
fusermount version: 2.9.2
using FUSE kernel interface version 7.19

rmt-net8# psall | grep lxcfs
root 1461 0.1 0.0 22060 2820 ? Ss 17:55 0:02 /usr/bin/lxcfs -f -s -o allow_other /var/lib/lxcfs/
root 13887 0.0 0.0 6616 796 pts/2 S+ 18:29 0:00 grep --color=auto lxcfs

_______

rmt-net8# lxc-start -n rmt-lightweight-vivid -F
systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
Detected virtualization lxc.
Detected architecture x86-64.

Welcome to Ubuntu 15.04!

Set hostname to <rmt-lightweight-vivid>.
Failed to install release agent, ignoring: No such file or directory
Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory.
Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[ OK ] Reached target Encrypted Volumes.
Failed to reset devices.list on /lxc/rmt-lightweight-vivid: Permission denied
[ OK ] Created slice Root Slice.
[ OK ] Listening on Delayed Shutdown Socket.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on Journal Audit Socket.
[ OK ] Listening on Journal Socket (/dev/log).
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice: Permission denied
[ OK ] Created slice System Slice.
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice/systemd-setup-dgram-qlen.service: Permission denied
         Starting Increase datagram queue length...
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice/system-getty.slice: Permission denied
[ OK ] Created slice system-getty.slice.
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice/system-container\x2dgetty.slice: Permission denied
[ OK ] Created slice system-container\x2dgetty.slice.
[ OK ] Reached target Paths.
[ OK ] Reached target Swap.
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/user.slice: Permission denied
[ OK ] Created slice User and Session Slice.
[ OK ] Reached target Slices.
[ OK ] Listening on Journal Socket.
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice/resolvconf.service: Permission denied
         Starting Nameserver information manager...
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice/systemd-remount-fs.service: Permission denied
         Starting Remount Root and Kernel File Systems...
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice/dev-mqueue.mount: Permission denied
         Mounting POSIX Message Queue File System...
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice/udev-finish.service: Permission denied
         Starting Copy rules generated while the root was ro...
Failed to reset devices.list on /lxc/rmt-lightweight-vivid/system.slice/dev-hu...

Read more...

Revision history for this message
Tessa (unit3) wrote :

Just ran into this tonight on a Xenial container running on a Xenial host:

May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/ondemand.service: Operation not permitted
May 1 09:12:55 mysqlbench systemd[1]: Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/mysql.service: Operation not permitted
May 1 09:12:55 mysqlbench systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/irqbalance.service: Operation not permitted
May 1 09:12:55 mysqlbench systemd[1]: Starting LSB: daemon to balance interrupts for SMP systems...
May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/systemd-user-sessions.service: Operation not permitted
May 1 09:12:55 mysqlbench systemd[1]: Starting Permit User Sessions...
May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/apport.service: Operation not permitted
May 1 09:12:55 mysqlbench systemd[1]: Starting LSB: automatic crash report generation...
May 1 09:12:55 mysqlbench systemd[1]: Started LSB: Start and stop the mysql database server daemon.
May 1 09:12:55 mysqlbench systemd[1]: Started Permit User Sessions.
May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/plymouth-quit.service: Operation not permitted
May 1 09:12:55 mysqlbench systemd[1]: Starting Terminate Plymouth Boot Screen...
May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/plymouth-quit-wait.service: Operation not permitted
May 1 09:12:55 mysqlbench systemd[1]: Starting Hold until boot process finishes up...
May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/systemd-user-sessions.service: Operation not permitted
May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/mysql.service: Operation not permitted
May 1 09:12:55 mysqlbench systemd[1]: Started Hold until boot process finishes up.
May 1 09:12:55 mysqlbench systemd[1]: Started LSB: automatic crash report generation.
May 1 09:12:55 mysqlbench systemd[1]: Failed to reset devices.list on /system.slice/console-getty.service: Operation not permitted

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.