Cockpit: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'

:~> systemctl status cockpit.socket

● cockpit.socket - Cockpit Web Service Socket
     Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; preset: disabled)
     Active: active (listening) since Thu 2025-05-29 16:38:49 MDT; 33min ago
   Triggers: ● cockpit.service
       Docs: man:cockpit-ws(8)
     Listen: [::]:9090 (Stream)
    Process: 5608 ExecStartPost=/usr/share/cockpit/motd/update-motd  localhost (code=exited, status=0/SUCCESS)
    Process: 5615 ExecStartPost=/bin/ln -snf active.motd /run/cockpit/motd (code=exited, status=0/SUCCESS)
      Tasks: 0 (limit: 4915)
        CPU: 32ms
     CGroup: /system.slice/cockpit.socket

~> sudo journalctl -xe

May 29 16:38:49 kbbn-kvmserver 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 13425.
May 29 16:38:49 kbbn-kvmserver systemd[1]: Listening on Cockpit Web Service Socket.
░░ Subject: A start job for unit cockpit.socket has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cockpit.socket has finished successfully.
░░ 
░░ The job identifier is 13425.
May 29 16:38:49 kbbn-kvmserver sudo[5599]: pam_unix(sudo:session): session closed for user root
May 29 16:38:49 kbbn-kvmserver sudo[5599]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session
May 29 16:38:49 kbbn-kvmserver sudo[5599]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
May 29 16:38:49 kbbn-kvmserver systemd[1]: Starting Cockpit motd updater service...
░░ Subject: A start job for unit cockpit-motd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cockpit-motd.service has begun execution.
░░ 
░░ The job identifier is 13565.
May 29 16:38:49 kbbn-kvmserver systemd[1]: cockpit-motd.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit cockpit-motd.service has successfully entered the 'dead' state.
May 29 16:38:49 kbbn-kvmserver systemd[1]: Finished Cockpit motd updater service.
░░ Subject: A start job for unit cockpit-motd.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cockpit-motd.service has finished successfully.
░░ 
░░ The job identifier is 13565.

However when I start the browser it fails
:~> systemctl status cockpit.socket

× cockpit.socket - Cockpit Web Service Socket
     Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; preset: disabled)
     Active: failed (Result: trigger-limit-hit) since Thu 2025-05-29 17:15:01 MDT; 1min 51s ago
   Duration: 36min 12.382s
   Triggers: ● cockpit.service
       Docs: man:cockpit-ws(8)
     Listen: [::]:9090 (Stream)
    Process: 5608 ExecStartPost=/usr/share/cockpit/motd/update-motd  localhost (code=exited, status=0/SUCCESS)
    Process: 5615 ExecStartPost=/bin/ln -snf active.motd /run/cockpit/motd (code=exited, status=0/SUCCESS)
    Process: 8744 ExecStopPost=/bin/ln -snf inactive.motd /run/cockpit/motd (code=exited, status=0/SUCCESS)
        CPU: 35ms

~> sudo journalctl -xe

May 29 17:15:01 kbbn-kvmserver systemd[1]: cockpit-wsinstance-http.socket: Start request repeated too quickly.
May 29 17:15:01 kbbn-kvmserver systemd[1]: cockpit-wsinstance-http.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-http.socket has entered the 'failed' state with result 'exit-code'.
May 29 17:15:01 kbbn-kvmserver systemd[1]: Failed to listen on Socket for Cockpit Web Service http instance.
░░ Subject: A start job for unit cockpit-wsinstance-http.socket has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cockpit-wsinstance-http.socket has finished with a failure.
░░ 
░░ The job identifier is 16422 and the job result is failed.
May 29 17:15:01 kbbn-kvmserver systemd[1]: Dependency failed for Cockpit Web Service.
░░ Subject: A start job for unit cockpit.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cockpit.service has finished with a failure.
░░ 
░░ The job identifier is 16421 and the job result is dependency.
May 29 17:15:01 kbbn-kvmserver systemd[1]: Dependency failed for Socket for Cockpit Web Service https instance factory.
░░ Subject: A start job for unit cockpit-wsinstance-https-factory.socket has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit cockpit-wsinstance-https-factory.socket has finished with a failure.
░░ 
░░ The job identifier is 16563 and the job result is dependency.
May 29 17:15:01 kbbn-kvmserver systemd[1]: cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.
May 29 17:15:01 kbbn-kvmserver systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.

It repeats this several times. What is this cockpit-wsinstance-http.socket dependency that is needs to get this working?

Something to check: Examine /etc/nsswitch.conf and make sure that the following entries are present (edit as required)…

passwd:         compat systemd
group:          compat [SUCCESS=merge] systemd
shadow:         compat systemd

I ran into something similar. I think that is all that I had to do.

1 Like

I don’t “see trigger-limit-hit” in your logs.

But I had this problem and I posted the fix.
Same as Deano just said.

There’s been some changes and browsing though this might help you if they make other changes. Here’s my post and a whole discussion about it.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.