Have you tried all of this?
Starting Cockpit Web Service Socket...
░░ Subject: A start job for unit cockpit.socket has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cockpit.socket has begun execution.
░░
░░ The job identifier is 35824.
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
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStartPre= process belonging to unit cockpit.socket has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jul 08 13:04:37 localhost.localdomain 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'.
Jul 08 13:04:37 localhost.localdomain 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 35824 and the job result is failed.
Jul 08 13:15:17 localhost.localdomain systemd[1]: Starting Cockpit Web Service Socket...
░░ Subject: A start job for unit cockpit.socket has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit cockpit.socket has begun execution.
░░
░░ The job identifier is 35994.
Jul 08 13:15:17 localhost.localdomain check_cockpit_users[278380]: 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:15:17 localhost.localdomain check_cockpit_users[278380]: 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:15:17 localhost.localdomain check_cockpit_users[278380]: 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:15:17 localhost.localdomain check_cockpit_users[278380]: 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:15:17 localhost.localdomain systemd[1]: cockpit.socket: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStartPre= process belonging to unit cockpit.socket has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jul 08 13:15:17 localhost.localdomain 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'.
Jul 08 13:15:17 localhost.localdomain 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 35994 and the job result is failed.
~
You must drop those users and groups. Take a look here: Error al iniciar cockpit en el navegador web [solucionado]
You can try to drop the groups, and when it fails because there’s users in the group, drop these users, try to drop the group and so.
Eureka!! Deleting cockpit-session-socket user and the cockpit-wsinstance-socket group fixed it.
But surely this is a bug since I did not create this user or group.
@jarome you seem to have some underlying issues with your test install… Disabling SELinux (setting to permissve) is likely not the problem.
I would suggest a fresh install of the system with the latest installer…
@jarome this is an M4 system? I suspect that and perhaps Parallels is not there yet? You might need to check on the Parallels forum as maybe it needs some tweaks for aarch64
M1 Ultra Studio. How do I set SELinux to permissive? That is not listed in Cockpit under SELinux.
@jarome Have a read here https://en.opensuse.org/Portal:SELinux
To set permissive see here, probably worth a read of the whole page https://en.opensuse.org/Portal:SELinux/Troubleshooting#There_are_no_AVC_denials,_could_it_still_be_SELinux?
I’ve also asked the openSUSE ARM Developer on the ARM IRC channel about support for your setup. Should hear back tomorrow…
@jarome Can you create a Tumbleweed install and see if cockpit works out of the box.
OK. Later today.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.