Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Thomas Bächler (brain0)
Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

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
Comment by meda (meda) - Saturday, 20 February 2016, 12:36 GMT
I am living same problem
Comment by Dave Reisner (falconindy) - Saturday, 20 February 2016, 13:33 GMT
Please investigate *why* these fail. There's clearly some common denominator.
Comment by Eduardo Barretto (dodys) - Saturday, 20 February 2016, 17:06 GMT
Same problem here
Comment by Jiezhe Wang (wangjiezhe) - Sunday, 21 February 2016, 02:04 GMT
Same problem with me, too. Upgrade to 229-3 won't help.
Comment by Doug Newgard (Scimmia) - Sunday, 21 February 2016, 14:25 GMT
Instead of useless "me too" posts, how about one of you does what Dave suggested?
Comment by Kacper Kopczyński (capsel) - Sunday, 21 February 2016, 14:29 GMT
How can I find *why*? Maybe some instructions to find this?

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.
Comment by Kacper Kopczyński (capsel) - Sunday, 21 February 2016, 14:34 GMT
reason.txt - effect of:
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?
Comment by Dave Reisner (falconindy) - Sunday, 21 February 2016, 14:54 GMT
No, it isn't. It's just repeating the same thing from your journal. What happens if you run "/usr/bin/systemd-hwdb update" from 229-3?
Comment by Kacper Kopczyński (capsel) - Sunday, 21 February 2016, 15:10 GMT
I've installed systemd, libsystemd from testing repo.

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.
Comment by Dave Reisner (falconindy) - Sunday, 21 February 2016, 18:22 GMT
Please boot with the kernel commandline flag systemd.log_level=debug and post the journal.

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.
Comment by Kacper Kopczyński (capsel) - Sunday, 21 February 2016, 18:57 GMT
I've attached `journalctl -b` output.
(application/x-gzip)    log.txt.gz (247.9 KiB)
Comment by Dave Reisner (falconindy) - Sunday, 21 February 2016, 19:04 GMT Comment by Doug Newgard (Scimmia) - Sunday, 21 February 2016, 19:13 GMT
Looking at that log, this could just be a display issue.
Comment by Dave Reisner (falconindy) - Sunday, 21 February 2016, 23:40 GMT
Does anyone reporting this bug *not* have laptop-mode-tools installed? Specifically, *not* have laptop-mode.service enabled? If so, can you please post debug logs?
Comment by Dave Reisner (falconindy) - Monday, 22 February 2016, 12:34 GMT
This is definitely caused by laptop-mode-tools's udev rule, and the "errors" being thrown are non-harmful. You can follow the upstream bug report if you have a horse in this race (but I do not).

Loading...