On 01/08/2015 11:54 AM, Jakub Hrozek wrote: > On Thu, Jan 08, 2015 at 09:31:16AM -0700, Orion Poplawski wrote: >> On 01/06/2015 11:32 PM, Jakub Hrozek wrote: >>> On Tue, Jan 06, 2015 at 05:06:39PM -0700, Orion Poplawski wrote: >>>> (Tue Jan 6 22:33:08 2015) [sssd[be[default]]] [get_single_value_as_string] >>>> (0x0080): More than one value found. >>>> (Tue Jan 6 22:33:08 2015) [sssd[be[default]]] >>>> [sdap_set_config_options_with_rootdse] (0x0020): get_naming_context failed. >>>> (Tue Jan 6 22:33:14 2015) [sssd[be[default]]] [get_single_value_as_string] >>>> (0x0080): More than one value found. >>> >>> This is weird as well, here SSSD is complaining that defaultNamingContext >>> attribute of rootDSE contains multiple values. But I don't see SSSD grabbing >>> the rootDSE anywhere at all..what log level did you use? >> >> Log level 3 >> >>> >>> You can read the rootDSE manually using: >>> ldapsearch -x -H ldap://server.com -s base -b "" defaultNamingContext >> >> # extended LDIF >> # >> # LDAPv3 >> # base <> with scope baseObject >> # filter: (objectclass=*) >> # requesting: defaultNamingContext >> # >> >> # >> dn: >> >> # search result >> search: 2 >> result: 0 Success >> >> # numResponses: 2 >> # numEntries: 1 >> >> I've now added a defaultnamingcontext. >> > > Did it cause any difference? > > I wouldn't expect a missing defaultNamingContext to be fatal for SSSD..
It got rid of the debug messages complaining about it :) -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane [email protected] Boulder, CO 80301 http://www.nwra.com _______________________________________________ sssd-users mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/sssd-users
