Description of problem: Jun 13 18:28:27: Failed to start Rebuild Hardware Database. Jun 13 18:28:27: multipathd.service: Start request repeated too quickly. Jun 13 18:28:27: Failed to start Device-Mapper Multipath Device Controller. Jun 13 18:28:27: systemd-binfmt.service: Start request repeated too quickly. Jun 13 18:28:27: Failed to start Set Up Additional Binary Formats. Jun 13 18:28:27: systemd-modules-load.service: Start request repeated too quickly. Jun 13 18:28:27: Failed to start Load Kernel Modules. Jun 13 18:28:27: sys-fs-fuse-connections.mount: Start request repeated too quickly. Jun 13 18:28:27: Failed to mount FUSE Control File System. Jun 13 18:28:27: ldconfig.service: Start request repeated too quickly. Jun 13 18:28:27: Failed to start Rebuild Dynamic Linker Cache. Jun 13 18:28:27: systemd-firstboot.service: Start request repeated too quickly. Jun 13 18:28:27: Failed to start First Boot Wizard. Jun 13 18:28:27: systemd-sysusers.service: Start request repeated too quickly. Jun 13 18:28:27: Failed to start Create System Users. Jun 13 18:28:27: systemd-ask-password-console.path: Start request repeated too quickly. Jun 13 18:28:27: Failed to start Dispatch Password Requests to Console Directory Watch. Version-Release number of selected component (if applicable): systemd-229-8.fc24.x86_64 How reproducible: Always. Steps to Reproduce: 1. Boot (ThinkPad T450s, upgrade from F23 using distro-sync). 2. Watch the failures in journal, console, boot.log etc. Actual results: Multiple failed starts. Expected results: Worked on F23. Additional info: Possibly: https://github.com/systemd/systemd/issues/2684
I've been running F24 since pre-alpha on a T440s and don't remember seeing anything like this. Did you reboot after update? Does it happen every boot? If yes, does setting selinux to permissive help?
(In reply to Jan Synacek from comment #1) > Did you reboot after update? Yes, multiple times. > Does it happen every boot? Yes. > If yes, does setting selinux to permissive help? Tried that, but sadly no. If it helps or is related, I also noticed other strange anomalies, like nscd not picking up /etc/resolv.conf, which then results in DNS not working correctly. So, I worked around that by putting something like this in /etc/systemd/system/nscd.service.d: ---------- [Unit] Requires=network-online.target After=network-online.target ----------
Output of the status command: ------------------- ● systemd-hwdb-update.service - Rebuild Hardware Database Loaded: loaded (/usr/lib/systemd/system/systemd-hwdb-update.service; static; vendor preset: disabled) Active: inactive (dead) Condition: start condition failed at Tue 2016-06-14 13:21:42 AEST; 1 day 1h ago Docs: man:hwdb(7) man:systemd-hwdb(8) Jun 14 13:21:42 <host> systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly. Jun 14 13:21:42 <host> systemd[1]: Failed to start Rebuild Hardware Database. ------------------- So, the condition failed (probably because /etc/udev/hwdb.d is empty), so this wasn't supposed to be started anyway, if I understand things correctly. So, why does systemd repeat the start request? Maybe my computer is too fast... :-) Every single unit in that list failed the same way: start condition failed.
Zbyszek, any idea?
I have the same problem on my ThinkPad W520 after upgrading from F23 to F24.
Yes, Patch https://github.com/systemd/systemd/commit/7629ec4642b03517742d09b7303c204fddf82108 fixes this issue.
Could we get a build into testing based on the above patch?
*** This bug has been marked as a duplicate of bug 1350686 ***