Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1346082
| Summary: | systemd reports multiple failures after upgrade to F24 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bojan Smojver <bojan> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | atigro, beltrami, bojan, johannbg, jsynacek, lnykryn, mathieu-acct, msekleta, muadda, perutka.ondrej, ssahani, s, systemd-maint, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-22 06:34:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Bojan Smojver
2016-06-13 22:05:29 UTC
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 *** |