Bug#822881: Systemd related services fail during early boot
Hi Guido On Thu, 28 Apr 2016 20:05:42 +0200 Guido =?iso-8859-1?Q?G=FCnther?=wrote: > Package: systemd > Version: 229-4 > Severity: normal > > Hi, > since updating to 229 a couple of weeks ago I'm seeing these during early > boot: > > Apr 28 19:48:21 bogon systemd[1]: systemd-hwdb-update.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start Rebuild Hardware Database. > Apr 28 19:48:21 bogon systemd[1]: systemd-fsck-root.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start File System Check on Root > Device. > Apr 28 19:48:21 bogon systemd[1]: sys-fs-fuse-connections.mount: Start > request repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount FUSE Control File System. > Apr 28 19:48:21 bogon systemd[1]: sys-kernel-config.mount: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount Configuration File System. > Apr 28 19:48:21 bogon systemd[1]: systemd-binfmt.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start Set Up Additional Binary > Formats. > Apr 28 19:48:21 bogon systemd[1]: systemd-binfmt.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start Set Up Additional Binary > Formats. > Apr 28 19:48:21 bogon systemd[1]: systemd-hwdb-update.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start Rebuild Hardware Database. > Apr 28 19:48:21 bogon systemd[1]: systemd-fsck-root.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start File System Check on Root > Device. > Apr 28 19:48:21 bogon systemd[1]: sys-kernel-config.mount: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount Configuration File System. > Apr 28 19:48:21 bogon systemd[1]: sys-fs-fuse-connections.mount: Start > request repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount FUSE Control File System. > Apr 28 19:48:21 bogon systemd[1]: var-lib-machines.mount: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount Virtual Machine and > Container Storage. This looks a lot like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817755 which was also filed against v229. According to the bug reporter, the problem is no longer reproducible with v232 from stretch. Can you confirm that or is this still an issue for you? Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#822881: Systemd related services fail during early boot
On 28 Apr 2016 15:09, "Guido Günther"wrote: > > Package: systemd > Version: 229-4 > Severity: normal > > Hi, > since updating to 229 a couple of weeks ago I'm seeing these during early > boot: > > Apr 28 19:48:21 bogon systemd[1]: systemd-hwdb-update.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start Rebuild Hardware Database. > Apr 28 19:48:21 bogon systemd[1]: systemd-fsck-root.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start File System Check on Root > Device. > Apr 28 19:48:21 bogon systemd[1]: sys-fs-fuse-connections.mount: Start > request repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount FUSE Control File System. > Apr 28 19:48:21 bogon systemd[1]: sys-kernel-config.mount: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount Configuration File System. > Apr 28 19:48:21 bogon systemd[1]: systemd-binfmt.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start Set Up Additional Binary > Formats. > Apr 28 19:48:21 bogon systemd[1]: systemd-binfmt.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start Set Up Additional Binary > Formats. > Apr 28 19:48:21 bogon systemd[1]: systemd-hwdb-update.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start Rebuild Hardware Database. > Apr 28 19:48:21 bogon systemd[1]: systemd-fsck-root.service: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to start File System Check on Root > Device. > Apr 28 19:48:21 bogon systemd[1]: sys-kernel-config.mount: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount Configuration File System. > Apr 28 19:48:21 bogon systemd[1]: sys-fs-fuse-connections.mount: Start > request repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount FUSE Control File System. > Apr 28 19:48:21 bogon systemd[1]: var-lib-machines.mount: Start request > repeated too quickly. > Apr 28 19:48:21 bogon systemd[1]: Failed to mount Virtual Machine and > Container Storage. > > which makes the boot look scary due to lots of failed units but the > system boots ok otherwise Could you please attach a full boot log, with debug output[1]? These messages say they repeated too quickly, but ideally one would want to know what is triggering them repeatedly. [1] Adding systemd.log_level=debug to the kernel command line -- Saludos
Bug#822881: Systemd related services fail during early boot
Package: systemd Version: 229-4 Severity: normal Hi, since updating to 229 a couple of weeks ago I'm seeing these during early boot: Apr 28 19:48:21 bogon systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to start Rebuild Hardware Database. Apr 28 19:48:21 bogon systemd[1]: systemd-fsck-root.service: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to start File System Check on Root Device. Apr 28 19:48:21 bogon systemd[1]: sys-fs-fuse-connections.mount: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to mount FUSE Control File System. Apr 28 19:48:21 bogon systemd[1]: sys-kernel-config.mount: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to mount Configuration File System. Apr 28 19:48:21 bogon systemd[1]: systemd-binfmt.service: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to start Set Up Additional Binary Formats. Apr 28 19:48:21 bogon systemd[1]: systemd-binfmt.service: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to start Set Up Additional Binary Formats. Apr 28 19:48:21 bogon systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to start Rebuild Hardware Database. Apr 28 19:48:21 bogon systemd[1]: systemd-fsck-root.service: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to start File System Check on Root Device. Apr 28 19:48:21 bogon systemd[1]: sys-kernel-config.mount: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to mount Configuration File System. Apr 28 19:48:21 bogon systemd[1]: sys-fs-fuse-connections.mount: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to mount FUSE Control File System. Apr 28 19:48:21 bogon systemd[1]: var-lib-machines.mount: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to mount Virtual Machine and Container Storage. which makes the boot look scary due to lots of failed units but the system boots ok otherwise. Looking at the services individually I see the error as well: # systemctl status systemd-binfmt.service ● systemd-binfmt.service - Set Up Additional Binary Formats Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Do 2016-04-28 19:48:21 CEST; 10min ago none of the trigger conditions were met Docs: man:systemd-binfmt.service(8) man:binfmt.d(5) https://www.kernel.org/doc/Documentation/binfmt_misc.txt Apr 28 19:48:21 bogon systemd[1]: systemd-binfmt.service: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to start Set Up Additional Binary Formats. Apr 28 19:48:21 bogon systemd[1]: systemd-binfmt.service: Start request repeated too quickly. Apr 28 19:48:21 bogon systemd[1]: Failed to start Set Up Additional Binary Formats. It would be great if the services would start up as expected. systemd-delta has: # systemd-delta [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf Please let me know if you require any further information. I went through the bugreports but couldn't find anything related but upstream has this: https://github.com/systemd/systemd/issues/2684 Cheers, -- Guido -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.114 ii libacl1 2.2.52-3 ii libapparmor12.10-4 ii libaudit1 1:2.4.5-1+b1 ii libblkid1 2.27.1-6 ii libc6 2.22-6 ii libcap2 1:2.24-12 ii libcap2-bin 1:2.24-12 ii libcryptsetup4 2:1.7.0-2 ii libgcrypt20 1.6.5-2 ii libgpg-error0 1.21-2 ii libkmod222-1.1 ii liblzma55.1.1alpha+20120614-2.1 ii libmount1 2.27.1-6 ii libpam0g1.1.8-3.2 ii libseccomp2 2.3.0-1 ii libselinux1 2.4-3+b1 ii libsystemd0 229-4 ii mount 2.27.1-6 ii util-linux 2.27.1-6 Versions of packages systemd recommends: ii dbus1.10.8-1 ii libpam-systemd 229-4 Versions of packages systemd suggests: ii systemd-container 229-4 pn systemd-ui Versions of packages systemd is related to: