Bug 709260
Summary: | sssd is constantly trying to find local user in configured domain | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Kemot1000 <kemot1000> |
Component: | sssd | Assignee: | Stephen Gallagher <sgallagh> |
Status: | CLOSED NOTABUG | QA Contact: | Chandrasekar Kannan <ckannan> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1 | CC: | benl, grajaiya, jgalipea, prc |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-05-31 11:57:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 709342, 709352 |
Description
Kemot1000
2011-05-31 08:32:19 UTC
This is not a bug in SSSD. The design of initgroups() in glibc requires that ALL name-service plugins are checked whenever initgroups() is requested of any user. Unlike the getpwuid/getpwnam() routines, which stops after the first time it encounters the requested user, initgroups() will always search through all of them. If this is causing undue stress on your LDAP server, you can add the filter_users = locallinuxuser And it will be permanently stored in the negative cache. Hi, Thanks for your response. I added localinuxuser to sssd.conf (filter_users = root,locallinuxuser). Stopped sssd then removed everything from /var/lib/sss/db folder just in case. Started again and I still get: (Tue May 31 14:14:47 2011) [sssd[nss]] [sss_ncache_check_str] (8): Checking negative cache for [NCE/USER/DOMAINNAME/localinuxuser] (Tue May 31 14:14:47 2011) [sssd[nss]] [nss_cmd_initgroups_search] (2): User [DOMAINNAME] does not exist in [localinuxuser]! (negative cache) Also this is strange: User [DOMAINNAME] does not exist in [localinuxuser] Part of sssd -i -d 9 output: (Tue May 31 14:14:47 2011) [sssd[nss]] [get_client_cred] (9): Client creds: euid[0] egid[0] pid[16717]. (Tue May 31 14:14:47 2011) [sssd[nss]] [accept_fd_handler] (4): Client connected! (Tue May 31 14:14:47 2011) [sssd[nss]] [sss_cmd_get_version] (5): Received client version [1]. (Tue May 31 14:14:47 2011) [sssd[nss]] [sss_cmd_get_version] (5): Offered version [1]. (Tue May 31 14:14:47 2011) [sssd[nss]] [nss_cmd_initgroups] (4): Requesting info for [localinuxuser] from [<ALL>] (Tue May 31 14:14:47 2011) [sssd[nss]] [sss_ncache_check_str] (8): Checking negative cache for [NCE/USER/DOMAINNAME/localinuxuser] (Tue May 31 14:14:47 2011) [sssd[nss]] [nss_cmd_initgroups_search] (2): User [DOMAINNAME] does not exist in [localinuxuser]! (negative cache) (Tue May 31 14:14:47 2011) [sssd[nss]] [nss_cmd_initgroups_search] (2): No matching domain found for [localinuxuser], fail! (Tue May 31 14:14:47 2011) [sssd[nss]] [client_recv] (5): Client disconnected! (In reply to comment #3) > Hi, > > Thanks for your response. I added localinuxuser to sssd.conf (filter_users = > root,locallinuxuser). > Stopped sssd then removed everything from /var/lib/sss/db folder just in case. > Started again and I still get: > (Tue May 31 14:14:47 2011) [sssd[nss]] [sss_ncache_check_str] (8): Checking > negative cache for [NCE/USER/DOMAINNAME/localinuxuser] > > (Tue May 31 14:14:47 2011) [sssd[nss]] [nss_cmd_initgroups_search] (2): User > [DOMAINNAME] does not exist in [localinuxuser]! (negative cache) > Yes, this is expected. We still get the request, this is just the notification that it's been detected in the negative cache, which means that it won't continue on to LDAP (it gets rejected locally). This is the best that we can do, given the way that glibc functions. > Also this is strange: > User [DOMAINNAME] does not exist in [localinuxuser] > Whoops, that's a bug in the log message. It's harmless, though. We just reversed the two variables being printed. The processing is occurring properly. I opened https://bugzilla.redhat.com/show_bug.cgi?id=709342 to fix the typo. Thanks for your help |