I recently upgraded to Ubuntu (Gnome) 20.10 and ever since I have lots of messages like
SSSD failed to start system security daemon
dependency failed for PAM security socker
... and some more dependency related info...during boot. As a beginner to Ubuntu I am not well able to judge how serious this problem is. But I don't want red flagged lines during my boot and that makes that I want to eliminate this problem. In journalctl -b I found some messages pertaining to to SSSD (see below). Especially the first message (in red) is worrysome: it appears that SSSD is not running.
- why is this caused by upgrading to 20.10?
- what can I do? I don't have an sssd.conf file in /etc/sssd but I am not sure why it has been removed or why it isn't present
As the journalctl file is about 8000 lines I only post the lines that signal the start of the sssd problems. If more info is needed please tell me.
Nov 05 20:44:30 loosken sssd[1031]: SSSD couldn't load the configuration database [2]: No such file or directory.
Nov 05 20:44:30 loosken systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION
Nov 05 20:44:30 loosken systemd[1]: sssd.service: Failed with result 'exit-code'.
Nov 05 20:44:30 loosken systemd[1]: Failed to start System Security Services Daemon.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD PAM Service responder private socket.
Nov 05 20:44:30 loosken snapd[1030]: AppArmor status: apparmor is enabled and all features are available
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD PAM Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-pam.socket: Job failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: sssd-pam-priv.socket: Job failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD NSS Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-nss.socket: Job failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD SSH Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-ssh.socket: Job failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD Sudo Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-sudo.socket: Job failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD AutoFS Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-autofs.socket: Job failed with result 'dependency'.
Nov 05 20:44:30 loosken systemd[1]: Dependency failed for SSSD PAC Service responder socket.
Nov 05 20:44:30 loosken systemd[1]: sssd-pac.socket: Job failed with result 'dependency'.
Nov 05 20:44:30 loosken dbus-daemon[995]: [system] AppArmor D-Bus mediation is enabled1 Answer
The first message says "SSSD couldn't load the configuration database [2]: No such file or directory." So, does the "/etc/sssd/sssd.conf" file exists? If not, you should create one as "root" with permission "0600".
