I'd like to summarize all the thought about this issue. The systemd
behavior regarding PAM stack has been changed:
1. systemd-232: if PAM stack fails service unit is still started, so PAM
errors are ignored.
2. systemd-233: if PAM stack fails service unit fails as well.
The second is IMO the
I suppose you meant pam_keyinit, not pam_keyring, right? Although I saw
that the new version of default "systemd-user" pam configuration file
added pam_keyinit, I tested migration of systemd from 232 to 233 with
exactly the same pam.d configuration (as I mentioned below). The _only_
thing that
On Sat, 29.04.17 16:59, Vlad (vo...@vovan.nl) wrote:
> Thanks for the answer. I'd then rephrase my original question: I'd like
> to know what has been changed in the systemd (pam_systemd?) version 233,
> that now it fails to start user@xxx.service? If I downgrade to the
> version 232, then
Thanks for the answer. I'd then rephrase my original question: I'd like
to know what has been changed in the systemd (pam_systemd?) version 233,
that now it fails to start user@xxx.service? If I downgrade to the
version 232, then systemd gives the same error, but still starts
user@xxx.service
On Sat, 29.04.17 13:25, Vlad (vo...@vovan.nl) wrote:
> Lennart,
>
> I've just tried your suggestion as well, but it doesn't change behavior.
> I'm just wondering how it would be possible to investigate the error.
> The message "user@xxx.service: Failed at step PAM spawning
>
Lennart,
I've just tried your suggestion as well, but it doesn't change behavior.
I'm just wondering how it would be possible to investigate the error.
The message "user@xxx.service: Failed at step PAM spawning
/usr/lib/systemd/systemd: Operation not permitted" isn't very
descriptive. I enabled
Lennart,
As I can see pam_systemd is "optional" everywhere in pam.d
configuration. Is that what you meant?
grep pam_systemd *
system-auth:session optionalpam_systemd.so debug
systemd-user:session optional pam_systemd.so
Regards,
Vlad.
On 29/04/17 12:21, Lennart Poettering wrote:
>
On Sat, 29.04.17 11:13, Vlad (vo...@vovan.nl) wrote:
> Hello,
>
> I've recently updated systemd and now user session is failing to start:
> Apr 29 11:04:02 xxx systemd[550]: user@xxx.service: Failed at step PAM
> spawning /usr/lib/systemd/systemd: Operation not permitted
> Apr 29 11:04:02 xxx
