Bug 695072
| Summary: | firstboot doesn not show up because system stuck in Starting D-Bus System message Bus | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jaroslav Franek <jarin.franek> |
| Component: | dracut | Assignee: | Lennart Poettering <lpoetter> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | harald, johannbg, jonathan, lpoetter, metherid, mschmidt, notting, plautrba |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-04-10 19:29:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jaroslav Franek
2011-04-10 10:49:23 UTC
Please make sure you wait at least 3 minutes. If a service is stuck, this is the default timeout when systemd gives up on it and tries to continue with the followup units.
Adam Williamson was seeing some issues with composes using dracut-008. It may be related. dracut would be the first thing I'd try updating (dracut-009-5.fc15 is on the way to stable) to see if that fixes the problem. ("dracut -f" then has to be run manually.)
Also "enforcing=0" is always a good test to see if it is SELinux-related.
For the record, I was waiting all the time I was writing the problem report and retyping the screen of the stuck system, so it was about 15 minutes. Nothing had happened during that time... Just a note, when you install pre-release then testing repository is by default enabled, not only stable. Bodhi says dracut-009-5 was submitted 2011-03-31 to testing, my installation was 2011-04-09, so it is probably there (can't access the system at the moment to verify). I will give it another try and disable SELinux. Oki, fresh new network install and got firstboot up and running, and my machine is back from zombieland :-) Seems like a proper fix was pushed into install repos just while ago. No need to play with SELinux. Most probably it was related to dracut issue mentioned by Michal, however I did not experience any tracebacks with Anaconda installer. Marking it a duplicate of Bug#694712 anyway, to keep logical relationship. Appologies for blaming systemd (which is an easy target to blame for all kinds of issues). *** This bug has been marked as a duplicate of bug 694712 *** |