Cockpit service fails to start on Leap 16

I can’t get the Cockpit service to start. I’m getting the following errors:

homeserver:~ # systemctl enable cockpit.socket
homeserver:~ # systemctl start cockpit.socket
Job failed. See "journalctl -xe" for details.
homeserver:~ # 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 Fri 2025-12-26 16:21:37 CET; 8s ago
 Invocation: a47bbf1e3664472d94f6857a1d82b539
   Triggers: ● cockpit.service
       Docs: man:cockpit-ws(8)
     Listen: [::]:9090 (Stream)
    Process: 5174 ExecStartPre=/usr/libexec/check_cockpit_users (code=exited, status=1/FAILURE)
        CPU: 17ms

Dec 26 16:21:37 homeserver systemd[1]: Starting Cockpit Web Service Socket...
Dec 26 16:21:37 homeserver check_cockpit_users[5174]: /etc/nsswitch.conf is out of date, please update it from /usr/etc/nsswitch.conf to use cockpit
Dec 26 16:21:37 homeserver systemd[1]: cockpit.socket: Control process exited, code=exited, status=1/FAILURE
Dec 26 16:21:37 homeserver systemd[1]: cockpit.socket: Failed with result 'exit-code'.
Dec 26 16:21:37 homeserver systemd[1]: Failed to listen on Cockpit Web Service Socket.
homeserver:~ # journalctl -xe
░░ A start job for unit cockpit-issue.service has begun execution.
░░ 
░░ The job identifier is 4160.
Dec 26 16:20:20 homeserver 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.
Dec 26 16:20:20 homeserver 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 4160.
Dec 26 16:21:31 homeserver systemd[1]: Reload requested from client PID 5136 ('systemctl') (unit session-1.scope)...
Dec 26 16:21:31 homeserver systemd[1]: Reloading...
Dec 26 16:21:31 homeserver systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed'>
Dec 26 16:21:32 homeserver systemd[1]: Reloading finished in 514 ms.
Dec 26 16:21:37 homeserver 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 4366.
Dec 26 16:21:37 homeserver check_cockpit_users[5174]: /etc/nsswitch.conf is out of date, please update it from /usr/etc/nsswitch.conf to use cockpit
Dec 26 16:21:37 homeserver 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.
Dec 26 16:21:37 homeserver 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'.
Dec 26 16:21:37 homeserver 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 4366 and the job result is failed.
Dec 26 16:21:37 homeserver 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 4559.
Dec 26 16:21:37 homeserver 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.
Dec 26 16:21:37 homeserver 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 4559.

That is a quite old issue which was already discussed in the forum and bugreports. For Leap 15.6 → 16.0 migrations, the nsswitch.conf needs the correct content.

One of the many threads:

1 Like

Thanks.

This solution works:
https://forums.opensuse.org/t/leap-15-6-cannot-run-cockpit/188436/13