Dependency failed for cockpit.service - Cockpit Web Service.

[Pshock13]

Explain what happens

I've had cockpit running on this system for a while now but today I was unable to connect remotely. When trying to connect I just get
"This page isn’t working
didn’t send any data.
ERR_EMPTY_RESPONSE"

cockpit.socket seems to stay active until I attempt to connect via :9090, at which point I end up with this

cockpit.socket - Cockpit Web Service Socket
     Loaded: loaded (/lib/systemd/system/cockpit.socket; enabled; preset: enabled)
     Active: failed (Result: trigger-limit-hit) since Fri 2025-02-14 09:47:22 EST; 13s ago
   Duration: 32.160s
   Triggers: ● cockpit.service
       Docs: man:cockpit-ws(8)
     Listen: [::]:9090 (Stream)
    Process: 3140397 ExecStartPost=/usr/share/cockpit/issue/update-issue  localhost (code=exited, status=0/SUCCESS)
    Process: 3140404 ExecStartPost=/bin/ln -snf active.issue /run/cockpit/issue (code=exited, status=0/SUCCESS)
    Process: 3140702 ExecStopPost=/bin/ln -snf inactive.issue /run/cockpit/issue (code=exited, status=0/SUCCESS)
        CPU: 23ms

Feb 14 09:46:49  systemd[1]: Starting cockpit.socket - Cockpit Web Service Socket...
Feb 14 09:46:49 systemd[1]: Listening on cockpit.socket - Cockpit Web Service Socket.
Feb 14 09:47:22 systemd[1]: cockpit.socket: Trigger limit hit, refusing further activation.
Feb 14 09:47:22 systemd[1]: cockpit.socket: Failed with result 'trigger-limit-hit'.

and then we have the cockpit.service

$  sudo systemctl status cockpit.service
○ cockpit.service - Cockpit Web Service
     Loaded: loaded (/lib/systemd/system/cockpit.service; static)
     Active: inactive (dead) since Fri 2025-02-14 08:08:40 EST; 2h 0min ago
   Duration: 4w 5h 47min 17.017s
TriggeredBy: × cockpit.socket
       Docs: man:cockpit-ws(8)
   Main PID: 796184 (code=killed, signal=TERM)
        CPU: 13min 55.969s

Feb 14 09:47:22 systemd[1]: Dependency failed for cockpit.service - Cockpit Web Service.
Feb 14 09:47:22 systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Feb 14 09:47:22 systemd[1]: Dependency failed for cockpit.service - Cockpit Web Service.
Feb 14 09:47:22 systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Feb 14 09:47:22 systemd[1]: Dependency failed for cockpit.service - Cockpit Web Service.
Feb 14 09:47:22 systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Feb 14 09:47:22 systemd[1]: Dependency failed for cockpit.service - Cockpit Web Service.
Feb 14 09:47:22 systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Feb 14 09:47:22 systemd[1]: Dependency failed for cockpit.service - Cockpit Web Service.
Feb 14 09:47:22 systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.

I've tried uninstalling and reinstalling fresh but I still get the same result

Version of Cockpit

Version: 331 Protocol: 1

Where is the problem in Cockpit?

None

Server operating system

Debian

Server operating system version

Debian GNU/Linux 12 (bookworm)

What browsers are you using?

Other

System log

Dependency failed for cockpit.service - Cockpit Web Service.
cockpit.service: Job cockpit.service/start failed with result 'dependency'.

[martinpitt]

Are you using the official backport (331-1~bpo12+1) or some custom build?

I'm afraid I need the full journal, cockpit.service also just failed because of a dependency but you didn't give that log. Reset with

systemctl stop cockpit.socket
systemctl reset-failed
systemctl start cockpit.socket

Then start journal -f, try to open cockpit, and copy&paste the output here. Thanks!

[Pshock13]

https://pastebin.com/UbNdKJHn

And yes I'm pretty sure I'm using the official backport as I installed this based on the instruction from the cockpit website. How would I verify this?