[opensuse-support] wicked (auto4, dhcp4, dhcp6) timeouts/fails with static network configuration
Hello all, after doing a 'zypper dup' from openSUSE Leap 42.3 (x86_64) to openSUSE Leap 15.1 (only openSUSE Repos) wickedd-auto4.service, wickedd-dhcp4.service, wickedd-dhcp6.service enter failed status roughly 50% of the boots. Even worse sometimes network services like SSH don't start up, either. Everything was working fine under openSUSE Leap 42.3. What really puzzles me is that the entire network configuration is static and only IPv4. So why do these 3 services have to run at all? The versions used are: --- snip --- box:~ # rpm -qa | grep wick | sort libwicked-0-6-0.6.54-lp151.1.1.x86_64 wicked-0.6.54-lp151.1.1.x86_64 wicked-service-0.6.54-lp151.1.1.x86_64 --- snap --- If it works, they roughly take a minute (still, way too long): --- snip --- box:~ # systemd-analyze blame | less -S 1min 1.899s wickedd-dhcp4.service 1min 1.893s wickedd-dhcp6.service 1min 1.887s wickedd-auto4.service 5.586s wicked.service 3.322s postfix.service [...] --- snap --- If it doesn't, they run ~ 90 seconds and timeout: --- snip --- box:~ # systemd-analyze blame | less -S 1min 30.242s wickedd-dhcp4.service 1min 30.241s wickedd-dhcp6.service 1min 30.240s wickedd-auto4.service 48.125s wickedd.service 5.674s wicked.service [...] --- snap --- Upon failure I see this in /var/log/messages: --- snip --- Jun 1 01:25:18 box systemd[1]: Starting wicked AutoIPv4 supplicant service... Jun 1 01:25:18 box systemd[1]: Starting wicked DHCPv4 supplicant service... Jun 1 01:25:18 box systemd[1]: Starting wicked DHCPv6 supplicant service... Jun 1 01:26:48 box systemd[1]: wickedd-auto4.service: Start operation timed out. Terminating. Jun 1 01:26:48 box systemd[1]: wickedd-dhcp6.service: Start operation timed out. Terminating. Jun 1 01:26:48 box systemd[1]: wickedd-dhcp4.service: Start operation timed out. Terminating. --- snap --- Sometimes accompanied by: --- snip --- Jun 1 08:36:19 box wickedd-nanny[879]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: Jun 1 08:36:19 box wickedd-nanny[879]: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files Jun 1 08:36:19 box wickedd-nanny[879]: Couldn't refresh list of active network interfaces --- snap --- If it's working I just see the services reading their config files: --- snip --- Jun 1 01:18:50 box systemd[1]: Starting wicked DHCPv4 supplicant service... Jun 1 01:18:50 box systemd[1]: Starting wicked DHCPv6 supplicant service... Jun 1 01:18:50 box systemd[1]: Starting wicked AutoIPv4 supplicant service... Jun 1 01:19:51 box wickedd-dhcp6[888]: Reading config file /etc/wicked/common.xml Jun 1 01:19:51 box wickedd-auto4[889]: Reading config file /etc/wicked/common.xml --- snap --- Like I said, no DHCP, no IPv6 configured at all. I tried disabling them via 'systemctl mask wickedd-auto4.service' etc. but that doesn't seem to change the overall behavior (works roughly 50% of the time). I'd appreciate any help/pointers/... in getting this to work! Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 01.06.19 um 09:49 schrieb Till Dörges:
after doing a 'zypper dup' from openSUSE Leap 42.3 (x86_64) to openSUSE Leap 15.1 (only openSUSE Repos) wickedd-auto4.service, wickedd-dhcp4.service, wickedd-dhcp6.service enter failed status roughly 50% of the boots. Even worse sometimes network services like SSH don't start up, either.
Everything was working fine under openSUSE Leap 42.3.
From the looks of it, the wicked problems seem to merely have been symptoms of a problem with firewalld configuration.
The configuration in 'yast firewall' looked just fine, but on the command line 'firewall-cmd --list-all-zones' both interfaces were assigned to the wrong zone. (I'm positive to have entered the configuration correctly in yast.) After redoing the configuration in 'yast firewall' 'firewall-cmd --list-all-zones' correctly reflects the configurations and wickedd-*.service don't seem to fail anymore.
What really puzzles me is that the entire network configuration is static and only IPv4. So why do these 3 services have to run at all?
That's still something I'd like to understand... Regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 01.06.19 um 10:59 schrieb Till Dörges:
Am 01.06.19 um 09:49 schrieb Till Dörges:
after doing a 'zypper dup' from openSUSE Leap 42.3 (x86_64) to openSUSE Leap 15.1 (only openSUSE Repos) wickedd-auto4.service, wickedd-dhcp4.service, wickedd-dhcp6.service enter failed status roughly 50% of the boots. Even worse sometimes network services like SSH don't start up, either.
Everything was working fine under openSUSE Leap 42.3.
From the looks of it, the wicked problems seem to merely have been symptoms of a problem with firewalld configuration.
The configuration in 'yast firewall' looked just fine, but on the command line 'firewall-cmd --list-all-zones' both interfaces were assigned to the wrong zone. (I'm positive to have entered the configuration correctly in yast.)
After redoing the configuration in 'yast firewall' 'firewall-cmd --list-all-zones' correctly reflects the configurations and wickedd-*.service don't seem to fail anymore.
Unfortunately I have to correct myself. I see less of these hangups, but the problem is still there. I now have a babysitter script in place that simply tries starting wicked.service again, but that's not my preferred solution.
What really puzzles me is that the entire network configuration is static and only IPv4. So why do these 3 services have to run at all?
That's still something I'd like to understand...
Like I said, I'd appreciate any help/pointers/... in getting this to work! Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op zondag 2 juni 2019 22:47:56 CEST schreef Till Dörges:
Am 01.06.19 um 09:49 schrieb Till Dörges:
after doing a 'zypper dup' from openSUSE Leap 42.3 (x86_64) to openSUSE Leap 15.1 (only openSUSE Repos) wickedd-auto4.service, wickedd-dhcp4.service, wickedd-dhcp6.service enter failed status roughly 50% of the boots. Even worse sometimes network services like SSH don't start up, either.
Everything was working fine under openSUSE Leap 42.3.
From the looks of it, the wicked problems seem to merely have been symptoms of a problem with firewalld configuration.
The configuration in 'yast firewall' looked just fine, but on the command line 'firewall-cmd --list-all-zones' both interfaces were assigned to the wrong zone. (I'm positive to have entered the configuration correctly in yast.)
After redoing the configuration in 'yast firewall' 'firewall-cmd --list-all-zones' correctly reflects the configurations and wickedd-*.service don't seem to fail anymore. Unfortunately I have to correct myself. I see less of these hangups, but the
Am 01.06.19 um 10:59 schrieb Till Dörges: problem is still there.
I now have a babysitter script in place that simply tries starting wicked.service again, but that's not my preferred solution.
What really puzzles me is that the entire network configuration is static and only IPv4. So why do these 3 services have to run at all?
That's still something I'd like to understand...
Like I said, I'd appreciate any help/pointers/... in getting this to work!
Thanks and regards -- Till Till, please try this: sudo rm /etc/resolv.conf sudo netconfig -f update and see if that improves things.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 03.06.19 um 00:34 schrieb Knurpht-openSUSE:
after doing a 'zypper dup' from openSUSE Leap 42.3 (x86_64) to openSUSE Leap 15.1 (only openSUSE Repos) wickedd-auto4.service, wickedd-dhcp4.service, wickedd-dhcp6.service enter failed status roughly 50% of the boots. Even worse sometimes network services like SSH don't start up, either.
Everything was working fine under openSUSE Leap 42.3. [...] What really puzzles me is that the entire network configuration is static and only IPv4. So why do these 3 services have to run at all?
That's still something I'd like to understand...
Till, please try this: sudo rm /etc/resolv.conf sudo netconfig -f update and see if that improves things.
It changed things. ;-) Now /var/run/netconfig/resolv.conf is a symlink /etc/resolv.conf. The generated /var/run/netconfig/resolv.conf had exactly the same configuration as the previous /etc/resolv.conf: --- snip --- box:~ # ll /etc/resolv.conf* -rw-r--r-- 1 root root 905 Jun 20 2012 /etc/resolv.conf -rw-r--r-- 1 root root 905 May 31 09:00 /etc/resolv.conf.netconfig box:~ # rm /etc/resolv.conf /etc/resolv.conf.netconfig box:~ # netconfig -f update box:~ # ll /etc/resolv.conf* lrwxrwxrwx 1 root root 30 Jun 3 11:57 /etc/resolv.conf -> /var/run/netconfig/resolv.conf --- snap --- Upon one test-reboot I didn't experience a hangup, but the problem didn't occur on every boot. So I'll keep monitoring. Out of curiosity: I understand having a symlink apparently is the netconfig-way, but should the above change really change the behavior? Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de Tel. +49 - 40 - 244 2407 - 0 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 03.06.19 um 16:02 schrieb Till Dörges:
Upon one test-reboot I didn't experience a hangup, but the problem didn't occur on every boot. So I'll keep monitoring.
FTR, it did not work. I'm still looking for ways to debug this further. Regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (2)
-
Knurpht-openSUSE -
Till Dörges