sssd sedfault in libldap_r-2.4.so.2.8.1

Bug #932823 reported by Jason Sharp
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sssd (Ubuntu)
New
Undecided
Unassigned

Bug Description

my sssd.conf

root@vut-precise02:~# cat /etc/sssd/sssd.conf
[sssd]
config_file_version = 2
services = nss, pam
domains = LOCAL
debug_level = 9

[nss]
filter_groups = root
filter_users = root

[pam]

[domain/LOCAL]
min_id = 1000
id_provider = ldap
acces_provider = ldap
auth_provider = krb5
cache_credentials = true
chpass_provider = krb5
ldap_access_order = expire
ldap_account_expire_policy = ad
ldap_uri = ldap://chidc.us.xxxxxxxxxxx.com
ldap_search_base = ou=accounts,dc=us,dc=xxxxxxxxxxx,dc=com
ldap_schema = rfc2307bis
ldap_user_object_class = user
ldap_group_object_class = top
ldap_tls_reqcert = allow
ldap_krb5_init_creds = true
ldap_sasl_mech = GSSAPI
ldap_sasl_canonicalize = true
ldap_sasl_authid = VUT-PRECISE02$
ldap_krb5_ticket_lifetime = 86400
ldap_force_upper_case_realm = true
ldap_user_home_directory = unixHomeDirectory
ldap_user_ad_account_expires = accountExpires
ldap_user_ad_account_control = userAccountControl
ldap_user_principal = userPrincipalName
ldap_user_name = sAMAccountName
ldap_user_fullname = sAMAccountName
krb5_server = US.xxxxxxxxxxx.COM
krb5_realm = US.xxxxxxxxxxx.COM
krb5_ccachedir = /tmp
krb5_ccname_template = FILE:%d/krb5cc_%U_XXXXXX
krb5_keytab = /etc/krb5.keytab
krb5_renewable_lifetime = 24h
krb5_lifetime = 24h
krb5_renew_interval = 10s
krb5_use_fast = try

This same config worked back in alpha 1, no changes have been made. Since the upgrade I am receiving the following message in syslog

root@vut-precise02:~# id jsharp

Feb 15 09:21:19 vut-precise02 kernel: [ 934.107585] sssd_be[2129]: segfault at 0 ip 00007fec1e2eeeb1 sp 00007fff654e9e10 error 4 in libldap_r-2.4.so.2.8.1[7fec1e2d5000+4b000]
Feb 15 09:21:20 vut-precise02 sssd[be[drwholdings]]: Starting up
Feb 15 09:21:26 vut-precise02 kernel: [ 941.045423] sssd_be[2153]: segfault at 0 ip 00007ff46792beb1 sp 00007fff4b791850 error 4 in libldap_r-2.4.so.2.8.1[7ff467912000+4b000]
Feb 15 09:21:27 vut-precise02 sssd[be[drwholdings]]: Starting up

/var/log/sssd/sssd.log shows

(Wed Feb 15 09:23:13 2012) [sssd] [service_check_alive] (4): Checking service pam(2104) is still alive
(Wed Feb 15 09:23:13 2012) [sssd] [service_send_ping] (4): Pinging pam
(Wed Feb 15 09:23:13 2012) [sssd] [sbus_add_timeout] (8): 0x23cf0c0
(Wed Feb 15 09:23:13 2012) [sssd] [sbus_remove_timeout] (8): 0x23cf0c0
(Wed Feb 15 09:23:13 2012) [sssd] [sbus_dispatch] (9): dbus conn: 23C43E0
(Wed Feb 15 09:23:13 2012) [sssd] [sbus_dispatch] (9): Dispatching.
(Wed Feb 15 09:23:13 2012) [sssd] [ping_check] (4): Service pam replied to ping
(Wed Feb 15 09:23:13 2012) [sssd] [sbus_remove_timeout] (8): 0x23cc740
(Wed Feb 15 09:23:13 2012) [sssd] [sbus_dispatch] (9): dbus conn: 23C4250
(Wed Feb 15 09:23:13 2012) [sssd] [sbus_dispatch] (9): Dispatching.
(Wed Feb 15 09:23:13 2012) [sssd] [ping_check] (4): Service nss replied to ping
(Wed Feb 15 09:23:16 2012) [sssd] [service_check_alive] (4): Checking service drwholdings(2157) is still alive
(Wed Feb 15 09:23:16 2012) [sssd] [service_send_ping] (4): Pinging drwholdings
(Wed Feb 15 09:23:16 2012) [sssd] [sbus_add_timeout] (8): 0x23cc740
(Wed Feb 15 09:23:16 2012) [sssd] [sbus_remove_timeout] (8): 0x23cc740
(Wed Feb 15 09:23:16 2012) [sssd] [sbus_dispatch] (9): dbus conn: 23D4650
(Wed Feb 15 09:23:16 2012) [sssd] [sbus_dispatch] (9): Dispatching.
(Wed Feb 15 09:23:16 2012) [sssd] [ping_check] (4): Service drwholdings replied to ping

id jsharp just sits, waiting

Related branches

Revision history for this message
Stephen Gallagher (stephen-gallagherhome) wrote :

This might be related to https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888

Could you check whether downgrading to openldap libraries 2.4.26 or older fixes the issue?

Revision history for this message
Jason Sharp (jsharp) wrote :

I used the same ubuntu package referenced in the other bug report

I am no longer getting the connect marked offline, or a segfault in the syslog, however, lookup's still are broken

Revision history for this message
Stephen Gallagher (stephen-gallagherhome) wrote :

Then let's have this bug closed as a dup of 929888.

Please open a new bug with the logs of the new issue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.