Re: Failed to determine supported controllers: No such process

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Di, 21.01.20 16:17, Reindl Harald (h.reindl@xxxxxxxxxxxxx) wrote:

>
>
> Am 21.01.20 um 16:13 schrieb Lennart Poettering:
> > On Di, 21.01.20 15:55, Reindl Harald (h.reindl@xxxxxxxxxxxxx) 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@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@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?

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel