localhost:~ # systemctl enable --now cockpit.socket
Job failed. See "journalctl -xe" for details.
localhost:~ # journalctl -xe
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 315092.
Jul 07 08:53:04 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 315096.
Jul 07 08:53:04 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 315100.
Jul 07 08:53:04 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 315104.
Jul 07 08:53:04 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 315108.
Jul 07 08:53:04 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 315112.
Jul 07 08:53:04 localhost.localdomain systemd[2927]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds i>
lines 7298-7342/7342 (END)
But it’s Leap 16, not MicroOS, and he doesn’t need open ports for a local connection.
But we need to start by there’s a problem starting it or connecting to it. If you run journalctl -xe you’ll see all messages: yours were about Drkonqui. Try with journalctl -xeu cockpit.socket
Some weeks ago when I tried Leap 16, I can’t connect with the browser: it refused my name/password account even when sshd was started. But flatpack client Cockpit runs well
If you scroll up a few lines on that page you will see that there are instructions for openSUSE Leap (starting with 15.6) and openSUSE Tumbleweed as well.
Doing systemctl enable --now cockpit.socket will just start the service. To get the user interface one needs to open a web browser and go to either
From your earlier Yast post I understood you are on a VM ?, I just installed Leap 16 in a VM and had the same issue until I used the ip address for the VM and not PC address. I checked my ip address by “ip address” inside the VM, the cockpit then started fine.
Yes, I am running inside Parallels on a Mac Studio. (first time that SUSE has worked in ARM). I am not sure where you are. using the ip address, but I used localhost:9090.
Also Discover will not start.
localhost:/etc/sysconfig # zypper in cockpit cockpit-selinux python3-pcp
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
'cockpit' is already installed.
No update candidate for 'cockpit-338-160000.1.3.aarch64'. The highest available version is already installed.
'cockpit-selinux' is already installed.
No update candidate for 'cockpit-selinux-338-160000.1.3.noarch'. The highest available version is already installed.
Resolving package dependencies...
The following 6 NEW packages are going to be installed:
libpcp3 libpcp_gui2 libpcp_import1 libpcp_mmv1 pcp-conf python3-pcp
6 new packages to install.
Package download size: 1.3 MiB
Package install size change:
| 3.1 MiB required by packages that will be installed
3.1 MiB | - 0 B released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
Preloading: libpcp_mmv1-6.2.0-160000.5.16.aarch64.rpm [done]
Preloading: libpcp_import1-6.2.0-160000.5.16.aarch64.rpm [done]
Preloading: libpcp_gui2-6.2.0-160000.5.16.aarch64.rpm [done]
Preloading: python3-pcp-6.2.0-160000.5.16.aarch64.rpm [done]
Preloading: pcp-conf-6.2.0-160000.5.16.noarch.rpm [done]
Preloading: libpcp3-6.2.0-160000.5.16.aarch64.rpm [done]
Preload finished. [success (1.2 KiB/s) ] .........................................................................................................................[done]
Retrieving: pcp-conf-6.2.0-160000.5.16.noarch (repo-oss (16.0)) (1/6), 114.4 KiB
Retrieving: libpcp3-6.2.0-160000.5.16.aarch64 (repo-oss (16.0)) (2/6), 668.5 KiB
Retrieving: libpcp_mmv1-6.2.0-160000.5.16.aarch64 (repo-oss (16.0)) (3/6), 108.2 KiB
Retrieving: libpcp_import1-6.2.0-160000.5.16.aarch64 (repo-oss (16.0)) (4/6), 112.0 KiB
Retrieving: libpcp_gui2-6.2.0-160000.5.16.aarch64 (repo-oss (16.0)) (5/6), 106.8 KiB
Retrieving: python3-pcp-6.2.0-160000.5.16.aarch64 (repo-oss (16.0)) (6/6), 266.0 KiB
Checking for file conflicts: .....................................................................................................................................[done]
(1/6) Installing: pcp-conf-6.2.0-160000.5.16.noarch ..............................................................................................................[done]
(2/6) Installing: libpcp3-6.2.0-160000.5.16.aarch64 ..............................................................................................................[done]
(3/6) Installing: libpcp_mmv1-6.2.0-160000.5.16.aarch64 ..........................................................................................................[done]
(4/6) Installing: libpcp_import1-6.2.0-160000.5.16.aarch64 .......................................................................................................[done]
(5/6) Installing: libpcp_gui2-6.2.0-160000.5.16.aarch64 ..........................................................................................................[done]
(6/6) Installing: python3-pcp-6.2.0-160000.5.16.aarch64 ..........................................................................................................[done]
Running post-transaction scripts .................................................................................................................................[done]
localhost:/etc/sysconfig # systemctl start cockpit
A dependency job for cockpit.service failed. See 'journalctl -xe' for details.
So here is what I get:
~
localhost:/etc/sysconfig # journalctl -xe
░░ The job identifier is 947080.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947084.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947088.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947092.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947096.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947100.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947104.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947108.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947112.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947116.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 947120.
Jul 08 12:59:11 localhost.localdomain systemd[2927]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
localhost:/etc/sysconfig # systemctl status cockpit.socket
× cockpit.socket - Cockpit Web Service Socket
Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; preset: disabled)
Active: failed (Result: exit-code) since Tue 2025-07-08 13:04:37 EDT; 7min ago
Invocation: 76472bad67fd421db4a3d06d507eccc9
Triggers: ● cockpit.service
Docs: man:cockpit-ws(8)
Listen: [::]:9090 (Stream)
Process: 277050 ExecStartPre=/usr/libexec/check_cockpit_users (code=exited, status=1/FAILURE)
CPU: 8ms
Jul 08 13:04:37 localhost.localdomain systemd[1]: Starting Cockpit Web Service Socket...
Jul 08 13:04:37 localhost.localdomain check_cockpit_users[277050]: user cockpit-wsinstance-socket exists, cockpit will fail to start up if this user exists, please run userdel cockpit-wsinstance-socket to resolve this
Jul 08 13:04:37 localhost.localdomain check_cockpit_users[277050]: group cockpit-wsinstance-socket exists, cockpit will fail to start up if this group exists, please run groupdel cockpit-wsinstance-socket to resolve this
Jul 08 13:04:37 localhost.localdomain check_cockpit_users[277050]: user cockpit-session-socket exists, cockpit will fail to start up if this user exists, please run userdel cockpit-session-socket to resolve this
Jul 08 13:04:37 localhost.localdomain check_cockpit_users[277050]: group cockpit-session-socket exists, cockpit will fail to start up if this group exists, please run groupdel cockpit-session-socket to resolve this
Jul 08 13:04:37 localhost.localdomain check_cockpit_users[277050]: user cockpit-systemd-service exists, cockpit will fail to start up if this group exists, please run userdel cockpit-systemd-service to resolve this
Jul 08 13:04:37 localhost.localdomain systemd[1]: cockpit.socket: Control process exited, code=exited, status=1/FAILURE
Jul 08 13:04:37 localhost.localdomain systemd[1]: cockpit.socket: Failed with result 'exit-code'.
Jul 08 13:04:37 localhost.localdomain systemd[1]: Failed to listen on Cockpit Web Service Socket.
localhost:/etc/sysconfig # userdel cockpit-wsinstance-socket
**userdel: group cockpit-wsinstance-socket is the primary group of another user and is not removed.**
Also may be related to
2025-07-08T13:24:59.349824-04:00 localhost systemd[2927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
2025-07-08T13:24:59.352833-04:00 localhost systemd[2927]: message repeated 15 times: [ Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).]
2025-07-08T13:24:59.352873-04:00 localhost systemd[2927]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
