Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=895565 (Red Hat Enterprise Linux 6)
Description of problem: id lookup shows "Memory buffer error" in domain log Version-Release number of selected component (if applicable): 1.9.2-68 How reproducible: Always Steps to Reproduce: 1. User and group in ldap as follows: dn: uid=User_CS1,ou=Users,dc=example,dc=com objectClass: posixAccount objectClass: account cn: User_CS1 homeDirectory: /home/User_CS1 userPassword:: U2VjcmV0MTIz uid: User_CS1_Alias uid: User_CS1 uidNumber: 304560 gidNumber: 304560 dn: cn=User_CS1_grp1,ou=Groups,dc=example,dc=com objectClass: posixGroup memberUid: User_CS1 cn: User_CS1_grp1_Alias cn: User_CS1_grp1 gidNumber: 304560 2. sssd.conf domain section has: [domain/PROXY] id_provider = proxy debug_level = 0xFFF0 proxy_lib_name = ldap proxy_pam_target = sssdproxyldap 3. # id User_CS1 uid=304560(User_CS1_Alias) gid=304560(User_CS1_grp1_Alias) groups=304560(User_CS1_grp1_Alias) Actual results: id lookup returns appropriate result, but errors appear in the domain log: (Tue Jan 15 20:01:22 2013) [sssd[be[PROXY]]] [get_initgr_groups_process] (0x0040): proxy -> initgroups_dyn failed (0)[Success] (Tue Jan 15 20:01:22 2013) [sssd[be[PROXY]]] [get_initgr] (0x0040): Could not process initgroups (Tue Jan 15 20:01:22 2013) [sssd[be[PROXY]]] [ldb] (0x4000): cancel ldb transaction (nesting: 0) (Tue Jan 15 20:01:22 2013) [sssd[be[PROXY]]] [acctinfo_callback] (0x0100): Request processed. Returned 3,5,Internal Error (Memory buffer error) Expected results: id lookup should not throw errors in the domain log. Additional info:
Ondra was looking into the bug already.
blockedby: => blocking: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => owner: somebody => okos selected: => testsupdated: => 0
This is happening only with aliases, and also it depends on their order. e.g. if i'm looking for User_CS1 and i have a setup with:
dn: uid=User_CS1,ou=People,dc=example,dc=com ... uid: User_CS1_Alias uid: User_CS1
then the error message will appear, with reverse order (alias on the second place)
dn: uid=User_CS1,ou=People,dc=example,dc=com ... uid: User_CS1 uid: User_CS1_Alias
the error message won't show. However, all user data is cached and returned properly.
_comment0: This is happening only with aliases, and also it depends on their order. e.g. if i'm looking for User_CS1 and i have a setup with: {{{ dn: uid=User_CS1,ou=People,dc=idm,dc=lab,dc=bos,dc=redhat,dc=com ... uid: User_CS1_Alias uid: User_CS1 }}} then the error message will appear, with reverse order (alias on the second place) {{{ dn: uid=User_CS1,ou=People,dc=idm,dc=lab,dc=bos,dc=redhat,dc=com ... uid: User_CS1 uid: User_CS1_Alias }}} the error message won't show. However, all user data is cached and returned properly. => 1358858552955271
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.12 beta priority: major => minor
Simo fixed the bug in 66d1f56
changelog: => owner: okos => simo review: => 0
milestone: SSSD 1.14 beta => SSSD 1.10.2 resolution: => fixed status: new => closed
Metadata Update from @jhrozek: - Issue assigned to simo - Issue set to the milestone: SSSD 1.10.2
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/2811
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.