Bug 691075
| Summary: | Boot up stalls for excessive amount of time | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike Chambers <mike> | ||||||||
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> | ||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 15 | CC: | aneil2, johannbg, lpoetter, metherid, mschmidt, notting, plautrba, tante | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-04-28 15:14: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: | |||||||||||
| Attachments: |
|
||||||||||
Could you attach /etc/fstab? And booting with "systemd.log_level=debug" will give more detailed information in /var/log/messages. Created attachment 487953 [details]
fstab file
Created attachment 487957 [details]
Messages in systemd debug mode
systemd.log_level=debug with latest /var/log/messages file.
I see a couple of bugs in the log: - network.target is reached long before NetworkManager is even started. (network.service is not enabled on this system). This should be fixed in the next systemd+NM upstream releases according to http://lists.freedesktop.org/archives/systemd-devel/2011-March/001692.html - local-fs.target is blocking on the NFS mount (indirectly via quotaon.service and quotacheck.service). This will be fixed in the next systemd upstream release by the commit http://cgit.freedesktop.org/systemd/commit/?id=0c380104cfc52b69ab39737722e8e91fbad6c676 (the special quota dependencies will not be added for nfs filesystems) Is there something I can edit/change to test/try out in mean time to help with the delay until I fix is out? To avoid the first problem you can use the classic network scripts: systemctl enable network.service To avoid the second problem you can disable quotas: systemctl disable quotaon.service quotacheck.service As much as I would rather keep my system to the defaults, changing over to classic network and turning off quotas def did the trick. Didn't stopwatch time it, but think from grub to desktop took less than a minute. Hoping the fixes get out soon. *** Bug 691908 has been marked as a duplicate of this bug. *** On current F15, if you run "systemctl enable NetworkManager-wait-online.service", do things work then for you on the next reboot? [root@scrappy system]# systemctl enable NetworkManager-wait-online.service Couldn't find NetworkManager-wait-online.service. [root@scrappy system]# rpm -qa |grep NetworkManager NetworkManager-openvpn-0.8.998-1.git20110405.fc15.x86_64 NetworkManager-glib-0.8.998-2.git20110406.fc15.x86_64 NetworkManager-pptp-0.8.998-1.fc15.x86_64 NetworkManager-0.8.998-2.git20110406.fc15.x86_64 evolution-NetworkManager-3.0.0-1.fc15.x86_64 NetworkManager-vpnc-0.8.998-1.git20110405.fc15.x86_64 [root@scrappy system]# rpm -qa |grep systemd systemd-units-24-1.fc15.x86_64 systemd-24-1.fc15.x86_64 System has been running somewhat better as of late and have done a new install or 2 since then.. Just stopwatched the boot and takes bout 1 minute 40 seconds from grub to desktop. Think the networkmanager wait online service should do that automatically or built in to or something? Anyway, as mentioned above, that service isn't on here or at least not working. Didn't see it in /lib/systemd/service (?) neither. requires a newer NM, from koji/bodhi. Sorry, I meant to comment couple days ago and think got sidetracked haha. Anyway, boot up seems fine and even have the wait-online.service enabled (guess got the newer NM you were referring to). Haven't seen anything to complain about yet. NetworkManager-pptp-0.8.998-1.fc15.x86_64 evolution-NetworkManager-3.0.1-1.fc15.x86_64 NetworkManager-openvpn-0.8.998-1.git20110405.fc15.x86_64 NetworkManager-glib-0.8.998-3.git20110419.fc15.x86_64 NetworkManager-0.8.998-3.git20110419.fc15.x86_64 NetworkManager-vpnc-0.8.998-1.git20110405.fc15.x86_64 systemd-units-25-1.fc15.x86_64 systemd-25-1.fc15.x86_64 [mike@scrappy ~]$ sudo systemctl enable NetworkManager-wait-online.service ln -s '/lib/systemd/system/NetworkManager-wait-online.service' '/etc/systemd/system/multi-user.target.wants/NetworkManager-wait-online.service' Can close if you want as I'm satisfied currently. OK, thanks. Will close. |
Created attachment 487831 [details] Trimmed copy of /var/log/message file to show the last reboot Description of problem:During a reboot, system takes almost 5 minutes to boot Version-Release number of selected component (if applicable):systemd-20-1.fc15.x86_64 How reproducible:Always Steps to Reproduce: 1.Install current F15 using KDE 2.Mount an nfs directory on the system 3.reboot Actual results:System pauses for 1-3 minutes at couple places during boot Expected results:System should boot up rather quickly (or lot faster than is now) Additional info: Going to attach my /var/log/messages file so you can see the results and the time delay. There will be a pause between a printer message, then a home-download.mount message. The printer is attached via usb, works just fine, as well as scan and everything else. Don't think that is what is causing the delay. Think it has to do with trying to auto mount my nfs dir and don't think dns/networking is running at that point, so therefore it won't work.