Comments

346 Comments

The new sssd.service fails to start in F28 and F27 for me causing a boot delay of around 1:53 minutes. Where would I started collecting useful data about that?

systemctl status sssd.service

‚óŹ sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Sat 2018-03-17 15:02:33 CET; 9min ago Process: 793 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} (code=exited, status=0/SUCCESS) Main PID: 793 (code=exited, status=0/SUCCESS)

Mar 17 15:01:03 localhost.localdomain systemd[1]: Starting System Security Services Daemon... Mar 17 15:01:08 localhost.localdomain sssd[793]: Starting up Mar 17 15:01:09 localhost.localdomain sssd[be[implicit_files]][827]: Starting up Mar 17 15:01:11 localhost.localdomain sssd[nss][843]: Starting up Mar 17 15:02:33 localhost.localdomain systemd[1]: sssd.service: Start operation timed out. Terminating. Mar 17 15:02:33 localhost.localdomain sssd[nss][843]: Shutting down Mar 17 15:02:33 localhost.localdomain sssd[be[implicit_files]][827]: Shutting down Mar 17 15:02:33 localhost.localdomain systemd[1]: sssd.service: Failed with result 'timeout'. Mar 17 15:02:33 localhost.localdomain systemd[1]: Failed to start System Security Services Daemon.

karma

Works for me.

karma

Looks good to me.

It works for me. Thank you!

karma

no regressions noted

karma

works for me in a VM

works for me in a VM

WFM

no regressions noted

karma

Works for me

karma

works for me

works for me

karma

No regressions here.

karma

Works

karma

Works

karma

works for me in a VM

karma

no regressions noted

karma

works for me

karma

works for me

fixing issue in previous build