I am seeing these services not being started when I boot using core-image-minimal on my arm bsp. I still need to reproduce this on QEMU machines. DISTRO_FEATURES_append = " systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" VIRTUAL-RUNTIME_init_manager = "systemd" VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" [ OK ] Listening on Load/Save RF …itch Status /dev/rfkill Watch. Starting Run pending postinsts... Starting Rebuild Journal Catalog... [FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details. [ OK ] Reached target Network. [ OK ] Reached target Host and Network Name Lookups. [FAILED] Failed to start Network Time Synchronization. See 'systemctl status systemd-timesyncd.service' for details. [ OK ] Reached target System Time Set. [ OK ] Reached target System Time Synchronized. Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Rebuild Journal Catalog. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Run pending postinsts. [ OK ] Stopped Network Name Resolution. [FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details. [ OK ] Stopped Network Time Synchronization. [FAILED] Failed to start Network Time Synchronization. See 'systemctl status systemd-timesyncd.service' for details. Starting Update is Completed... [ OK ] Stopped Network Name Resolution. [FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details. [ OK ] Stopped Network Time Synchronization. [FAILED] Failed to start Network Time Synchronization. See 'systemctl status systemd-timesyncd.service' for details. [ OK ] Started Update is Completed. [ OK ] Stopped Network Name Resolution. [FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details. [ OK ] Stopped Network Time Synchronization. [FAILED] Failed to start Network Time Synchronization. See 'systemctl status systemd-timesyncd.service' for details. [ OK ] Reached target System Initialization. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Listening on dropbear.socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. [ OK ] Started Kernel Logging Service. [ OK ] Started System Logging Service. Oct 18 04:29:01 odroid-xu3-lite syslog.info syslogd started: BusyBox v1.31.0 [ OK ] Started D-Bus System Message Bus. [ OK ] Started Getty on tty1. [ OK ] Started Serial Getty on ttyS0. [ OK ] Started Serial Getty on ttySAC2. [ OK ] Reached target Login Prompts. [FAILED] Failed to start Login Service. See 'systemctl status systemd-logind.service' for details. [ OK ] Reached target Multi-User System. Starting Update UTMP about System Runlevel Changes... [ OK ] Stopped Login Service. [FAILED] Failed to start Login Service. See 'systemctl status systemd-logind.service' for details. [ OK ] Stopped Network Name Resolution. [FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details. [ OK ] Stopped Network Time Synchronization. [FAILED] Failed to start Network Time Synchronization. See 'systemctl status systemd-timesyncd.service' for details. [ OK ] Started Update UTMP about System Runlevel Changes.
just capturing info for later.
this is nfs root
Loaded: loaded (/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled) Active: [[0;1;31mfailed[[0m (Result: resources) since Wed 2019-12-18 18:53:59 UTC; 3min 38s ago Docs: man:systemd-logind.service(8) man:logind.conf(5) https://www.freedesktop.org/wiki/Software/systemd/logind https://www.freedesktop.org/wiki/Software/systemd/multiseat Dec 18 18:53:59 odroid-c2 systemd[1]: systemd-logind.service: Service has no hold-off time (RestartSec=0), scheduling restart. Dec 18 18:53:59 odroid-c2 systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5. Dec 18 18:53:59 odroid-c2 systemd[1]: Stopped Login Service. Dec 18 18:53:59 odroid-c2 systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185msystemd-logind.service: Start request repeated too quickly .[[0m Dec 18 18:53:59 odroid-c2 systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185msystemd-logind.service: Failed with result 'resources'.[[0 m Dec 18 18:53:59 odroid-c2 systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to start Login Service.[[0m
altered /lib/systemd/system/systemd-logind.service RestartSec=o to 2 and it still failed once but then worked.
Seeing the same issue with poky 3.1. The workaround to change /lib/systemd/system/systemd-logind.service does not work for me. Do you have any other workaround?
not seeing this anymore