<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-2022-jp"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="en-SE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Hi Luca,<o:p></o:p> <o:p> </o:p> Sorry, for late reply, below is a log with debug. This time I run with a user with higher UID, but the result is the same.<o:p></o:p> <o:p> </o:p> root@host:~# systemd-analyze set-log-level debug<o:p></o:p> root@host:~# systemctl set-environment XDG_RUNTIME_DIR="/run/user/1001"<o:p></o:p> root@host:~# systemctl start user@1001.service<o:p></o:p> Job for user@1001.service failed because the control process exited with error code.<o:p></o:p> See "systemctl status user@1001.service" and "journalctl -xeu user@1001.service" for details.<o:p></o:p> root@host:~# journalctl -xeu user@1001.service<o:p></o:p> Dec 08 09:35:53 host systemd[1]: /usr/lib/systemd/system/user@.service:19: Support for option PAMName= has been disabled at compile time and it is ignored<o:p></o:p> Dec 08 09:35:53 host systemd[1]: user@1001.service: Trying to enqueue job user@1001.service/start/replace<o:p></o:p> Dec 08 09:35:53 host systemd[1]: user@1001.service: Installed new job user@1001.service/start as 6724<o:p></o:p> Dec 08 09:35:53 host systemd[1]: user@1001.service: Enqueued job user@1001.service/start as 6724<o:p></o:p> Dec 08 09:35:53 host systemd[1]: user@1001.service: starting held back, waiting for: user-runtime-dir@1001.service<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Will spawn child (service_enter_start): /usr/lib/systemd/systemd<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Failed to set 'memory.zswap.max' attribute on '/user.slice/user-1001.slice/user@1001.service' to 'max': No such file or directory<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Passing 0 fds to service<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: About to execute: /usr/lib/systemd/systemd --user<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Forked /usr/lib/systemd/systemd as 6899<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Changed dead -> start<o:p></o:p> Dec 08 09:35:54 host systemd[1]: Starting User Manager for UID 1001...<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Bind-mounting / on /run/systemd/mount-rootfs (MS_BIND|MS_REC "")...<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: User lookup succeeded: uid=1001 gid=118<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Applying namespace mount on /run/systemd/mount-rootfs/run/credentials<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Bind-mounting /run/systemd/inaccessible/dir on /run/systemd/mount-rootfs/run/credentials (MS_BIND|MS_REC "")...<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Successfully mounted /run/systemd/inaccessible/dir to /run/systemd/mount-rootfs/run/credentials<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Applying namespace mount on /run/systemd/mount-rootfs/run/systemd/incoming<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Followed source symlinks /run/systemd/propagate/user@1001.service $B"*(B /run/systemd/propagate/user@1001.service.<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Bind-mounting /run/systemd/propagate/user@1001.service on /run/systemd/mount-rootfs/run/systemd/incoming (MS_BIND "")...<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Successfully mounted /run/systemd/propagate/user@1001.service to /run/systemd/mount-rootfs/run/systemd/incoming<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Applying namespace mount on /run/systemd/mount-rootfs/sys<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Failed to umount /run/systemd/mount-rootfs/sys, ignoring: Device or resource busy<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Failed to umount /run/systemd/mount-rootfs/sys, ignoring: Device or resource busy<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Failed to umount /run/systemd/mount-rootfs/sys, ignoring: Device or resource busy<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Failed to umount /run/systemd/mount-rootfs/sys, ignoring: Device or resource busy<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Failed to umount /run/systemd/mount-rootfs/sys, ignoring: Device or resource busy<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Failed to umount /run/systemd/mount-rootfs/sys, ignoring: Device or resource busy<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Failed to umount /run/systemd/mount-rootfs/sys, ignoring: Device or resource busy<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Failed to umount /run/systemd/mount-rootfs/sys, ignoring: Device or resource busy<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: Mounting sysfs (sysfs) on /run/systemd/mount-rootfs/sys (MS_NOSUID|MS_NODEV|MS_NOEXEC "")...<o:p></o:p> Dec 08 09:35:54 host (systemd)[6899]: user@1001.service: Executing: /usr/lib/systemd/systemd --user<o:p></o:p> Dec 08 09:35:54 host systemd[6899]: Failed to copy os-release for propagation, ignoring: Permission denied<o:p></o:p> Dec 08 09:35:54 host systemd[6899]: Failed to allocate manager object: Permission denied<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Got notification message from PID 6899 (ERRNO=13)<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Got notification message from PID 6899 (EXIT_STATUS=1)<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Child 6899 belongs to user@1001.service.<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Main process exited, code=exited, status=1/FAILURE<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Failed with result 'exit-code'.<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Service will not restart (restart setting)<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Changed start -> failed<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Job 6724 user@1001.service/start finished, result=failed<o:p></o:p> Dec 08 09:35:54 host systemd[1]: Failed to start User Manager for UID 1001.<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Unit entered failed state.<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Consumed 63ms CPU time.<o:p></o:p> Dec 08 09:35:54 host systemd[1]: user@1001.service: Releasing resources...<o:p></o:p> <o:p> </o:p> Best regards,<o:p></o:p> <div> <div> Christopher Wong<o:p></o:p> <o:p> </o:p> </div> </div> <o:p> </o:p> <o:p> </o:p> <div id="mail-editor-reference-message-container"> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Luca Boccassi <luca.boccassi@gmail.com> Date: Wednesday, 6 December 2023 at 17:46 To: Christopher Wong <Christopher.Wong@axis.com> Cc: systemd-devel@lists.freedesktop.org <systemd-devel@lists.freedesktop.org> Subject: Re: [systemd-devel] Manual start of user@<uid>.service failed with permission denied<o:p></o:p> </div> <div> On Wed, 6 Dec 2023 at 16:00, Christopher Wong <Christopher.Wong@axis.com> wrote: > Hi, > > I$B!G(Bm trying to do the following: > > root@host:~# systemctl set-environment XDG_RUNTIME_DIR="/run/user/503" Why are you setting this? Anyway, enable debug level log and attach the output, otherwise it's hard to say<o:p></o:p> </div> </div> </div> </div> </body> </html>