Reporting at boot about "SSSD" Service responder sockets

In the "boot.log.1" file (boot.log is empty ?), I see the following:

[DEPEND] Dependency failed for SSSD NSS Service responder socket.
[DEPEND] Dependency failed for SSSD…toFS Service responder socket.
[DEPEND] Dependency failed for SSSD PAC Service responder socket.
[DEPEND] Dependency failed for SSSD…vice responder private socket.
[DEPEND] Dependency failed for SSSD PAM Service responder socket.
[DEPEND] Dependency failed for SSSD SSH Service responder socket.
[DEPEND] Dependency failed for SSSD Sudo Service responder socket.

Is there anything here that I need to be worried about ?

Hopefully, the following information might help:

3 Likes

So ... if my box is a personal tool, not a server, does that mean that I can remove the sssd package completely ?

It looks just like that. I'm certain that one does not need SSSD service until he does not

...access remote directories and authentication mechanisms...

At the same time I can not ensure you that removal of pre-installed SSSD daemon would not cripple some OS integrated functionality.

3 Likes

OK. Play it safe. Leave well enough alone! :slight_smile:

@ugnvs is right, SSSD is not needed in a home setup. One of the comments explains a lot:

It's not an error though. It's just logging that it didn't start sssd, which isn't an error for a user who doesn't need the enterprise integration that sssd provides. I realise that "start condition failed" might sound alarming, but that's the mechanism that's supposed to be used to avoid attempting to start a service when that service isn't required.

It seems that sssd can't do its job because it can't find its configuration files.
If you really want to start sssd , this should do the job:

sudo cp /usr/lib/x86_64-linux-gnu/sssd/conf/sssd.conf /etc/sssd/.
sudo chmod 600 /etc/sssd/sssd.conf

This gets the configfile from the directory where the package dropped it and puts in in the directory where sssd expects it to be.

2 Likes