Intermittent failure of user@<uid>.service

[jpokorny@xxxxxxxxxxxxxxxxx (Jan Pokorný)]

On 10/08/18 20:58 -0700, Johannes Ernst wrote:
> This is Arch. I boot the system, and ssh in as user â??shepherdâ??.
> Something goes wrong, but from the log (below) I cannot tell what it
> is. I do get a shell and everything seems to work fine. If I
> terminate ssh and re-log in, everything is fine.
> 
> This happens often enough Iâ??m wondering â?¦ ideas?
> 
> [...]
> 
> Aug 11 03:52:38 ubosbox systemd[1]: Started /run/user/979 mount wrapper.
> Aug 11 03:52:38 ubosbox systemd[1]: Starting User Manager for UID 979...
> Aug 11 03:52:38 ubosbox systemd-logind[345]: New session c1 of user shepherd.
> Aug 11 03:52:38 ubosbox systemd[1]: Started Session c1 of user shepherd.
> Aug 11 03:52:38 ubosbox systemd[1266]: Failed to fully start up daemon: Permission denied
> Aug 11 03:52:38 ubosbox systemd[1]: user at 979.service: Failed with result 'protocol'.
> Aug 11 03:52:38 ubosbox systemd[1]: Failed to start User Manager for UID 979.

I've seen something like that after updating systemd to 239 (you can
possibly retry with 238 if it persists), and the fix is allegedly
coming;  see also a possible workaround I am currently sticking with:

https://github.com/systemd/systemd/issues/9461#issuecomment-409929860

though it can be more tricky in remote access case (not my scenario).

-- 
Nazdar,
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180814/fe9ac04e/attachment.sig>