[systemd-devel] Failed to determine supported controllers: No such process

[Reindl Harald]

Am 21.01.20 um 16:58 schrieb Lennart Poettering:
> On Di, 21.01.20 16:17, Reindl Harald (h.reindl at thelounge.net) wrote:
> 
>>
>>
>> Am 21.01.20 um 16:13 schrieb Lennart Poettering:
>>> On Di, 21.01.20 15:55, Reindl Harald (h.reindl at thelounge.net) wrote:
>>>
>>>> Hi
>>>>
>>>> about to upgrade prepare Fedora 31 upgrades
>>>>
>>>> ------------------------------
>>>>
>>>> Jan 21 15:30:01 testserver systemd[17664]: Failed to determine supported
>>>> controllers: No such process
>>>> Jan 21 15:30:01 testserver systemd[17664]: Failed to allocate manager
>>>> object: No such process
>>>> Jan 21 15:30:01 testserver systemd[1]: user at 48.service: Failed with
>>>> result 'protocol'.
>>>> Jan 21 15:30:01 testserver systemd[1]: Failed to start User Manager for
>>>> UID 48.
>>>
>>> How does user "user at 48.service" and its drop-ins look like?
>>
>> as shipped as part of systemd which is the one starting full sessions
>> just because of a cronjob
> 
> Hmm, so for some reason the per-user instance of systemd cannot figure
> out which cgroup cntrollers are available in its subtree. Something is
> strange there.
> 
> Do you have any non-standard mounts in the host mount namespace? how
> does /etc/fstab look like for you?

i was already considering "hidepid" as the root cause
systemd-243.5-1.fc31.x86_64 other than
systemd-241-12.git323cdf4.fc30.x86_64 can no longer deal with

there are runnign a ton of batched compile jobs at the moment, i will
play around with value 1 and 0 at that place and give feedback later

if that's the case the non-privilged task has to be fixed in a way that
it has no busienss to look into other processes and receive whatever
information it needs from dbus or so

# https://linux-audit.com/linux-system-hardening-adding-hidepid-to-proc/
# allow group 'proc_allow=4502' additionally to root
proc /proc proc    rw,nosuid,nodev,noexec,relatime,hidepid=2,gid=4502