Learn more about these different git repos.
Other Git URLs
The following behaviour can be seen when requesting a non-existing netgroup:
$ getent netgroup unknown_netgroup $ getent netgroup unknown_netgroup unknown_netgroup
getent netgroup should always return nothing if the netgroup does not exists.
The subject line is a bit misleading. This appears to be happening intermittently, not always at the second attempt:
[sgallagh@sgallagh ~]$ getent netgroup nosuchng [sgallagh@sgallagh ~]$ getent netgroup nosuchng nosuchng [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 nosuchng2 [sgallagh@sgallagh ~]$ getent netgroup nosuchng2 [sgallagh@sgallagh ~]$
Furthermore, no cached entry is appearing in the sysdb for the netgroup, yet sssd_nss.log shows:
(Thu Mar 10 08:08:22 2011) [sssd[nss]] [get_client_cred] (9): Client creds: euid[13041] egid[13041] pid[5146]. (Thu Mar 10 08:08:22 2011) [sssd[nss]] [accept_fd_handler] (4): Client connected! (Thu Mar 10 08:08:22 2011) [sssd[nss]] [sss_cmd_get_version] (5): Received client version [1]. (Thu Mar 10 08:08:22 2011) [sssd[nss]] [sss_cmd_get_version] (5): Offered version [1]. (Thu Mar 10 08:08:22 2011) [sssd[nss]] [setnetgrent_send] (4): Requesting info for netgroup [nosuchng2] from [<ALL>] (Thu Mar 10 08:08:22 2011) [sssd[nss]] [nss_cmd_getnetgrent] (4): Requesting netgroup data (Thu Mar 10 08:08:22 2011) [sssd[nss]] [nss_cmd_getnetgrent] (6): Returning results for [nosuchng2] (Thu Mar 10 08:08:22 2011) [sssd[nss]] [nss_cmd_getnetgrent_process] (5): No entries found (Thu Mar 10 08:08:22 2011) [sssd[nss]] [client_recv] (5): Client disconnected!
So the problem is definitely in the NSS responder somewhere.
component: SSSD => NSS
I think it is the in-memory cache which we use to avoid too frequent requests to the server. Currently we cannot distinguish between a cached empty group and a cached non-existing group.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.6.0
owner: somebody => jhrozek
owner: jhrozek => jzeleny
status: new => assigned
Fixed by 7a0e6e2
patch: => 0 resolution: => fixed status: assigned => closed
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=785888
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=785888 785888]
Metadata Update from @sbose: - Issue assigned to jzeleny - Issue set to the milestone: SSSD 1.6.0
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1862
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.