Cockpit help for not starting

Hi ,

I am trying to use the Cockpit and have some errors.

I have tried to started following this guide and have this error:

Sep 26 08:13:37  systemd[1]: Failed to listen on Socket for Cockpit Web Service http instance.
Sep 26 08:13:37  systemd[1]: cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start faile>
Sep 26 08:13:37 systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.
Sep 26 08:13:37  systemd[1]: cockpit.socket: Trigger limit hit, refusing further activation.
Sep 26 08:13:37  systemd[1]: cockpit.socket: Failed with result 'trigger-limit-hit'

The guide is from the official website:

Also tried to change ports for http and move away from port 9090 but nothing.

A little help would be appreciated…

The firewall is disabled for testing it.

@malcolmlewis Maybe do you have any idea why is this happening?

Regards.

@Jniko Hi, I only use the Cockpit bridge and the flatpak client (org.cockpit_project.CockpitClient) to connect over ssh.

Hello,

I installed cockpit with zypper in cockpit and got the same issue.
When I looked at the LOGs I see that the cockpit-ws User was not created.
I don’t really know why and how but if you want a quickfix it should be enough to create the user: sudo useradd -r -s /sbin/nologin cockpit-ws

After that you should start the cockpit.socket systemctl enable --now cockpit.socket
Finally you should reach the UI with: https://localhost:9090

Let me know if this works for you :slight_smile:

I’ve found an open Bug (Ticket ID 1230546) for this Issue.

Sadly still not working on my side. I have the same error. :frowning_face:

This is not what I’ve expected :frowning:

Please try the following:

systemctl start cockpit.socket
systemctl status cockpit.socket

open https://localhost:9090
systemctl status cockpit.socket
journalctl -u cockpit.socket
journalctl -u cockpit.service

I have this output on journal after doing the recommended above.

For cockpit socket:

Sep 29 17:02:56 localhost systemd[1]: Starting Cockpit Web Service Socket...
Sep 29 17:02:56 localhost systemd[1]: Listening on Cockpit Web Service Socket.
Sep 29 17:03:19 192.168.88.179 systemd[1]: cockpit.socket: Failed with result 'service-start-limit-hit'.
Sep 29 17:08:15 192.168.88.179 systemd[1]: Starting Cockpit Web Service Socket...
Sep 29 17:08:15 192.168.88.179 systemd[1]: Listening on Cockpit Web Service Socket.
Sep 29 17:08:20 192.168.88.179 systemd[1]: cockpit.socket: Failed with result 'service-start-limit-hit'.
Sep 29 17:09:06 192.168.88.179 systemd[1]: Starting Cockpit Web Service Socket...
Sep 29 17:09:06 192.168.88.179 systemd[1]: Listening on Cockpit Web Service Socket.
Sep 29 17:09:10 192.168.88.179 systemd[1]: cockpit.socket: Failed with result 'service-start-limit-hit'.
Sep 29 17:15:35 192.168.88.179 systemd[1]: Starting Cockpit Web Service Socket...
Sep 29 17:15:35 192.168.88.179 systemd[1]: Listening on Cockpit Web Service Socket.
Sep 29 17:15:48 192.168.88.179 systemd[1]: cockpit.socket: Failed with result 'service-start-limit-hit'.
Sep 29 17:38:42 192.168.88.179 systemd[1]: Starting Cockpit Web Service Socket...
Sep 29 17:38:42 192.168.88.179 systemd[1]: Listening on Cockpit Web Service Socket.
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.socket: Failed with result 'service-start-limit-hit'.

For cockpit service:

Sep 29 17:39:21 192.168.88.179 systemd[1]: Starting Cockpit Web Service...
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22519]: cockpit.service: Failed to determine group credentials: No such process
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22519]: cockpit.service: Failed at step GROUP spawning /usr/lib/cockpit-certificate-ensure: No su>
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Control process exited, code=exited, status=216/GROUP
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Failed with result 'exit-code'.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Failed to start Cockpit Web Service.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Starting Cockpit Web Service...
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22522]: cockpit.service: Failed to determine group credentials: No such process
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22522]: cockpit.service: Failed at step GROUP spawning /usr/lib/cockpit-certificate-ensure: No su>
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Control process exited, code=exited, status=216/GROUP
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Failed with result 'exit-code'.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Failed to start Cockpit Web Service.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Starting Cockpit Web Service...
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22525]: cockpit.service: Failed to determine group credentials: No such process
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22525]: cockpit.service: Failed at step GROUP spawning /usr/lib/cockpit-certificate-ensure: No su>
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Control process exited, code=exited, status=216/GROUP
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Failed with result 'exit-code'.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Failed to start Cockpit Web Service.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Starting Cockpit Web Service...
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22528]: cockpit.service: Failed to determine group credentials: No such process
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22528]: cockpit.service: Failed at step GROUP spawning /usr/lib/cockpit-certificate-ensure: No su>
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Control process exited, code=exited, status=216/GROUP
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Failed with result 'exit-code'.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Failed to start Cockpit Web Service.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Starting Cockpit Web Service...
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22531]: cockpit.service: Failed to determine group credentials: No such process
Sep 29 17:39:21 192.168.88.179 (e-ensure)[22531]: cockpit.service: Failed at step GROUP spawning /usr/lib/cockpit-certificate-ensure: No su>
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Control process exited, code=exited, status=216/GROUP
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Failed with result 'exit-code'.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Failed to start Cockpit Web Service.
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Start request repeated too quickly.
Sep 29 17:39:21 192.168.88.179 systemd[1]: cockpit.service: Failed with result 'exit-code'.
Sep 29 17:39:21 192.168.88.179 systemd[1]: Failed to start Cockpit Web Service.


