| Summary: | systemd-38-3.fc17 prevents machine from booting "multiuser" | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | johannbg, lpoetter, metherid, mschmidt, mtasaka, notting, plautrba, systemd-maint, waltersheridan |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-13 12:35:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Michal Jaegermann
2012-01-14 00:34:15 UTC
What's the SELinux mode? Try with 'enforcing=0'. (In reply to comment #1) > What's the SELinux mode? Try with 'enforcing=0'. It is off. Forgot to mention that. On the system in question selinux is never in use. I can see one more option. Due to a bug 768778 a dracut is not updated to the current one. Maybe this has something to do with it? I will check that later. Only if this is the case then the whole concotion is getting waaaay to fragile for a sane init. When in the rescue shell, does "systemctl --failed" list any units?
Does "systemctl status systemd-journald.{socket,service}" show both units as running?
What syslog implementation do you use? rsyslog?
(In reply to comment #2) > > I can see one more option. Due to a bug 768778 a dracut is not updated to the > current one. Yes, that was behind it. After hacking broken dracut-014-9.git20111215.fc17.noarch to produce a usable initrd I was able to boot using systemd-38-3.fc17. Only I immediately run into then next bug 781657 (no reboot/shutdown). > ... does "systemctl --failed" list any units? Booting that way an older kernel with initrtd produces by the previous dracut and running "systemctl --failed" gets me: systemd-journald.service loaded failed and nothing else (even with "--all"). I am really glad that this is not a remote machine or I would be totally screwed. I see this issue on both current rawhide and also on F-16 (from perhaps systemd-37-6.fc16) (In reply to comment #5) > I see this issue on both current rawhide and also on F-16 > (from perhaps systemd-37-6.fc16) In F-16 you may be seeing bug 786182 or a similar bug in a different service. With Alt + SysRq + I it boots into graphic mode even if it hangs during "permit user sessions" Hmm, so is there anything left to fix here that bug 768778 or bug 786182 can't explain? (In reply to comment #8) > Hmm, so is there anything left to fix here that bug 768778 or bug 786182 can't > explain? AFAICT I already replied to this "No" in a comment #4 from 2012-01-13. Some other people added later comments indicating that they still have issues. What is a status with these I have no idea. OK, people should probably report new bugs if there's something to fix here from anybody but the original reporter. Closing. |