Sssd/ldb breakage

Rocky Linux Help & Support
1

Somewhere between
sssd-common-2.9.5-4.el9_5.1.x86_64 and sssd-common-2.9.6-4.el9_6.2.x86_64, memberof.so has been moved from /usr/lib64/ldb/modules/ldb/ to /usr/lib64/samba/ldb/. This prevents sssd from starting:

   *  (2025-11-27 15:31:59): [sssd] [sysdb_domain_init_internal] (0x0200): DB File for cm.cluster: /var/lib/sss/db/cache_cm.cluster.ldb
   *  (2025-11-27 15:31:59): [sssd] [sysdb_domain_init_internal] (0x0200): Timestamp file for cm.cluster: /var/lib/sss/db/timestamps_cm.cluster.ldb
   *  (2025-11-27 15:31:59): [sssd] [sysdb_ldb_connect] (0x4000): No ldb module path set in env
   *  (2025-11-27 15:31:59): [sssd] [ldb] (0x0010): WARNING: Module [memberof] not found - do you need to set LDB_MODULES_PATH?
********************** BACKTRACE DUMP ENDS HERE *********************************

Is this a proper bug, or should I adjust my config? If so, how?

Thanks a lot,

A.

2

Once you have ensured all sssd packages are updated, as well as libldb package has also been updated, you will need to do:

dnf install ldb-tools
ls -l /var/lib/sss/db/
systemctl stop sssd
mv /var/lib/sss/db/cache_LDAP.ldb /var/lib/sss/db/cache_LDAP.ldb.bak
mv /var/lib/sss/db/timestamps_LDAP.ldb /var/lib/sss/db/timestamps_LDAP.ldb.bak
systemctl start sssd

solution found from google, I noticed your filenames are different, so it may require you to use your filenames, rather than the ones I’ve found above.

It would suggest that after renaming those files, new ones will be created that will use the new path for the memberof.so file.

3

Thanks a lot, this has solved it. I did not even rename the databases, just updating libldb and/or installing ldb-tools (I didn’t try doing just one or the other) was enough.

Best,

A.

1 Like