Bug#1014694: caddy.service: Failed to determine user credentials: No such process

[Geert Stappers]

Package: caddy
Version: 2.4.6-2
Severity: serious
Justification: package usable



Hello,


For me, on Debian Testing, doesn't Caddy start.

How I installed:

|stappers@hop:~
|$ wget http://ftp.nl.debian.org/debian/pool/main/c/caddy/caddy_2.4.6-2_amd64.deb
|--2022-07-10 11:15:44-- http://ftp.nl.debian.org/debian/pool/main/c/caddy/caddy_2.4.6-2_amd64.deb
|Resolving ftp.nl.debian.org (ftp.nl.debian.org)... 2001:67c:2564:a120::21, 130.89.149.21
|Connecting to ftp.nl.debian.org (ftp.nl.debian.org)|2001:67c:2564:a120::21|:80... connected.
|HTTP request sent, awaiting response... 200 OK
|Length: 8073508 (7.7M) [application/x-debian-package]
|Saving to: ‘caddy_2.4.6-2_amd64.deb’
|
|caddy_2.4.6-2_amd64.deb 100%[==========================================>] 7.70M --.-KB/s in 0.05s
|
|2022-07-10 11:15:44 (141 MB/s) - ‘caddy_2.4.6-2_amd64.deb’ saved [8073508/8073508]
|
|stappers@hop:~
|$ sudo dpkg -i caddy_2.4.6-2_amd64.deb
|Selecting previously unselected package caddy.
|(Reading database ... 26988 files and directories currently installed.)
|Preparing to unpack caddy_2.4.6-2_amd64.deb ...
|Unpacking caddy (2.4.6-2) ...
|Setting up caddy (2.4.6-2) ...
|Processing triggers for man-db (2.10.2-1) ...
|stappers@hop:~
|$ systemctl status caddy
|○ caddy.service - Caddy
| Loaded: loaded (/lib/systemd/system/caddy.service; disabled; vendor preset: enabled)
| Active: inactive (dead)
| Docs: https://caddyserver.com/docs/
|stappers@hop:~
|$


What I have, including error message "Failed to determine user credentials":

|stappers@hop:~
|$ dpkg -l caddy
|Desired=Unknown/Install/Remove/Purge/Hold
|| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
||/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
|||/ Name Version Architecture Description
|+++-==============-============-============-=================================================
|ii caddy 2.4.6-2 amd64 Fast, lightweight web server with automatic HTTPS
|stappers@hop:~
|$ systemctl --failed
| UNIT LOAD ACTIVE SUB DESCRIPTION
|● caddy.service loaded failed failed Caddy
|
|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.
|1 loaded units listed.
|stappers@hop:~
|$ systemctl status caddy
|× caddy.service - Caddy
| Loaded: loaded (/lib/systemd/system/caddy.service; disabled; vendor preset: enabled)
| Active: failed (Result: exit-code) since Sun 2022-07-10 11:16:23 UTC; 42min ago
| Docs: https://caddyserver.com/docs/
| Process: 189961 ExecStart=/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile (code=exited, status=217/USER)
| Main PID: 189961 (code=exited, status=217/USER)
| CPU: 2ms
|
|Jul 10 11:16:23 hop systemd[1]: Starting Caddy...
|Jul 10 11:16:23 hop systemd[189961]: caddy.service: Failed to determine user credentials: No such process
|Jul 10 11:16:23 hop systemd[189961]: caddy.service: Failed at step USER spawning /usr/bin/caddy: No such process
|Jul 10 11:16:23 hop systemd[1]: caddy.service: Main process exited, code=exited, status=217/USER
|Jul 10 11:16:23 hop systemd[1]: caddy.service: Failed with result 'exit-code'.
|Jul 10 11:16:23 hop systemd[1]: Failed to start Caddy.
|stappers@hop:~
|$


The unit file, without comment line, note the 'User=caddy' being present

|stappers@hop:~
|$ systemctl cat caddy | grep -v ^\#
|
|[Unit]
|Description=Caddy
|Documentation=https://caddyserver.com/docs/
|After=network.target network-online.target
|Requires=network-online.target
|
|[Service]
|Type=notify
|User=caddy
|Group=caddy
|ExecStart=/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile
|ExecReload=/usr/bin/caddy reload --config /etc/caddy/Caddyfile
|TimeoutStopSec=5s
|LimitNOFILE=1048576
|LimitNPROC=512
|PrivateTmp=true
|ProtectSystem=full
|AmbientCapabilities=CAP_NET_BIND_SERVICE
|
|[Install]
|WantedBy=multi-user.target
|stappers@hop:~
|$

But user 'caddy' is not present.


|stappers@hop:~
|$ id caddy
|id: ‘caddy’: no such user
|stappers@hop:~
|$



I think that is the reason for
caddy.service: Failed to determine user credentials: No such process




Regards
Geert Stappers
Will reply to this bugreport with possible solution
--
Silence is hard to parse