wicked: org.opensuse.Network was not provided by any .service files

Hi,
let my tell you first, I am not familiar with systemd. So if I’m doing stupid things, please tell me :slight_smile:

I have installed LEAP 42.2 on an iMac. After booting a few times I noticed that the network interface is not coming up anymore. Doing

systemctl start wicked

on the console started the interface. As I have not seen a useful error message in journalctrl I have set “–debug all” in /usr/lib/systemd/system/wicked.service. That showed following on the next boot:


Jan 01 22:58:15 mate wicked[950]: Reading config file /etc/wicked/client.xml
Jan 01 22:58:15 mate wicked[950]: Reading config file /etc/wicked/common.xml
Jan 01 22:58:15 mate wicked[950]: __ni_config_parse_ifconfig_source: Adding ifconfig firmware:
Jan 01 22:58:15 mate wicked[950]: __ni_config_parse_ifconfig_source: Adding ifconfig compat:
Jan 01 22:58:15 mate wicked[950]: __ni_config_parse_ifconfig_source: Adding ifconfig wicked:
Jan 01 22:58:15 mate wicked[950]: Executing: /usr/sbin/wicked --debug all --systemd ifup all
Jan 01 22:58:15 mate ModemManager[940]: <info>  ModemManager (version 1.4.14) starting in system bus...
Jan 01 22:58:15 mate dbus-daemon[953]: Unknown username "srvGeoClue" in message bus configuration file
Jan 01 22:58:16 mate wicked[950]: ni_dbus_xml_register_services(scope=dbus)
Jan 01 22:58:16 mate wicked[950]: register dbus service description org.opensuse.Network.Scripts
Jan 01 22:58:16 mate wicked[950]: register dbus service description org.opensuse.Network.Team.Factory
Jan 01 22:58:16 mate wicked[950]: register dbus service description org.opensuse.Network.ManagedInterface
Jan 01 22:58:16 mate wicked[950]: register dbus service description org.opensuse.Network.Firewall
Jan 01 22:58:16 mate wicked[950]: register dbus service description org.opensuse.Network.Addrconf
Jan 01 22:58:16 mate wicked[950]: ni_objectmodel_bind_extensions()
Jan 01 22:58:16 mate wicked[950]: ni_dbus_client_open(bus_type=(null), bus_name=org.opensuse.Network)
Jan 01 22:58:16 mate wicked[950]: ni_dbus_connection_open(bus=system, name=)
Jan 01 22:58:16 mate wicked[950]: created /org/opensuse/Network/Interface as child of /org/opensuse/Network, class netif-list
Jan 01 22:58:16 mate wicked[950]: dbus error reply = org.freedesktop.DBus.Error.ServiceUnknown (The name org.opensuse.Network was not provided by any .service files)
Jan 01 22:58:16 mate wicked[950]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds:
Jan 01 22:58:16 mate wicked[950]: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files
Jan 01 22:58:16 mate wicked[950]: Couldn't refresh list of active network interfaces
Jan 01 22:58:16 mate wicked[950]: Exit with status: 1
Jan 01 22:58:16 mate dbus[953]: [system] Activating systemd to hand-off: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Jan 01 22:58:16 mate dbus[953]: [system] Successfully activated service 'org.freedesktop.systemd1'
Jan 01 22:58:16 mate systemd[1]: Network Manager is not active.
Jan 01 22:58:16 mate systemd[1]: Started Name Service Cache Daemon.
Jan 01 22:58:16 mate systemd[1]: Started Console Mouse manager.
Jan 01 22:58:16 mate systemd[1]: Started download broadcom firmware files needed for bcm43xx WLAN chips.
Jan 01 22:58:16 mate systemd[1]: Started Save/Restore Sound Card State.
Jan 01 22:58:16 mate systemd[1]: Started /etc/init.d/boot.local Compatibility.
Jan 01 22:58:16 mate systemd[1]: wicked.service: Main process exited, code=exited, status=1/FAILURE
Jan 01 22:58:16 mate systemd[1]: Failed to start wicked managed network interfaces.
Jan 01 22:58:16 mate systemd[1]: wicked.service: Unit entered failed state.
Jan 01 22:58:16 mate systemd[1]: wicked.service: Failed with result 'exit-code'.

