30.9. Troubleshooting SSSD
30.9.1. Checking SSSD Log Files
/var/log/sssd/directory. SSSD produces a log file for each domain, as well as an
/var/log/securefile logs authentication failures and the reason for the failure.
debug_levelparameter for each section in the
sssd.conffile for which to product extra logs. For example:
[sssd] config_file_version = 2 services = nss, pam domains = LDAP
debug_level = 9
Table 30.8. Debug Log Levels
|0||Fatal failures. Anything that would prevent SSSD from starting up or causes it to cease running.|
|1||Critical failures. An error that doesn't kill the SSSD, but one that indicates that at least one major feature is not going to work properly.|
|2||Serious failures. An error announcing that a particular request or operation has failed.|
|3||Minor failures. These are the errors that would percolate down to cause the operation failure of 2.|
|6||Trace messages for operation functions.|
|7||Trace messages for internal control functions.|
|8||Contents of function-internal variables that may be interesting.|
|9||Extremely low-level tracing information.|
30.9.2. Problems with SSSD Configuration
SSSD requires that the configuration file be properly set up, with all the required entries, before the daemon will start.
- SSSD requires at least one properly configured domain before the service will start. Without a domain, attempting to start SSSD returns an error that no domains are configured:
# sssd -d4 [sssd] [ldb] (3): server_sort:Unable to register control with rootdse! [sssd] [confdb_get_domains] (0): No domains configured, fatal error! [sssd] [get_monitor_config] (0): No domains configured.Edit the
/etc/sssd/sssd.conffile and create at least one domain.
- SSSD also requires at least one available service provider before it will start. If the problem is with the service provider configuration, the error message indicates that there are no services configured:
[sssd] [get_monitor_config] (0): No services configured!Edit the
/etc/sssd/sssd.conffile and configure at least one service provider.
ImportantSSSD requires that service providers be configured as a comma-separated list in a single
servicesentry in the
/etc/sssd/sssd.conffile. If services are listed in multiple entries, only the last entry is recognized by SSSD.
This may be due to an incorrect
ldap_schema setting in the
[domain/DOMAINNAME] section of
memberuidattribute, which contains the name of the users that are members. In an RFC2307bis server, group members are stored as the multi-valued
uniqueMemberattribute which contains the DN of the user or group that is a member of this group. RFC2307bis allows nested groups to be maintained as well.
- Restarting SSSD.
ldap_group_name = uniqueMember
To perform authentication, SSSD requires that the communication channel be encrypted. This means that if
sssd.conf is configured to connect over a standard protocol (
ldap://), it attempts to encrypt the communication channel with Start TLS. If
sssd.conf is configured to connect over a secure protocol (
ldaps://), then SSSD uses SSL.
syslogmessage is written, indicating that TLS encryption could not be started. The certificate configuration can be tested by checking if the LDAP server is accessible apart from SSSD. For example, this tests an anonymous bind over a TLS connection to
$ ldapsearch -x -ZZ -h test.example.com -b dc=example,dc=com
ldap_start_tls: Connect error (-11) additional info: TLS error -8179:Unknown code ___f 13
- Obtain a copy of the public CA certificate for the certificate authority used to sign the LDAP server certificate and save it to the local system.
- Add a line to the
sssd.conffile that points to the CA certificate on the filesystem.
ldap_tls_cacert = /path/to/cacert
- If the LDAP server uses a self-signed certificate, remove the
ldap_tls_reqcertline from the
sssd.conffile.This parameter directs SSSD to trust any certificate issued by the CA certificate, which is a security risk with a self-signed CA certificate.
When running SELinux in enforcing mode, the client's SELinux policy has to be modified to connect to the LDAP server over the non-standard port. For example:
# semanage port -a -t ldap_port_t -p tcp 1389
This usually means that SSSD cannot connect to the NSS service.
- Ensure that NSS is running:
# service sssd status
- If NSS is running, make sure that the provider is properly configured in the
[nss]section of the
/etc/sssd/sssd.conffile. Especially check the
- Make sure that NSS is included in the list of services that SSSD uses.
- Check the configuration in the
If searches are returning the incorrect user information, check that there are not conflicting usernames in separate domains. When there are multiple domains, set the
use_fully_qualified_domains attribute to
true in the
/etc/sssd/sssd.conf file. This differentiates between different users in different domains with the same name.
When attempting to change a local SSSD user's password, it may prompt for the password twice:
[root@clientF11 tmp]# passwd user1000 Changing password for user user1000. New password: Retype new password: New Password: Reenter new Password: passwd: all authentication tokens updated successfully.
use_authtokoption is correctly configured in your