Ubuntu
systemd package

  1. Bug #2073776
  2. Comment #2

Comment 2 for bug 2073776

Revision history for this message
Andrew Martin (asmartin) wrote : Re: cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but systemd units still use cockpit-ws as the username

Yes, cockpit fails to start:
cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.
cockpit.service: Job cockpit.service/start failed with result 'dependency'.
cockpit-wsinstance-https-factory.socket: Control process exited, code=exited, status=217/USER
cockpit-wsinstance-https-factory.socket: Failed to resolve user cockpit-ws: No such process
cockpit-wsinstance-http.socket: Failed with result 'exit-code'.
Failed to listen on Socket for Cockpit Web Service http instance.
Dependency failed for Cockpit Web Service.
Dependency failed for Socket for Cockpit Web Service https instance factory.

This is on Ubuntu 22.04.