Regards

Thank you for the information.

Please remove the user cockpit-ws we created before and try this:

groupadd -g 466 cockpit-ws
useradd -u 104 -g 466 -c "User for cockpit web service" -d /nonexisting -s /sbin/nologin cockpit-ws
systemctl start cockpit.socket
systemctl status cockpit.socket

open https://localhost:9090 

if this doesn’t help, please post the logs for cockpit.service again

Still the same:

Sep 29 17:59:26 192.168.88.179 systemd[1]: Starting Cockpit Web Service Socket...
Sep 29 17:59:26 192.168.88.179 systemd[1]: Listening on Cockpit Web Service Socket.
Sep 29 17:59:39 192.168.88.179 systemd[1]: cockpit.socket: Failed with result 'service-start-limit-hit'.

Sep 29 17:59:38 192.168.88.179 systemd[1]: Dependency failed for Cockpit Web Service.
Sep 29 17:59:38 192.168.88.179 systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.

Also when I add the user with your command above I have this output:

sudo useradd -u 104 -g 466 -c "User for cockpit web service" -d /nonexisting -s /sbin/nologin cockpit-ws
useradd: UID 104 is not unique

Regards.

Show me the following output:

getent passwd 104
cut -d: -f1,3 /etc/passwd | sort -t: -k2n
getent group cockpit-ws
cat /etc/group
cat /etc/group
root:x:0:
shadow:x:15:vnc
trusted:x:42:
users:x:100:
lock:x:499:
messagebus:x:498:
tftp:x:497:dnsmasq
srvGeoClue:!:496:
nogroup:x:65533:
nobody:x:65534:
man:x:62:
mail:!:495:postfix
lp:!:494:
daemon:x:2:
wheel:x:493:
kvm:x:36:qemu,dell
kmem:x:492:
tty:x:5:
utmp:x:491:
audio:x:490:pulse
cdrom:x:489:
dialout:x:488:
disk:x:487:
input:x:486:
render:x:485:
sgx:x:484:
tape:x:483:
video:x:482:
audit:x:481:
dnsmasq:!:480:
bin:x:1:daemon
pulse-access:x:479:
pulse:!:478:
avahi:!:477:
chrony:!:476:
systemd-journal:x:475:
postfix:x:51:
maildrop:x:59:postfix
polkitd:!:474:
rtkit:!:473:
scard:x:472:
systemd-timesync:x:471:
nscd:!:470:
ntadmin:x:71:
sshd:!:466:
colord:!:465:
lightdm:!:464:
vnc:!:463:
libvirt:x:108:dell,libvirtdbus
qemu:x:107:
tss:!:98:
pesign:x:469:
plugdev:x:468:dell
libvirtdbus:!:105:dell
cockpit-wsinstance:x:467:dell

cut -d: -f1,3 /etc/passwd | sort -t: -k2n
root:0
bin:1
daemon:2
man:13
postfix:51
tss:98
cockpit-wsinstance:104
libvirtdbus:105
pesign:106
qemu:107
vnc:463
lightdm:464
colord:465
sshd:466
statd:467
usbmux:468
rpc:469
nscd:470
systemd-timesync:471
scard:488
rtkit:489
polkitd:490
chrony:491
avahi:492
pulse:493
dnsmasq:494
lp:495
mail:496
srvGeoClue:497
tftp:498
messagebus:499
dell:1000
nobody:65534

etent passwd 104
cockpit-wsinstance:x:104:467:User for cockpit-ws instances:/nonexisting:/sbin/nologin

On getent group cockpit-ws I have no output.

Regards.

Try adding the Group cockpit-ws

sudo groupadd cockpit-ws

The same error:

Sep 29 19:27:11 192.168.88.179 systemd[1]: Dependency failed for Cockpit Web Service.
Sep 29 19:27:11 192.168.88.179 systemd[1]: cockpit.service: Job cockpit.service/start failed with result 'dependency'.

Regards.

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