[Bug 1568094] Re: Many error message such as "Start request repeated too quickly."

[Martin Pitt]

By default the various binfmt.d directories are indeed empty, that's
normal and the 'condition failed' in systemctl status is entirely
expected. So maybe what happens is that some other service repeatedly
tries to run systemd-binfmt.service. Can you please give me the output
of

  systemctl show systemd-binfmt.service |grep By

?

What might also help me is to run

  systemd-analyze dump > /tmp/dump.txt

and attach /tmp/dump.txt here.

Thanks!

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1568094

Title:
  Many error message such as "Start request repeated too quickly."

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  when I look at journalctl's output, I see many error messages of the
  same type:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary Formats.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password Requests to Console Directory Watch.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password Requests to Console Directory Watch.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu1
  Uname: Linux 4.5.0-040500-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr  8 20:41:02 2016
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500-lowlatency root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-03-31 (8 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.systemd.timesyncd.conf: 2015-10-21T22:12:17.831478

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