Re: Failed to determine supported controllers: No such process

[Reindl Harald <h.reindl@xxxxxxxxxxxxx>]

Am 21.01.20 um 16:17 schrieb Reindl Harald:
> 
> 
> 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

and it happens with every session
5000 was the ssh login of my builduser

luckily nothing cares about the failing usermanager service - the godd
question is if that applies to graphical sessions too or upgrade to F31
would kill X11/KDE at the moment

-----------------------------------------

[root@testserver:~]$ systemctl list-units | grep 5000
  run-user-5000.mount
                           loaded active mounted   /run/user/5000

  user-runtime-dir@5000.service
                           loaded active exited    User Runtime
Directory /run/user/5000
● user@5000.service
                           loaded failed failed    User Manager for UID
5000
  user-5000.slice
                           loaded active active    User Slice of UID 5000

-----------------------------------------

[root@testserver:~]$ systemctl status user@5000.service
● user@5000.service - User Manager for UID 5000
   Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor
preset: disabled)
   Active: failed (Result: protocol) since Tue 2020-01-21 16:19:28 CET;
4min 33s ago
     Docs: man:user@.service(5)
  Process: 1268 ExecStart=/usr/lib/systemd/systemd --user (code=exited,
status=1/FAILURE)
 Main PID: 1268 (code=exited, status=1/FAILURE)
      CPU: 22ms

Jan 21 16:19:28 testserver.rhsoft.net systemd[1]: Starting User Manager
for UID 5000...
Jan 21 16:19:28 testserver.rhsoft.net systemd[1268]:
pam_unix(systemd-user:session): session opened for user builduser by (uid=0)
Jan 21 16:19:28 testserver.rhsoft.net systemd[1268]: Failed to determine
supported controllers: No such process
Jan 21 16:19:28 testserver.rhsoft.net systemd[1268]: Failed to allocate
manager object: No such process
Jan 21 16:19:28 testserver.rhsoft.net systemd[1273]:
pam_unix(systemd-user:session): session closed for user builduser
Jan 21 16:19:28 testserver.rhsoft.net systemd[1]: user@5000.service:
Failed with result 'protocol'.
Jan 21 16:19:28 testserver.rhsoft.net systemd[1]: Failed to start User
Manager for UID 5000.

> [root@testserver:~]$ systemctl status user@48.service
> ● user@48.service - User Manager for UID 48
>    Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor
> preset: disabled)
>    Active: failed (Result: protocol) since Tue 2020-01-21 16:00:02 CET;
> 16min ago
>      Docs: man:user@.service(5)
>   Process: 34694 ExecStart=/usr/lib/systemd/systemd --user (code=exited,
> status=1/FAILURE)
>  Main PID: 34694 (code=exited, status=1/FAILURE)
>       CPU: 35ms
> 
> Jan 21 16:00:01 testserver.rhsoft.net systemd[1]: Starting User Manager
> for UID 48...
> Jan 21 16:00:01 testserver.rhsoft.net systemd[34694]:
> pam_unix(systemd-user:session): session opened for user apache by (uid=0)
> Jan 21 16:00:02 testserver.rhsoft.net systemd[34694]: Failed to
> determine supported controllers: No such process
> Jan 21 16:00:02 testserver.rhsoft.net systemd[34694]: Failed to allocate
> manager object: No such process
> Jan 21 16:00:02 testserver.rhsoft.net systemd[34709]:
> pam_unix(systemd-user:session): session closed for user apache
> Jan 21 16:00:02 testserver.rhsoft.net systemd[1]: user@48.service:
> Failed with result 'protocol'.
> Jan 21 16:00:02 testserver.rhsoft.net systemd[1]: Failed to start User
> Manager for UID 48.
> 
> [root@testserver:~]$ cat /usr/lib/systemd/system/user@.service
> #  SPDX-License-Identifier: LGPL-2.1+
> #
> #  This file is part of systemd.
> #
> #  systemd is free software; you can redistribute it and/or modify it
> #  under the terms of the GNU Lesser General Public License as published by
> #  the Free Software Foundation; either version 2.1 of the License, or
> #  (at your option) any later version.
> 
> [Unit]
> Description=User Manager for UID %i
> Documentation=man:user@.service(5)
> After=systemd-user-sessions.service user-runtime-dir@%i.service dbus.service
> Requires=user-runtime-dir@%i.service
> IgnoreOnIsolate=yes
> 
> [Service]
> User=%i
> PAMName=systemd-user
> Type=notify
> ExecStart=-/usr/lib/systemd/systemd --user
> Slice=user-%i.slice
> KillMode=mixed
> Delegate=pids memory
> TasksMax=infinity
> TimeoutStopSec=120s
> KeyringMode=inherit
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel