On (30/01/20 07:31), Sumit Bose wrote:
On Wed, Jan 29, 2020 at 07:23:16PM -0000, Manjot Singh wrote:
> ● sssd.service - System Security Services Daemon
> Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset:
enabled)
> Active: failed (Result: exit-code) since Wed 2020-01-29 14:12:32 EST; 9s ago
> Process: 23217 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} (code=exited, status=4)
> Main PID: 23217 (code=exited, status=4)
>
> Jan 29 14:12:32 pop-os systemd[1]: sssd.service: Service RestartSec=100ms expired,
scheduling restart.
> Jan 29 14:12:32 pop-os systemd[1]: sssd.service: Scheduled restart job, restart
counter is at 5.
> Jan 29 14:12:32 pop-os systemd[1]: Stopped System Security Services Daemon.
> Jan 29 14:12:32 pop-os systemd[1]: sssd.service: Start request repeated too quickly.
> Jan 29 14:12:32 pop-os systemd[1]: sssd.service: Failed with result
'exit-code'.
> Jan 29 14:12:32 pop-os systemd[1]: Failed to start System Security Services Daemon.
Hi,
I guess there might be some issues with your sssd.conf. Please try to
run SSSD manually as root
/usr/sbin/sssd -i -d 10
Running this command as user will cause issues with SELinux context for some
file :-)
But very critical messages shoudl be logged by default into
/var/log/sssd/sssd.log
And some configuration issues can be detected by `sssctl config-check`
You might try to follow following page
https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html
LS