User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20100101 Firefox/10.0.4 Iceweasel/10.0.4

Hi,

I've tried to configure ldap based auth on my server but there is a problem with sssd daemon. It won't start, due to version missmatch somewhere on interface between sssd and libldb1. I have installed:

newton:~ # rpm -q sssd libldb1
sssd-1.8.3-1.1.x86_64
libldb1-1.1.6-1.1.x86_64




Reproducible: Always

Steps to Reproduce:
1. upgrade to latest version (zypper ref & zypper up)
2. try to start sssd with service sssd restart (or simply reboot the system)
Actual Results:  
newton:~ # service sssd restart
redirecting to systemctl
Job failed. See system journal and 'systemctl status' for details.


newton:~ # service sssd status
redirecting to systemctl
sssd.service - System Security Services Daemon
	  Loaded: loaded (/lib/systemd/system/sssd.service; enabled)
	  Active: failed (Result: exit-code) since Sun, 24 Jun 2012 14:33:13 +0200; 3min 36s ago
	 Process: 6474 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=4)
	  CGroup: name=systemd:/system/sssd.service

Jun 24 14:33:13 newton sssd[6474]: nscd socket was detected.  Nscd caching capabilities may conflict with SSSD for users and groups. It is recommended not to run nscd in parallel with SSSD, unless nscd is configured ...oup nsswitch maps.
Jun 24 14:33:13 newton sssd[6474]: ldb: module version mismatch in src/ldb_modules/memberof.c : ldb_version=1.1.6 module_version=1.0.2


newton:~ # tail -f /var/log/messages

Jun 24 14:38:09 newton sssd: nscd socket was detected.  Nscd caching capabilities may conflict with SSSD for users and groups. It is recommended not to run nscd in parallel with SSSD, unless nscd is configured not to cache the passwd, group and netgroup nsswitch maps.
Jun 24 14:38:09 newton sssd[6491]: ldb: module version mismatch in src/ldb_modules/memberof.c : ldb_version=1.1.6 module_version=1.0.2
Jun 24 14:38:09 newton sssd[6491]: ldb: failed to initialise module /usr/lib64/ldb/memberof.so : Unavailable
Jun 24 14:38:09 newton sssd: Cannot load configuration database
Jun 24 14:38:09 newton systemd[1]: sssd.service: control process exited, code=exited status=4
Jun 24 14:38:09 newton systemd[1]: Unit sssd.service entered failed state.



Expected Results:  
The daemon should start.

Similar situation on Debian is described here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670595

perhaps it's the same bug. There it was fixed by uploading sssd 1.8.4-1 (and appropriate deps).