← Back to team overview

touch-packages team mailing list archive

[Bug 1467131] Re: systmd-tmpfiles-setup sometimes not run on boot

 

So systemd-tmpfiles-setup-dev.service ran fine (don't worry about the
"does not match any include prefix", that's debugging output from setup-
dev), but systemd-tmpfiles-setup.service never actually ran, it seems
its waiting for local-fs.target to get active, which never actually
happens. But if you ran this from rescue mode that's no surprise -- all
this runs way before it. Can you please give me a journal output for a
normal (non-rescue) boot? After such a boot, please log in, do

  systemctl list-jobs > jobs.txt
  systemctl --failed > failed.txt

and attach jobs.txt and failed.txt here as well. Thanks!

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1467131

Title:
  systmd-tmpfiles-setup sometimes not run on boot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This is happening on an up-to-date 15.04,with systemd=219-7ubuntu6.
  Ocasionally, when booting up the system, network-manager service fails to start, reporting in logs that it is missing /run/sendsigs.omit.d directory.
  That file is indeed missing, although it is listed in /usr/lib/tmpiles.d/debian.conf
  The issue is reproducible when starting the system in recovery mode; in normal mode it happens occasionally (about 50%).

  Output of "journalctl -b": http://paste.ubuntu.com/11745993/
  Contents of /usr/lib/tempfiles.d/debian.conf: http://paste.ubuntu.com/11746045/

  Running "systemd-tmpfiles --create" after such unsuccesfull boot
  creates the missing directory (and some other too).

  The problem is similar to #1431110, but that bug was found to be a
  duplicate of another problem that is now fixed. Even with that fix, I
  am experiencing a correlated issue. I considered commenting on that
  bug, but marking it as non-incomplete (so that it would gain any
  attention) would require unlinking the duplicate, which wouldn't be
  right.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1467131/+subscriptions


References