Hallo,
ich habe in einer VM ein Leap 15.6 auf 16.0 migriert, das lief soweit recht gut 
Nun will ich mir Cockpit ansehen und bin wie hier beschrieben vorgegangen:
https://en.opensuse.org/Main:Cockpit
Die Installation ist ok, aber schon beim 2. Schritt wars vorbei 
localhost:~ # systemctl enable --now cockpit.socket
Created symlink '/etc/systemd/system/sockets.target.wants/cockpit.socket' → '/usr/lib/systemd/system/cockpit.socket'.
Job failed. See "journalctl -xe" for details.
Und cockpit startet natürlich nicht.
Weitere Infos.
localhost:~ # zypper se -i cockpit
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+------------------------+------------------------------------------------------------------------------+--------
i+ | cockpit | Web Console for Linux servers | package
i+ | cockpit | Pattern for Cockpit, a web based remote system management interface | pattern
i | cockpit-bridge | Cockpit bridge server-side component | package
i | cockpit-firewalld | Allows Cockpit access through the firewall | package
i | cockpit-kdump | Cockpit user interface for kernel crash dumping | package
i | cockpit-networkmanager | Cockpit user interface for networking, using NetworkManager | package
i | cockpit-packagekit | Cockpit user interface for packages | package
i | cockpit-packages | A cockpit module for (un)installing packages | package
i | cockpit-repos | A Cockpit module for managing system repositories | package
i | cockpit-storaged | Cockpit user interface for storage, using udisks | package
i | cockpit-subscriptions | Cockpit module for managing and registering subscriptions | package
i | cockpit-system | Cockpit admin interface package for configuring and troubleshooting a system | package
i | cockpit-ws | Cockpit Web Service | package
i+ | patterns-cockpit | Pattern for Cockpit, a web based remote system management interface | package
localhost:~ # systemctl status cockpit.socket
× cockpit.socket - Cockpit Web Service Socket
Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sun 2026-02-15 12:09:15 CET; 2min 14s ago
Invocation: 7fe158cac44f4981a2aa81ae55facc57
Triggers: ● cockpit.service
Docs: man:cockpit-ws(8)
Listen: [::]:9090 (Stream)
Process: 2303 ExecStartPre=/usr/libexec/check_cockpit_users (code=exited, status=1/FAILURE)
CPU: 12ms
Feb 15 12:09:15 localhost systemd[1]: Starting Cockpit Web Service Socket...
Feb 15 12:09:15 localhost check_cockpit_users[2303]: /etc/nsswitch.conf is out of date, please update it from /usr/etc/nsswitch.conf to use cockpit
Feb 15 12:09:15 localhost systemd[1]: cockpit.socket: Control process exited, code=exited, status=1/FAILURE
Feb 15 12:09:15 localhost systemd[1]: cockpit.socket: Failed with result 'exit-code'.
Feb 15 12:09:15 localhost systemd[1]: Failed to listen on Cockpit Web Service Socket.
localhost:~ # systemctl start cockpit.service
A dependency job for cockpit.service failed. See 'journalctl -xe' for details.
localhost:~ #
localhost:~ # journalctl -xe
░░ An ExecStartPre= process belonging to unit cockpit.socket has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Feb 15 12:19:38 localhost systemd[1]: cockpit.socket: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit cockpit.socket has entered the 'failed' state with result 'exit-code'.
Feb 15 12:19:38 localhost systemd[1]: Failed to listen on Cockpit Web Service Socket.
░░ Subject: A start job for unit cockpit.socket has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cockpit.socket has finished with a failure.
░░
░░ The job identifier is 3754 and the job result is failed.
Feb 15 12:19:38 localhost systemd[1]: cockpit-wsinstance-https-factory.socket: Control process exited, code=exited, status=216/GROUP
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStartChown= process belonging to unit cockpit-wsinstance-https-factory.socket has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 216.
Feb 15 12:19:38 localhost systemd[1]: cockpit-wsinstance-https-factory.socket: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit cockpit-wsinstance-https-factory.socket has entered the 'failed' state with result 'exit-code'.
Feb 15 12:19:38 localhost systemd[1]: Starting Cockpit issue updater service...
░░ Subject: A start job for unit cockpit-issue.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cockpit-issue.service has begun execution.
░░
░░ The job identifier is 3854.
Feb 15 12:19:38 localhost systemd[1]: cockpit-issue.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit cockpit-issue.service has successfully entered the 'dead' state.
Feb 15 12:19:38 localhost systemd[1]: Finished Cockpit issue updater service.
░░ Subject: A start job for unit cockpit-issue.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cockpit-issue.service has finished successfully.
░░
░░ The job identifier is 3854.
Wie bekomme ich nun cockpit zum Laufen?