Please note the line **dbus error reply = org.freedesktop.DBus.Error.ServiceUnknown (The name org.opensuse.Network was not provided by any .service files)
**
After looking a bit around I found that org.opensuse.Network is provied by wickedd (double d). systemctrl status wickedd gives me the wired message that wickedd/start was removed to break a dependency(?) cycle. Does someone know the problem? I am a bit confused as this is a fresh installed system (yet 6 hours old). Also I noticed that many users are switching over to network manager. But as wicked is obviously preferred by opensuse I would like to stay with wicked (tell me if you think that there is no reason for :slight_smile: ).

regards
Daniel

Please show full command output. Also, boot using “systemd.log_level=debug” on kernel command line and upload “journalctl -b” output to http://susepaste.org/.

Note also if Wicked is giving problem you can also use NetworkManager. The settings to configure wicked or select NM are Yast

Well… someone forgot to put deterministic behavior into systemd :open_mouth:

After I messed up my fresh installed system by (try) removing apparmor I decided to do a reinstall and reconfigure of the whole system (as said before, it was only a few hours old).

Now it is sometimes working, sometimes not. Sometimes it’s wickedd sometimes it’s wicked… I will keep an eye on it. Here is the message I mentioned before anyway:


Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Found ordering cycle on wickedd-nanny.service/start
Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Found dependency on wickedd.service/start
Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Found dependency on wickedd-auto4.service/start
Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Found dependency on local-fs.target/start
Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Found dependency on home-damage.mount/start
Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Found dependency on home.mount/start
Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Found dependency on network-online.target/start
Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Found dependency on network.target/start
Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Found dependency on wickedd-nanny.service/start
Jan 02 04:28:31 mate systemd[1]: wickedd-nanny.service: Breaking ordering cycle by deleting job wickedd.service/start
Jan 02 04:28:31 mate systemd[1]: wickedd.service: Job wickedd.service/start deleted to break ordering cycle starting with wickedd-nanny.service/start

I have the feeling(!!) that all that has something to do with the mount of the /home directory. It is a NFS share which - of course - has a network dependency.

regards
Daniel

Please show your /etc/fstab. systemd should recognize that /home is network mount and not add it to local-fs.target dependencies.


# cat /etc/fstab                                                                                                                                                                 
UUID=fe6f7cda-5cce-48fa-8470-78f8ce0d23d7 swap                 swap       defaults              0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /                    btrfs      defaults              0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /boot/grub2/i386-pc  btrfs      subvol=@/boot/grub2/i386-pc 0 0                                                                               
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /boot/grub2/x86_64-efi btrfs      subvol=@/boot/grub2/x86_64-efi 0 0                                                                          
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /opt                 btrfs      subvol=@/opt          0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /srv                 btrfs      subvol=@/srv          0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /tmp                 btrfs      subvol=@/tmp          0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /usr/local           btrfs      subvol=@/usr/local    0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/cache           btrfs      subvol=@/var/cache    0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/crash           btrfs      subvol=@/var/crash    0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/lib/libvirt/images btrfs      subvol=@/var/lib/libvirt/images 0 0                                                                        
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/lib/machines    btrfs      subvol=@/var/lib/machines 0 0                                                                                 
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/lib/mailman     btrfs      subvol=@/var/lib/mailman 0 0                                                                                  
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/lib/mariadb     btrfs      subvol=@/var/lib/mariadb 0 0                                                                                  
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/lib/mysql       btrfs      subvol=@/var/lib/mysql 0 0                                                                                    
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/lib/named       btrfs      subvol=@/var/lib/named 0 0                                                                                    
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/lib/pgsql       btrfs      subvol=@/var/lib/pgsql 0 0                                                                                    
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/log             btrfs      subvol=@/var/log      0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/opt             btrfs      subvol=@/var/opt      0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/spool           btrfs      subvol=@/var/spool    0 0                                                                                     
UUID=5c63ff0a-b55a-4b5f-8f0d-646a6778cc0b /var/tmp             btrfs      subvol=@/var/tmp      0 0
UUID=67E3-17ED       /boot/efi            vfat       umask=0002,utf8=true  0 0
192.168.11.1:/mnt/space/homes   /home   nfs     rw,_netdev      0 0
/home/damage/.Private   /home/damage    ecryptfs        rw,user,nosuid,nodev,relatime,ecryptfs_fnek_sig=xxxxx,ecryptfs_sig=yyyyy,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs 0 0

Just noticed that “/home/damage” is missing “noauto”

Add _netdev to /home/damage options in /etc/fstab. This should force systemd to treat it as remote filesystem (which it is indirectly, because it depends on remote filesystem) and avoid dependency loop.