FS#48267 - [systemd] "Start request repeated too quickly" after update to 229.2
Attached to Project:
Arch Linux
Opened by Elvis Stansvik (estan) - Saturday, 20 February 2016, 09:35 GMT
Last edited by Dave Reisner (falconindy) - Monday, 22 February 2016, 12:34 GMT
Opened by Elvis Stansvik (estan) - Saturday, 20 February 2016, 09:35 GMT
Last edited by Dave Reisner (falconindy) - Monday, 22 February 2016, 12:34 GMT
|
Details
Description:
After updating 228-4 => 229-2, a bunch of units fail with "Start request repeated too quickly." in the journal. Others are having the same problem with this upgrade: https://bbs.archlinux.org/viewtopic.php?id=209100 Additional info: * libsystemd 229-2 * systemd 229-2 * systemd-sysvcompat 229-2 Steps to reproduce: * Accept the upgrade to 229-2 of the systemd packages and reboot. * Look at the startup log. |
This task depends upon
Closed by Dave Reisner (falconindy)
Monday, 22 February 2016, 12:34 GMT
Reason for closing: Upstream
Additional comments about closing: https://github.com/systemd/systemd/issue s/2684
Monday, 22 February 2016, 12:34 GMT
Reason for closing: Upstream
Additional comments about closing: https://github.com/systemd/systemd/issue s/2684
systemctl --failed
[root@ai ~]# systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
journalctl -b
lut 20 22:54:42 ai systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to start Rebuild Hardware Database.
lut 20 22:54:42 ai systemd[1]: sys-fs-fuse-connections.mount: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to mount FUSE Control File System.
lut 20 22:54:42 ai systemd[1]: ldconfig.service: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to start Rebuild Dynamic Linker Cache.
lut 20 22:54:42 ai systemd[1]: systemd-binfmt.service: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to start Set Up Additional Binary Formats.
lut 20 22:54:42 ai systemd[1]: systemd-firstboot.service: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to start First Boot Wizard.
lut 20 22:54:42 ai systemd[1]: systemd-sysusers.service: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to start Create System Users.
lut 20 22:54:42 ai systemd[1]: var-lib-machines.mount: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to mount Virtual Machine and Container Storage.
lut 20 22:54:42 ai systemd[1]: ldconfig.service: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to start Rebuild Dynamic Linker Cache.
lut 20 22:54:42 ai systemd[1]: systemd-binfmt.service: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to start Set Up Additional Binary Formats.
lut 20 22:54:42 ai systemd[1]: var-lib-machines.mount: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to mount Virtual Machine and Container Storage.
lut 20 22:54:42 ai systemd[1]: systemd-firstboot.service: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to start First Boot Wizard.
lut 20 22:54:42 ai systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
lut 20 22:54:42 ai systemd[1]: Failed to start Rebuild Hardware Database.
for service in `journalctl -b | grep quick | grep "\.service" | cut -d ' ' -f 6 | cut -d ':' -f 1 | sort | uniq`; do systemctl status $service; done > reason.txt
is this sufficient?
Command that you gave did not output anything. It may have added last two lines from journal.
I'll try now to `touch /etc/.updated && reboot` now.
[root@ai capsel]# systemctl status systemd-hwdb-update
● 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 nie 2016-02-21 16:00:49 CET; 2min 56s ago
ConditionNeedsUpdate=/etc was not met
Docs: man:hwdb(7)
man:systemd-hwdb(8)
lut 21 16:00:49 ai systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
lut 21 16:00:49 ai systemd[1]: Failed to start Rebuild Hardware Database.
lut 21 16:00:49 ai systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
lut 21 16:00:49 ai systemd[1]: Failed to start Rebuild Hardware Database.
lut 21 16:00:49 ai systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
lut 21 16:00:49 ai systemd[1]: Failed to start Rebuild Hardware Database.
lut 21 16:00:50 ai systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
lut 21 16:00:50 ai systemd[1]: Failed to start Rebuild Hardware Database.
lut 21 16:00:52 ai systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.
lut 21 16:00:52 ai systemd[1]: Failed to start Rebuild Hardware Database.
The commonality seems to be that these are all services which have start conditions which are not met. Oddly, I don't think any of these services have Restart= values, either.