1 |
Hello, |
2 |
|
3 |
Very simple question but did you have "pam" in your global USE flag or |
4 |
Systemd USE flag ? |
5 |
|
6 |
If this is on the first, did you compile systemd and may be dependencies |
7 |
after add it ? |
8 |
|
9 |
Did you try that: |
10 |
|
11 |
|systemctl reset-failed| |
12 |
|
13 |
|For a guy on github, that solve (without explanation) the problem: |
14 |
| |
15 |
|
16 |
|https://github.com/coreos/bugs/issues/1498| |
17 |
|| |
18 |
|
19 |
|
20 |
|
21 |
Hogren |
22 |
|
23 |
|
24 |
|
25 |
|
26 |
|
27 |
On 22/05/2017 14:13, Raffaele Belardi wrote: |
28 |
> On Mon, 2017-05-22 at 13:02 +0300, Alexander Kapshuk wrote: |
29 |
>> On Mon, May 22, 2017 at 1:00 PM, Raffaele Belardi |
30 |
>> <raffaele.belardi@××.com> wrote: |
31 |
>>> On Mon, 2017-05-22 at 12:47 +0300, Alexander Kapshuk wrote: |
32 |
>>>> A Google search found this systemd issue: |
33 |
>>>> https://github.com/systemd/systemd/issues/4342 |
34 |
>>>> Quote: |
35 |
>>>> @poettering I see I left no account modules in the bare-bones PAM |
36 |
>>>> config. Maybe it is pam_acct_mgmt failing then? |
37 |
>>>> |
38 |
>>>> @yuwata what happens if you add account required pam_unix.so ? |
39 |
>>>> |
40 |
>>>> @fsateler Thanks. By adding the line, user sessions successfully |
41 |
>>>> start |
42 |
>>>> without the error messages. Do you think the line should be added |
43 |
>>>> to |
44 |
>>>> the minimal PAM file? |
45 |
>>>> |
46 |
>>>> See if that helps. |
47 |
>>>> |
48 |
>>> Yes, I saw that but the solution is not at all clear to me: which |
49 |
>>> PAM |
50 |
>>> config file are they referring to? |
51 |
>>> |
52 |
>>> raffaele |
53 |
>>> |
54 |
>>> |
55 |
>> Could it be this one, /etc/pam.d/systemd-user? |
56 |
>> |
57 |
> Done then issued 'systemctl daemon-reload' and 'systemctl start gdm', |
58 |
> no change: |
59 |
> |
60 |
> $ cat /etc/pam.d/systemd-user |
61 |
> # This file is part of systemd. |
62 |
> # |
63 |
> # Used by systemd --user instances. |
64 |
> |
65 |
> account include system-auth |
66 |
> # [RB] |
67 |
> account required pam_unix.so |
68 |
> session include system-auth |
69 |
> session optional pam_keyinit.so force revoke |
70 |
> session optional pam_systemd.so |
71 |
> |
72 |
> #journalctl -b |
73 |
> ... |
74 |
> systemd[1]: Created slice User Slice of gdm. |
75 |
> systemd[1]: Starting User Manager for UID 32... |
76 |
> systemd[1]: Started Session c519 of user gdm. |
77 |
> systemd-logind[173]: New session c519 of user gdm. |
78 |
> systemd[15240]: user@××.service: Failed at step PAM spawning |
79 |
> /usr/lib/systemd/systemd: Operation not permitted |
80 |
> systemd[1]: Failed to start User Manager for UID 32. |
81 |
> systemd[1]: user@××.service: Unit entered failed state. |
82 |
> systemd[1]: user@××.service: Failed with result 'protocol'. |
83 |
> gdm-launch-environment][15237]: pam_systemd(gdm-launch- |
84 |
> environment:session): Failed to create session: Start job for unit user |
85 |
> @32.service failed with 'failed' |
86 |
> systemd-logind[173]: Removed session c519. |
87 |
> |