|
Bugzilla – Full Text Bug Listing |
| Summary: | Systemd hangs for a few seconds before completing boot process | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Ursan Marius Bogdan <Creationn> |
| Component: | Basesystem | Assignee: | Frederic Crozat <fcrozat> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | cyberorg, mt, raul.malea |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
dmesg log for systemd boot process
systemd blame dmesg log boot svg file systemd dmesg debug |
||
Don`t know if this is related but here is a line from /var/log/messages:
dbus[1018]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
Console output for that command is:
dbus-org.freedesktop.NetworkManager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
To see how things are going i had tried Network Manager + systemd; in network manager i had used manual configuration since i own a router and i had reserved the first ip for the MAC of my LAN card. I was suprised to see that my PC booted faster with network manager handling the connection rather than ifup; LED for the LAN connection still flickered showing up a transaction between the onboard lan-card and the dhcp server of the router but it was made much faster. For the first time in 6 years i was happy to use network manager under openSUSE so i must assume that ifup+systemd don`t mix to well, a shame really since not all users are managing their network connection thru network manager. please remove /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service, it is a leftover of Factory (and Tumbleweed 11.4). to better find what is causing the issue, check : systemd-analyze blame systemd-analyze plot > boot.svg and check svg file and try to boot with systemd.log_level=debug systemd.log_target=kmsg and attach dmesg output Created attachment 464535 [details]
systemd blame
Created attachment 464538 [details]
dmesg log
Both blame and dmesg are attached. How do i delete that leftover and how do i add that line "systemd.log_level=debug systemd.log_target=kmsg" ? And how do i use that svg? imageshack won`t let me upload it on their site. attach the svg file to this bug report ? systemd.log_level=debug systemd.log_target=kmsg should be added to boot commandline (and dmesg output is useful only when booting with those options). Created attachment 464557 [details]
boot svg file
I'm not sure to understand what is your exact issue. Created attachment 464558 [details]
systemd dmesg debug
I hope i got the dmesg log file right. Still how do i remove "/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service" ? Long story shot: 1. if i use ifup the boot process hangs for a few seconds right at the network configuration part (led for the lan connection stops and then starts) and then continues to load normally 2. if i use network manager the hang time does not happen even if the led for the lan connection still stops and then starts. run to remove the file: rm /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service adding mt, he is our network overlord creation:/etc/systemd/system # ls -all total 40 drwxr-xr-x 10 root root 4096 Nov 29 16:03 . drwxr-xr-x 4 root root 4096 Nov 17 09:59 .. lrwxrwxrwx 1 root root 40 Nov 17 10:02 dbus-org.freedesktop.Avahi.service -> /lib/systemd/system/avahi-daemon.service lrwxrwxrwx 1 root root 36 Nov 17 09:59 default.target -> /lib/systemd/system/runlevel5.target drwxr-xr-x 2 root root 4096 Nov 17 09:59 default.target.wants drwxr-xr-x 2 root root 4096 Nov 17 09:59 getty.target.wants lrwxrwxrwx 1 root root 9 Nov 29 16:03 klogd.service -> /dev/null drwxr-xr-x 2 root root 4096 Nov 17 13:26 multi-user.target.wants drwxr-xr-x 2 root root 4096 Nov 17 10:27 network.target.wants drwxr-xr-x 2 root root 4096 Nov 17 13:26 runlevel2.target.wants drwxr-xr-x 2 root root 4096 Nov 17 13:26 runlevel3.target.wants drwxr-xr-x 2 root root 4096 Nov 17 13:26 runlevel5.target.wants drwxr-xr-x 2 root root 4096 Nov 17 10:02 sockets.target.wants creation:/etc/systemd/system # I don`t have that service in /etc/systemd/system/; any other places where it might be ? try : find / -name dbus-org.freedesktop.NetworkManager.service Weird, find did not found anything... Good day, its been while since i did not report anything about my issue. During this time i got a new version of the linux kernel and of systemd. My system boots normally now and does not hang anymore. I`m closing this bug. |
Created attachment 462684 [details] dmesg log for systemd boot process User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 Upgraded my system today from 11.4 Tumbleweed to 12.1 Tumbleweed and after the hole process i did reboot my pc. While using sysvinit the system boots fine with no issues but since the default is now systemd when booting using it, the boot process hangs for a few seconds. During that time i see that LED`s from my router flicker especially the one for Lan connection. Bellow i will add a dmesg log to help you. As a way to configure my network connection i use ifup+dhcp. Reproducible: Always