SSSD Dependency Boot Warnings

Summary

SSSD dependency warnings during Linux reboot can look alarming but may be benign when SSSD is disabled or unused for centralized authentication; dependent sockets fail because the parent SSSD service is intentionally skipped (Ticket #42377).

Frequency

• 1 ticket in this evidence set reports Dependency failed for SSSD messages during reboot with delayed but successful login (Ticket #42377).

Common Causes

1. SSSD disabled or skipped while dependent sockets remain enabled. When SSSD is not configured for LDAP, Active Directory, Kerberos, or similar centralized identity services, dependent sockets such as sssd-nss, sssd-pam, sssd-autofs, sssd-pac, sssd-ssh, and sssd-sudo can report dependency failures during boot (Ticket #42377).
2. Unrelated application symptoms creating a false association. In this case, CryoSPARC 180-second timeouts were caused by CIFS share authentication/session loss, not by the SSSD boot warnings (Tickets #42377, #42484).

Diagnostic Steps

1. Confirm whether SSSD is actually used. Check whether the environment depends on centralized identity or authorization such as LDAP, Active Directory, or Kerberos before treating SSSD dependency messages as a functional outage (Ticket #42377).
2. Collect boot and hardware/software probes. journalctl -b, dmesg, inxi -xxx -F, and lspci -vvv helped support separate boot messages from hardware or application failures (Ticket #42377).
3. Investigate the application-specific logs separately. If CryoSPARC or another app is also failing, inspect that app's logs and storage dependencies instead of assuming boot-service warnings are causal (Ticket #42377).

Solutions

1. Treat disabled-SSSD dependency output as benign when centralized auth is not in use. Support advised that these messages are expected and harmless in that configuration (Ticket #42377).
2. Resolve the real application dependency. For the paired CryoSPARC issue, the fix path was IT review of the CIFS mount/session/authentication configuration for //data.einstein.edu/home, as detailed in linked ticket #42484 (Tickets #42377, #42484).
3. Offer paid software assistance when the fix is outside base hardware support. Exxact noted that a software technician could assist with the CIFS configuration under quoted support hours if the customer's IT team wanted help (Ticket #42377).

Edge Cases

• Benign warnings can still cause customer concern when they appear on only one of two similar systems. The affected system showed the SSSD messages while the companion workstation did not, but diagnostics still separated the warnings from the CryoSPARC timeout root cause (Ticket #42377).
• Boot-service warnings can distract from network storage faults. The important CryoSPARC failure path was CIFS reconnect/authentication behavior during jobs, not the SSSD dependency output seen at reboot (Tickets #42377, #42484).

Related Issues

• CryoSPARC Integration