Description of problem: This is based on bug 488597. In one sentence: due to nss-pam-ldapd / nscd miscommunication nscd is discarding cached entries even with unlimited reload count. It would seem that there will be no change in nscd so nss-pam-ldapd must be adjusted. Most relevant background information: https://bugzilla.redhat.com/show_bug.cgi?id=488597#c0 https://bugzilla.redhat.com/show_bug.cgi?id=488597#c36 https://bugzilla.redhat.com/show_bug.cgi?id=488597#c39 http://sourceware.org/bugzilla/show_bug.cgi?id=2132#c14
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This seems to be still unfixed, changing version to rawhide.
If someone is able to confirm the correct result codes an NSS module should return to Glibc [1] I would be more than happy to fix this. http://sourceware.org/bugzilla/show_bug.cgi?id=2132#c14
(In reply to comment #3) > If someone is able to confirm the correct result codes an NSS module should > return to Glibc [1] I would be more than happy to fix this. > > http://sourceware.org/bugzilla/show_bug.cgi?id=2132#c14 If I'm not mistaken the glibc maintainer has changed - CC'ing Jeff who might hopefully have the insight about this. Thanks in advance.
Yes, Carlos O'Donell is taking over glibc from me. I was really just a caretaker while the glibc team was rebuilt. Adding him to the CC list on this bug.
There is a *lot* of background discussion on this issue and I have not reviewed all of it, but I have gone through the bulk of it. Someone please correct me if my understanding is correct: * One wants to operate in disconnected state. * One uses nss-pam-ldapd and nscd to access ldap and cache those entries. * nscd can already cache entries forever given that a fuzzy set of circumstances hold true. * interaction between nss-pam-ldapd are causing nscd to discard cached entries which renders the disconnected usage broken. Is this the *current* status in Fedora rawhide? Is this still broken?
Consider using SSSD instead of nss-pam-ldap nscd. It was built to solve exactly these problems. SSSD = predicatable cache + consistent online and offline behavior. https://fedorahosted.org/sssd/
(In reply to comment #6) > There is a *lot* of background discussion on this issue and I have not > reviewed all of it, but I have gone through the bulk of it. > > Someone please correct me if my understanding is correct: > * One wants to operate in disconnected state. > * One uses nss-pam-ldapd and nscd to access ldap and cache those entries. > * nscd can already cache entries forever given that a fuzzy set of > circumstances hold true. > * interaction between nss-pam-ldapd are causing nscd to discard cached > entries which renders the disconnected usage broken. Yes, this summarizes it. And more technical details on the links in comment 0 and comment 3 as you surely noticed. > Is this the *current* status in Fedora rawhide? Is this still broken? Sorry, I'm still stuck with F17 so can't comment on rawhide status but based on Arthur's update last week I think nss-pam-ldapd hasn't changed on this front recently and you might know best the nscd side. My *guess* is that rawhide is still affected. Thanks.
I won't be able to get to this for a while as we fix the getaddrinfo problems in glibc which are of the highest priority for fedora. As a workaround one might be able to switch, as suggested, to SSSD (haven't verified that this does everything you need). At the end of the day we still want nscd and nss-pam-ldapd to work correctly. We'll review this after the getaddrinfo work is done.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Given that this is related to nscd caching, I'd like to review this in rawhide as a use case for other fixes we're doing. Moving forward for verification.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
sssd fixes this, as far as I know.