On Thu, Apr 25, 2019 at 01:05:52PM -0400, John Desantis via FreeIPA-users wrote:
Hello all,
So, for anyone following this thread, I've been able to make some progress but not enough to consider the configuration production ready.
After watching sssd logs ([domain] debug_level = 10, [sssd] debug_level = 10, and [nss] debug_level = 10) on both the client and server, I am able to reduce by ~50% the time required and failures of user look-ups via `getent passwd` and `id` by configuring the [nss] option 'entry_negative_timeout = 1'.
Hi,
this option controls how long a "failed" lookup will be cached, The default is 15s which means that in your case when the first lookup fails SSSD will reply to every request for the same user during the next 15s with "User does not exists" and will not try to get fresh data from the IPA server. Making this value shorter allows you trigger a new request to the IPA server earlier and hopefully also have a proper result earlier. But it might also cause more unneeded request to the IPA server for users or groups which really do not exist. So I would not recommend to lower this value.
According to the logs you send there is an error during the first lookup when lookup up the group adglobalposixgroup:
/var/log/sssd/sssd_ipa.domain.com.log:(Mon Apr 22 10:58:36 2019) [sssd[be[ipa.domain.com]]] [ipa_s2n_save_objects] (0x0020): Cannot find SID of object. /var/log/sssd/sssd_ipa.domain.com.log:(Mon Apr 22 10:58:36 2019) [sssd[be[ipa.domain.com]]] [ipa_s2n_save_objects] (0x0020): Object [adglobalposixgroup@ipa.domain.com] has no SID, please check the ipaNTSecurityIdentifier attribute on the server-side. /var/log/sssd/sssd_ipa.domain.com.log:(Mon Apr 22 10:58:36 2019) [sssd[be[ipa.domain.com]]] [ipa_s2n_get_list_save_step] (0x0040): ipa_s2n_save_objects failed. /var/log/sssd/sssd_ipa.domain.com.log:(Mon Apr 22 10:58:36 2019) [sssd[be[ipa.domain.com]]] [ipa_s2n_get_list_next] (0x0040): ipa_s2n_get_list_save_step failed. /var/log/sssd/sssd_ipa.domain.com.log:(Mon Apr 22 10:58:36 2019) [sssd[be[ipa.domain.com]]] [ipa_s2n_get_list_done] (0x0040): s2n get_fqlist request failed.
Is this really a group from the IPA domain? If yes and the SID is really missing (you can check with 'ipa group-show --all adglobalposixgroup) you might need the re-run the sidgen task to assign a SID.
Can you send the sssd.conf from the IPA server and client used to generate the debug logs (or the current version) as well?
bye, Sumit
No matter what other options are configured on the client via sssd, the first look-up always fails. The server logs do not indicate that the client checked the server's sssd cache on the first look-up. Only after a negative entry has been introduced and then purged will a "true" client look-up receive a result. I cannot understand why this does not happen on the IPA servers with a default sssd configuration, but happens continually on a client's generated sssd configuration via the IPA installer. Even after removing the additional trusted domains and their ID ranges, the behaviour remains.
In order to rule out the hardware on the client and an older sssd version (1.15.2), I installed on new hardware and with the latest sssd version offered via our satellite server (1.16.2), and the behavior was the same.
Why is the first user lookup-up on the native IPA client failing to retrieve the entry that is properly cached on the IPA server?
Thanks, John DeSantis
Il giorno mer 24 apr 2019 alle ore 08:42 John Desantis desantis@mail.usf.edu ha scritto:
Hello all,
Doh! I realized that I hadn't actually attached the logs; so much for trouble-shooting!
Thanks, John DeSantis
Il giorno lun 22 apr 2019 alle ore 13:07 John Desantis desantis@mail.usf.edu ha scritto:
Hello all,
I've pretty much exhausted my searching in order to find a solution to a problem I've been working on for about a week now, and now I find myself grasping at straws.
Basically, AD trust user lookups on IPA clients fail several times in a row before finally returning results (after 8-20 seconds). However, this does not happen on the IPA servers - even after clearing caches. Furthermore, querying the same list of users against a non IPA Linux client that connects directly to our AD domain using nslcd has no issues querying the same list of users.
From what I understand regarding the anatomy of the FreeIPA - AD Trust relationship, the FreeIPA servers' sssd caches are queried first by FreeIPA clients and if there is no result, then the FreeIPA server queries the AD domain controllers, receives results, caches them, and then provides the results to the FreeIPA client.
I've tried adjusting the sssd.conf file on both the server and the client, without any expected results:
ignore_group_members = True ldap_purge_cache_timeout = (various values) memcache_timeout = (various values) cache_first = (various values) ldap_opt_timeout = (various values) ldap_search_timeout = (various values)
The trust was established using the range type of "ipa-ad-trust-posix" since each user has a unique Posix UID and a shared unique Posix GID (no AD groups are returned).
I've attached logs (dirsrv and sssd) from the IPA server I directly specified via the client sssd.conf and logs from the client itself.
Any pointers and/or suggestions would be extremely helpful!
Thank you, John DeSantis
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-leave@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahoste...