[systemd-devel] Missing kernel service for systemd causes user at 0.service to fail

[Mantas Mikulėnas]

On Thu, Feb 15, 2018 at 3:05 AM, tedheadster <tedheadster at gmail.com> wrote:
> Team,
>   I have compiled my linux kernel using 'allnoconfig' and added back
> in all the kernel options that have been documented as necessary for
> systemd. I'm still getting an error. It fails trying to start
> user at 0.service, and it is related to PAM somehow.
>
> Here is the debug log:
>
> Feb 14 23:48:57 intel486 systemd[1]: user at 0.service: About to execute:
> /lib/systemd/systemd --user
> Feb 14 23:48:57 intel486 systemd[1]: user at 0.service: Forked
> /lib/systemd/systemd as 111
> Feb 14 23:48:57 intel486 systemd[1]: user at 0.service: Changed dead -> start
> Feb 14 23:48:57 intel486 systemd[1]: Starting User Manager for UID 0...
> Feb 14 23:48:57 intel486 systemd[1]: user at 0.service: User lookup
> succeeded: uid=0 gid=0
> Feb 14 23:48:57 intel486 systemd[111]: user at 0.service: Kernel keyring
> not supported, ignoring.
> Feb 14 23:48:57 intel486 systemd[111]: PAM failed: Function not
implemented
> Feb 14 23:48:57 intel486 systemd[111]: user at 0.service: Failed to set
> up PAM session: Function not implemented
> […]
> Trying to run this post-boot under strace did not get me any good leads.
>
> What do you suggest to track this kernel configuration option down?

Examine all modules listed in /etc/pam.d/systemd-user, and enable all
kernel options *those* modules might need.

`strace pamtester systemd-user $USER acct_mgmt open_session close_session`
might be a good method.

-- 
Mantas Mikulėnas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180215/d421b60e/attachment.html>