Help to start cockpit

English Applications
1

hi
i have the same problem and i did’nt see any solution

ns:~ # journalctl -u cockpit.service
Jun 30 18:19:25 ns systemd[1]: Dependency failed for Cockpit Web Service.
Jun 30 18:19:25 ns systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Jun 30 18:19:25 ns systemd[1]: Dependency failed for Cockpit Web Service.
Jun 30 18:19:25 ns systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Jun 30 18:19:25 ns systemd[1]: Dependency failed for Cockpit Web Service.
2

some more informations
I have created a self-signed certificate

ns:~ # 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 Tue 2025-07-01 09:32:23 CEST; 8min ago
   Duration: 49.658s
   Triggers: ● cockpit.service
       Docs: man:cockpit-ws(8)
     Listen: [::]:9090 (Stream)
    Process: 29278 ExecStartPost=/usr/share/cockpit/motd/update-motd  localhost (code=exited, status=0/SUCCES>
    Process: 29286 ExecStartPost=/bin/ln -snf active.motd /run/cockpit/motd (code=exited, status=0/SUCCESS)
    Process: 29728 ExecStopPost=/bin/ln -snf inactive.motd /run/cockpit/motd (code=exited, status=0/SUCCESS)
        CPU: 42ms

Jul 01 09:31:33 ns systemd[1]: Starting Cockpit Web Service Socket...
Jul 01 09:31:33 ns systemd[1]: Listening on Cockpit Web Service Socket.
Jul 01 09:32:23 ns systemd[1]: cockpit.socket: Trigger limit hit, refusing further activation.
Jul 01 09:32:23 ns systemd[1]: cockpit.socket: Failed with result 'trigger-limit-hit'.
3

Hey, you might wanna check out this thread

What worked for me was:

Or you could just install the flatpak version of cockpit

4

i see no solution to my problem in this post

5

Did you look at this github issue?

Can you post the output of systemctl --failed?

6

So this Unwelcome changes to openSuSE - #137 by susejunky is not working for you?

7

Have you some “cockpit-xxxxxx”-Users or Groups?

8

Suggestion: open up Discover app and install the Flatpak of Cockpit.

9

@jsc
Hi
i have a group cockpit-winstance

10

@aggie
HI i saw that , but before i will try others solutions, I prefer to keep official packet and i did’nt know how to use discover

11

hi @Bird
Looks like my problem , a bug
please find :

ns:~ # systemctl --failed
  UNIT                                    LOAD   ACTIVE SUB    DESCRIPTION                                   >
● postfix.service                         loaded failed failed Postfix Mail Transport Agent                  >
● cockpit-wsinstance-http.socket          loaded failed failed Socket for Cockpit Web Service http instance
● cockpit-wsinstance-https-factory.socket loaded failed failed Socket for Cockpit Web Service https instance >
● cockpit.socket                          loaded failed failed Cockpit Web Service Socket

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
4 loaded units listed.
lines 1-10/10 (END)
12

@susejunky
Hi i did but nothing
should i reboot ?
EDIT : yes , after reboot it is OK !!
thank’s

13

I’m no expert, but it seems to be related to the same problem I had. Check if /etc/nsswitch.conf and /usr/etc/nsswitch.confare different.
And as @susejunky suggested:

Or just do as I did, and replace /etc/nsswitch.confwith a symlink to /usr/etc/nsswitch.conf

14

https://www.reddit.com/r/openSUSE/comments/1kep0wp/comment/mqnx9vm/

15

yes I did and i said it is OK and marke solution

16

I hope this will be OK !!
I can connect and see the server but i have a lot of error message !!
just a sample !

Screenshot_20250701_165117
Screenshot_20250701_1651171614×427 59.7 KB

17

Yea, good idea … I did the same - started up Discover app, typed “cockpit” in the search field (to find it quickly), clicked on “Cockpit-Client” then Install button, exited Discover. In less than a couple of minutes, I was running Cockpit, error-free (to this day).

I think it was @malcolmlewis (an Administrator out here in the forums) who suggested installing the Flatpak version. :+1:

18

@myswtest yes, that’s what I use here on my primary desktop. With that I need no cockpit type packages installed on the clients I access, which is x86_64, aarch64 and riscv64. All services running on the clients get the appropriate plugins added via the flatpak package installed and run as my user.

1 Like