Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 525352 - sys-auth/sssd-1.12.1 - [load_backend_module] (0x0010): Unable to load ad module with path (/usr/lib64/sssd/, error: /usr/lib64/sssd/ cannot open shared object file: No such file or directory
Summary: sys-auth/sssd-1.12.1 - [load_backend_module] (0x0010): Unable to load ad modu...
Status: RESOLVED DUPLICATE of bug 477190
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Markos Chandras (RETIRED)
Depends on:
Reported: 2014-10-14 00:34 UTC by KK
Modified: 2014-10-29 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description KK 2014-10-14 00:34:52 UTC
I am using gentoo hardened-sources and today emerged sssd-1.12.1 with an aim to use it to get data from Samba 4 AD. According to the Samba wiki at sssd from version 1.10.0 onwards should support the "AD id_provider".

Following their recommendations and using the suggested configuration file however results in sssd not being able to start with the following messages:
 * Starting sssd ...
 * start-stop-daemon: failed to start `/usr/sbin/sssd'                  [ !! ]
 * ERROR: sssd failed to start

Adding the debug and interactive option with logging to stederr when starting sssd reveals that it fails to open a required library file for the requested backend provider:
[load_backend_module] (0x0010): Unable to load ad module with path (/usr/lib64/sssd/, error: /usr/lib64/sssd/ cannot open shared object file: No such file or directory
[be_process_init] (0x0010): fatal error initializing data providers
[main] (0x0010): Could not initialize backend [79]
Child [] exited with code [3]

It turns out that required file /usr/lib64/sssd/ is not being installed (for a complete list of files for the sssd package see - and that's regardless of the USE flag settings (tested with all flags except augeas, selinux, test): This file is not compiled and subsequently also nor being installed.

I assume the relevant path in the source tree for the backend provider should be sssd-1.12.1/src/providers/ad which after "ebuild sssd-ebuild-file compile" does not contain any binary objects.

reproducable: always
expected behaviour: the required libs for AD id provider should be installed

Ideally this should be covered by a special AD use flag if this is not too much of a hassle.

Thanks KK
Comment 1 Markos Chandras (RETIRED) gentoo-dev 2014-10-29 19:42:37 UTC

Probably because samba4 is forced-disabled in the ebuild. Samba4 is still masked on Gentoo. See

Closing as duplicate of 477190

*** This bug has been marked as a duplicate of bug 477190 ***