#1581 sssd_be crashes while looking up users
Closed: Fixed None Opened 11 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=866542 (Red Hat Enterprise Linux 6)

Description of problem:
sssd_be crashes while looking up users

Version-Release number of selected component (if applicable):
sssd-1.9.2-2.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. sssd.conf domain section:
[domain/LDAP]
debug_level = 0xFFF0
id_provider = ldap
auth_provider = ldap
ldap_uri = ldap://ldapserver.example.com
ldap_search_base = dc=example,dc=com
ldap_tls_cacert = /etc/openldap/certs/server.pem

2. Lookup a user in ldap:
# getent passwd kau1    <== Returns nothing. sssd_be crashes

Actual results:
Lookup fails and sssd_be crashes.

Expected results:
Lookup succeeds

Additional info:

/var/log/messages shows:

Oct 15 19:48:40 dhcp201-200 kernel: sssd_be[6250]: segfault at 0 ip
00007fe25bf46351 sp 00007fff7b9686d0 error 4 in
libsss_ldap.so[7fe25be58000+139000]
Oct 15 19:48:40 dhcp201-200 abrtd: Directory 'ccpp-2012-10-15-19:48:40-6250'
creation detected
Oct 15 19:48:40 dhcp201-200 abrt[6263]: Saved core dump of pid 6250
(/usr/libexec/sssd/sssd_be) to /var/spool/abrt/ccpp-2012-10-15-19:48:40-6250
(1265664 bytes)
Oct 15 19:48:40 dhcp201-200 sssd[be[LDAP]]: Starting up

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
milestone: NEEDS_TRIAGE => SSSD 1.9.3
owner: somebody => jhrozek
status: new => assigned
testsupdated: => 0

Fields changed

patch: 0 => 1

master: f2c39d4

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.3

7 years ago

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/2623

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata