Absense of user and service

Debian 12
There's no entry in /etc/passwd for stubby, there's also no service file (systemd).
The expectation was that those would be created when installed by a package manager.
Exceptional or rule?

This results in monitoring pollution with shell scripting failures, but worst, it hurts ones eyes (kidding)

Eg:
aliensRus@planetEarth: ~# ss -tulnep | grep LISTEN | sudo lsof -i -n -P
lsof: no pwd entry for UID 64707
stubby 9194 64707 3u IPv4 38172 0t0 UDP 127.0.0.1:8053
lsof: no pwd entry for UID 64707
stubby 9194 64707 4u IPv4 38173 0t0 TCP 127.0.0.1:8053 (LISTEN)
lsof: no pwd entry for UID 64707
stubby 9194 64707 5u IPv6 38174 0t0 UDP [::1]:8053
lsof: no pwd entry for UID 64707
stubby 9194 64707 6u IPv6 38175 0t0 TCP [::1]:8053 (LISTEN)

64707 should be/could be "stubby"

The following files do not have an defined groups ownership: /run/stubby
The following files are unowned: /run/stubby

[andy-bower]

Hi Ghost, the systemd service file does exist in bookworm, which is why you are seeing those numerical user ids - they are from systemd's DynamicUser concept, which allocates one on the fly rather than adding it into /etc/passwd. I avoid systemd myself so I'm not sure if this is installed by default or not but you would need the libnss-systemd package installed and enabled in /etc/nsswitch.conf to get the reverse user name resolution working. If you prefer a static user, you can install your own version of the service file and add a sysusers.d configuration to effect this.

[Masrkai]

I was concerned when i saw my stubby service with the user "64707" and i thought this was a configuration mistake on my part, turns out it's the project will to not rely fully on systemd according to my understanding up to this point