Am 06.05.2015 um 21:18 schrieb Hendrik Woltersdorf:
Am 06.05.2015 um 21:08 schrieb Yamaban:
On Wed, 6 May 2015 20:26, Olaf Hering <olaf@...> wrote:
On Tue, May 05, Ludwig Nussel wrote:
Changed packages: ...
For me network is broken, tested only booting a dom0. 'systemctl start wicked.service' started the network as expected. My guess: there are wrong Before=/After= lines in various .services:
root@optiplex:~ # journalctl -b | grep delete Mai 06 20:05:25 optiplex systemd[1]: Job NetworkManager-wait-online.service/start deleted to break ordering cycle starting with network.target/start Mai 06 20:05:25 optiplex systemd[1]: Job NetworkManager.service/verify-active deleted to break ordering cycle starting with network.target/start Mai 06 20:05:25 optiplex systemd[1]: Job wicked.service/start deleted to break ordering cycle starting with network.target/start Mai 06 20:05:25 optiplex systemd[1]: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start Mai 06 20:05:28 optiplex systemd[1]: Job YaST2-Second-Stage.service/start deleted to break ordering cycle starting with NetworkManager.service/verify-active Mai 06 20:05:28 optiplex systemd[1]: Job NetworkManager-wait-online.service/start deleted to break ordering cycle starting with NetworkManager.service/verify-active Mai 06 20:05:29 optiplex systemd[1]: Job xinetd.service/start deleted to break ordering cycle starting with NetworkManager.service/verify-active Mai 06 20:05:29 optiplex systemd[1]: Job network.target/start deleted to break ordering cycle starting with NetworkManager.service/verify-active Mai 06 20:05:29 optiplex systemd[1]: Job xenstored.socket/start deleted to break ordering cycle starting with sockets.target/start Mai 06 20:05:29 optiplex systemd[1]: Job proc-xen.mount/start deleted to break ordering cycle starting with sockets.target/start Mai 06 20:05:29 optiplex systemd[1]: Job sockets.target/start deleted to break ordering cycle starting with sockets.target/start Mai 06 20:05:29 optiplex systemd[1]: Job wicked.service/start deleted to break ordering cycle starting with YaST2-Firstboot.service/start Mai 06 20:06:33 optiplex /usr/lib/gdm/gdm-x-session[1534]: Entry deleted from font path.
I think the subject should read 20150505, thats why me /etc/issue has. But perhaps I run the to-be-released snapshot?!
1 | factory-Essentials | factory-Essentials | Yes | Yes | http://packman.inode.at/suse/Factory/Essentials 2 | factory-Extra | factory-Extra | Yes | Yes | http://packman.inode.at/suse/Factory/Extra 3 | factory-Games | factory-Games | Yes | Yes | http://packman.inode.at/suse/Factory/Games 4 | factory-Multimedia | factory-Multimedia | Yes | Yes | http://packman.inode.at/suse/Factory/Multimedia 5 | factory-debug | factory-debug | Yes | Yes | http://download.opensuse.org/factory/repo/debug/ 6 | factory-non-oss | factory-non-oss | Yes | Yes | http://download.opensuse.org/factory/repo/non-oss/ 7 | factory-oss | factory-oss | Yes | Yes | http://download.opensuse.org/factory/repo/oss/ 10 | obs-network_wicked_master | obs-network_wicked_master | Yes | Yes | http://download.opensuse.org/repositories/network:/wicked:/master/openSUSE_F...
13 | remote-packman-essentials | remote-packman-essentials | Yes | Yes | http://packman.inode.at/suse/Factory/Essentials 14 | remove-Virtualization | remove-Virtualization | Yes | Yes | http://download.opensuse.org/repositories/Virtualization/openSUSE_Factory
A few hints to solve that.
As you have included your repo-list, and seeing "/network:/wicked:/master/" there, this rises the question, where are your "wicked" packages from?
either with "rpm -qi {package}", see "Vendor" field, or with zypper se -s wicked
Please check for these packages: libwicked wicked wicked-service sysconfig sysconfig-netconfig
Either with "rpm -qi {package}", see "Vendor" field, or with "zypper se -s wicked sysconfig", see "repo" field.
For these Packages it should be either "factory-oss" or "obs-network_wicked_master" but not mixed in the installation.
Next question: where points "network.service" to? systemctl status network.service5~
If you want to use wicked, please disable NetworkManager, and enable wicked after that.
systemctl disable NetworkManager.service systemctl enable wicked.service systemctl daemon-reload
After that wicked should work as expected again after the next reboot.
- Yamaban
Hi,
I've got the same problem with NetworkManager:
Mai 06 21:10:29 linux-yb52 systemd[1]: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start
and less repositories:
# | Alias | Name | Enabled | Refresh --+-------------------------------------+-----------------------------+---------+-------- 1 | Packman | Packman | Yes | Yes 2 | http-download.opensuse.org-55ced6b4 | X11:RemoteDesktop | No | No 3 | openSUSE-20150225-0 | openSUSE-20150225-0 | No | No 4 | ownclowd-Desktop | ownclowd-Desktop | Yes | Yes 5 | repo-debug | openSUSE-Tumbleweed-Debug | No | Yes 6 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | Yes 7 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | Yes 8 | repo-source | openSUSE-Tumbleweed-Source | No | Yes 9 | repo-update | openSUSE-Tumbleweed-Update | Yes | Yes
Hendrik
I just got the network up again by disabling systemd-timesyncd.service Even though there are still "deleted" messages: ai 06 21:37:56 linux-yb52 systemd[1]: Job YaST2-Firstboot.service/start deleted to break ordering cycle starting with NetworkManager.service/start Mai 06 21:37:56 linux-yb52 systemd[1]: Job SuSEfirewall2_init.service/start deleted to break ordering cycle starting with NetworkManager.service/start Mai 06 21:37:56 linux-yb52 systemd[1]: Job YaST2-Second-Stage.service/start deleted to break ordering cycle starting with NetworkManager.service/start Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org