SOLVED: openSUSE Tumbleweed does not start network interface after reboot
this post
–-
One of my servers, an experimental instance running openSUSE Tumbleweed, was just updated to the latest snapshot and now the network interface does not start automatically when the server is rebooted. I have to log onto the console via Lish and enter "wicked ifup eth0" to start it manually; otherwise, there is no network connectivity.
Network Helper does not support Tumbleweed, but networking was functioning properly before this last update. The network configuration files seem to be okay. Any ideas?
—DragonLord
3 Replies
—DragonLord
The output changes every time I reboot. Here are some examples:
[ 1.789006] systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped
[ 1.825096] systemd[1]: systemd-readahead-collect.service: Cannot add dependency job, ignoring: Unit systemd-readahead-collect.service failed to load: No such file or directory.
[ 1.828143] systemd[1]: systemd-readahead-replay.service: Cannot add dependency job, ignoring: Unit systemd-readahead-replay.service failed to load: No such file or directory.
[ 1.831182] systemd[1]: network.target: Found ordering cycle on network.target/start
[ 1.832463] systemd[1]: network.target: Found dependency on wickedd-auto4.service/start
[ 1.833784] systemd[1]: network.target: Found dependency on SuSEfirewall2_init.service/start
[ 1.835170] systemd[1]: network.target: Found dependency on YaST2-Second-Stage.service/start
[ 1.836549] systemd[1]: network.target: Found dependency on xinetd.service/start
[ 1.837767] systemd[1]: network.target: Found dependency on network.target/start
[ 1.838919] systemd[1]: network.target: Breaking ordering cycle by deleting job wickedd-auto4.service/start
[ 1.840712] systemd[1]: wickedd-auto4.service: Job wickedd-auto4.service/start deleted to break ordering cycle starting with network.target/start
[ 1.844344] systemd[1]: network.target: Found ordering cycle on network.target/start
[ 1.845541] systemd[1]: network.target: Found dependency on wickedd.service/start
[ 1.846610] systemd[1]: network.target: Found dependency on SuSEfirewall2_init.service/start
[ 1.847832] systemd[1]: network.target: Found dependency on YaST2-Second-Stage.service/start
[ 1.849050] systemd[1]: network.target: Found dependency on xinetd.service/start
[ 1.850139] systemd[1]: network.target: Found dependency on network.target/start
[ 1.851229] systemd[1]: network.target: Breaking ordering cycle by deleting job wickedd.service/start
[ 1.852740] systemd[1]: wickedd.service: Job wickedd.service/start deleted to break ordering cycle starting with network.target/start
[ 1.856034] systemd[1]: network.target: Found ordering cycle on network.target/start
[ 1.857136] systemd[1]: network.target: Found dependency on wicked.service/start
[ 1.858165] systemd[1]: network.target: Found dependency on SuSEfirewall2_init.service/start
[ 1.859344] systemd[1]: network.target: Found dependency on YaST2-Second-Stage.service/start
[ 1.860531] systemd[1]: network.target: Found dependency on xinetd.service/start
[ 1.861558] systemd[1]: network.target: Found dependency on network.target/start
[ 1.862569] systemd[1]: network.target: Breaking ordering cycle by deleting job wicked.service/start
[ 1.863946] systemd[1]: wicked.service: Job wicked.service/start deleted to break ordering cycle starting with network.target/start
[ 1.866877] systemd[1]: network.target: Found ordering cycle on network.target/start
[ 1.867909] systemd[1]: network.target: Found dependency on wickedd-nanny.service/start
[ 1.868952] systemd[1]: network.target: Found dependency on SuSEfirewall2_init.service/start
[ 1.870096] systemd[1]: network.target: Found dependency on YaST2-Second-Stage.service/start
[ 1.871252] systemd[1]: network.target: Found dependency on xinetd.service/start
[ 1.872237] systemd[1]: network.target: Found dependency on network.target/start
[ 1.873232] systemd[1]: network.target: Breaking ordering cycle by deleting job wickedd-nanny.service/start
[ 1.874678] systemd[1]: wickedd-nanny.service: Job wickedd-nanny.service/start deleted to break ordering cycle starting with network.target/start
[ 1.877701] systemd[1]: wickedd-dhcp4.service: Found ordering cycle on wickedd-dhcp4.service/start
[ 1.878970] systemd[1]: wickedd-dhcp4.service: Found dependency on SuSEfirewall2_init.service/start
[ 1.880268] systemd[1]: wickedd-dhcp4.service: Found dependency on YaST2-Second-Stage.service/start
[ 1.881546] systemd[1]: wickedd-dhcp4.service: Found dependency on xinetd.service/start
[ 1.882595] systemd[1]: wickedd-dhcp4.service: Found dependency on network.target/start
[ 1.883627] systemd[1]: wickedd-dhcp4.service: Found dependency on wickedd-dhcp4.service/start
[ 1.884846] systemd[1]: wickedd-dhcp4.service: Breaking ordering cycle by deleting job SuSEfirewall2_init.service/start
[ 1.886313] systemd[1]: SuSEfirewall2_init.service: Job SuSEfirewall2_init.service/start deleted to break ordering cycle starting with wickedd-dhcp4.service/start
[ 1.889329] systemd[1]: systemd-journald.socket: Found ordering cycle on systemd-journald.socket/start
[ 1.890604] systemd[1]: systemd-journald.socket: Found dependency on haveged.service/start
[ 1.891612] systemd[1]: systemd-journald.socket: Found dependency on systemd-random-seed.service/start
[ 1.892851] systemd[1]: systemd-journald.socket: Found dependency on systemd-remount-fs.service/start
[ 1.894102] systemd[1]: systemd-journald.socket: Found dependency on systemd-journald.socket/start
[ 1.895314] systemd[1]: systemd-journald.socket: Breaking ordering cycle by deleting job haveged.service/start
[ 1.896632] systemd[1]: haveged.service: Job haveged.service/start deleted to break ordering cycle starting with systemd-journald.socket/start
[ 1.768396] systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped
[ 1.802259] systemd[1]: systemd-readahead-collect.service: Cannot add dependency job, ignoring: Unit systemd-readahead-collect.service failed to load: No such file or directory.
[ 1.804482] systemd[1]: systemd-readahead-replay.service: Cannot add dependency job, ignoring: Unit systemd-readahead-replay.service failed to load: No such file or directory.
[ 1.806786] systemd[1]: wicked.service: Found ordering cycle on wicked.service/start
[ 1.807768] systemd[1]: wicked.service: Found dependency on SuSEfirewall2_init.service/start
[ 1.808835] systemd[1]: wicked.service: Found dependency on YaST2-Second-Stage.service/start
[ 1.809870] systemd[1]: wicked.service: Found dependency on xinetd.service/start
[ 1.810830] systemd[1]: wicked.service: Found dependency on network.target/start
[ 1.811742] systemd[1]: wicked.service: Found dependency on wicked.service/start
[ 1.812674] systemd[1]: wicked.service: Breaking ordering cycle by deleting job SuSEfirewall2_init.service/start
[ 1.814038] systemd[1]: SuSEfirewall2_init.service: Job SuSEfirewall2_init.service/start deleted to break ordering cycle starting with wicked.service/start
[ 1.817069] systemd[1]: wicked.service: Found ordering cycle on wicked.service/start
[ 1.818070] systemd[1]: wicked.service: Found dependency on YaST2-Second-Stage.service/start
[ 1.819116] systemd[1]: wicked.service: Found dependency on xinetd.service/start
[ 1.820055] systemd[1]: wicked.service: Found dependency on network.target/start
[ 1.820981] systemd[1]: wicked.service: Found dependency on wicked.service/start
[ 1.821862] systemd[1]: wicked.service: Breaking ordering cycle by deleting job YaST2-Second-Stage.service/start
[ 1.823213] systemd[1]: YaST2-Second-Stage.service: Job YaST2-Second-Stage.service/start deleted to break ordering cycle starting with wicked.service/start
[ 1.826054] systemd[1]: systemd-random-seed.service: Found ordering cycle on systemd-random-seed.service/start
[ 1.827415] systemd[1]: systemd-random-seed.service: Found dependency on systemd-journald.socket/start
[ 1.828721] systemd[1]: systemd-random-seed.service: Found dependency on haveged.service/start
[ 1.829908] systemd[1]: systemd-random-seed.service: Found dependency on systemd-random-seed.service/start
[ 1.831190] systemd[1]: systemd-random-seed.service: Breaking ordering cycle by deleting job systemd-journald.socket/start
[ 1.832614] systemd[1]: systemd-journald.socket: Job systemd-journald.socket/start deleted to break ordering cycle starting with systemd-random-seed.service/start
Any pointers?
—DragonLord
this messagehere
An extraneous service YaST2-Second-Stage.service (normally used only during initial system installation) is messing up the dependencies causing systemd to run into a race condition and randomly disable networking services. The solution is this one command:
systemctl disable YaST2-Second-Stage.service
(Your system may have started in read-only mode as a result of this bug; if this fails; reboot the instance and try again. You may need to reboot a few times because of the random nature of the problem.)
—DragonLord