Bug ID 1029152
Summary systemd-logind and wickedd-services not starting
Classification openSUSE
Product openSUSE Distribution
Version Leap 42.2
Hardware x86-64
OS Other
Status NEW
Severity Major
Priority P5 - None
Component Basesystem
Assignee bnc-team-screening@forge.provo.novell.com
Reporter thomas.voigt@netkom.de
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Setting up a brand new HP ProLiant DL160Gen9 here with OpenSuSE Leap 42.2.
First configurations (static IP configuration) run fine so restarted the
system. All fine until there.

Now changed authentication to LDAP-based authentication via Yast. After the
next reboot the following messages appear:

"Failed to start login service"
"Failed to start wicked DHCPv6 supplicant service" (I'm not using IPv6)
"Failed to start wicked AUTOIPv4 supplicant service"
"Failed to start wicked DHCPv4 supplicant service"

Starting the system now lasts very long (maybe 15min).

System log shows multiple times:

M��r 13 14:48:32 srv034 systemd[1]: Starting Login Service...
M��r 13 14:48:57 srv034 systemd-logind[13378]: Failed to enable subscription:
Connection timed out
M��r 13 14:48:57 srv034 systemd-logind[13378]: Failed to fully start up daemon:
Connection timed out
M��r 13 14:48:57 srv034 dbus[924]: [system] Failed to activate service
'org.freedesktop.systemd1': timed out
M��r 13 14:48:57 srv034 systemd[1]: systemd-logind.service: Main process exited,
code=exited, status=1/FAILURE
M��r 13 14:48:57 srv034 systemd[1]: Failed to start Login Service.
M��r 13 14:48:57 srv034 systemd[1]: systemd-logind.service: Unit entered failed
state.
M��r 13 14:48:57 srv034 systemd[1]: systemd-logind.service: Failed with result
'exit-code'.
M��r 13 14:48:57 srv034 systemd[1]: systemd-logind.service: Service has no
hold-off time, scheduling restart.
M��r 13 14:48:57 srv034 systemd[1]: Stopped Login Service.

systemd-logind service doesn't come up:

srv034:~ # systemctl status systemd-logind.service
��� systemd-logind.service - Login Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static;
vendor preset: disabled)
   Active: activating (start) since Mo 2017-03-13 15:16:35 CET; 12s ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/logind
           http://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 4360 (systemd-logind)
    Tasks: 1 (limit: 512)
   CGroup: /system.slice/systemd-logind.service
           ������4360 /usr/lib/systemd/systemd-logind

M��r 13 15:16:35 srv034 systemd[1]: Starting Login Service...



Workaround_1:
- reinstall System from scratch
(works until changing authentication to LDAP-based)

Workaround_2:
- Change Authentication back to local only
- Change from wicked to Networkmanager or vice versa
- reboot
- then use NetworkManager or wicked -> system is running
(works until changing authentication to LDAP-based)

Have seen the same behaviour on DL360Gen9 and an old ML350Gen5 with Leap 42.2.
After some reboots these machines are working now stable.


You are receiving this mail because: