Created attachment 386090 [details] Domain/Realm specific log. I'm running ~amd64 hardened with systemd. Updating from sssd-1.9.6-r3 to sssd.1.12.1 results in sssd being unable to start. home.private is my domain, HOME.PRIVATE is my kerberos realm name. I'm authenticating against FreeIPA 3.0.0-37.el6 running on CentOS 6. Attached is my domain log (it shows a bunch of attempts at starting the daemon) as well as sssd.log, which shows a single launch attempt of the daemon. Please let me know what other logs you'd like.
Created attachment 386092 [details] sssd.log
Created attachment 386094 [details] Build log for sssd-1.12.1 Using use flags: [ebuild R ] sys-auth/sssd-1.12.1 USE="acl augeas autofs locator manpages netlink nls python ssh sudo -nfsv4 (-selinux) {-test}" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" 0 KiB
I think it's the same reason as explained on #525352. Samba4 is masked on Gentoo, hence samba4 support has been disabled in the ebuild until that's fixed. From the Makefile.am if BUILD_SAMBA sssdlib_LTLIBRARIES += \ libsss_ipa.la \ libsss_ad.la endif I am sorry :) You can always join the effort in fixing samba4 and get things fixed properly in the tree :) *** This bug has been marked as a duplicate of bug 489762 ***