RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1602025 - sssd problem
Summary: sssd problem
Keywords:
Status: CLOSED DUPLICATE of bug 1636172
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.10
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: sssd-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-17 15:58 UTC by Kapetanakis Giannis
Modified: 2022-03-13 15:14 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-14 12:26:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
abrt report for sssd_pam (31.94 KB, text/plain)
2018-10-14 17:48 UTC, M Sanderson 		no flags Details
View All

Description Kapetanakis Giannis 2018-07-17 15:58:03 UTC 
After updating from 6.9 -> 6.10 
sssd-1.13.3-60 does not work:

Jul 17 18:32:52 sssd: Starting up
Jul 17 18:32:52 sssd[be[DOMAIN1]]: Starting up
Jul 17 18:32:52 sssd[be[DOMAIN2]]: Starting up
Jul 17 18:32:52 sssd[nss]: Starting up
Jul 17 18:32:52 sssd[pam]: Starting up
Jul 17 18:32:55 kernel: sssd_pam[5922] general protection ip:341740dc6c sp:7ffd949039a0 error:0 in libldb.so.1.1.25[3417400000+2d000]
Jul 17 18:32:55 sssd[pam]: Starting up
Jul 17 18:33:04 kernel: sssd_pam[5941] general protection ip:341740dc6c sp:7ffcfc857ed0 error:0 in libldb.so.1.1.25[3417400000+2d000]
Jul 17 18:33:06 sssd[pam]: Starting up
Jul 17 18:33:13 kernel: sssd_pam[5984] general protection ip:341740dc6c sp:7fffacf17b10 error:0 in libldb.so.1.1.25[3417400000+2d000]
Jul 17 18:33:17 sssd[pam]: Starting up
Jul 17 18:33:32 kernel: sssd_pam[6013] general protection ip:341740dc6c sp:7ffcc6794d50 error:0 in libldb.so.1.1.25[3417400000+2d000]
Jul 17 18:33:32 sssd: Exiting the SSSD. Could not restart critical service [pam].
Jul 17 18:33:32 sssd[nss]: Shutting down
Jul 17 18:33:32 sssd[be[DOMAIN1]]: Shutting down
Jul 17 18:33:32 sssd[be[DOMAIN2]]: Shutting down

downgrading back to 6.9 packages from updates solves the problem

working versions:
libsss_idmap-1.13.3-58.el6_9.x86_64
python-sss-1.13.3-58.el6_9.x86_64
python-sssdconfig-1.13.3-58.el6_9.noarch
python-sss-murmur-1.13.3-58.el6_9.x86_64
sssd-1.13.3-58.el6_9.x86_64
sssd-ad-1.13.3-58.el6_9.x86_64
sssd-client-1.13.3-58.el6_9.x86_64
sssd-common-1.13.3-58.el6_9.x86_64
sssd-common-pac-1.13.3-58.el6_9.x86_64
sssd-dbus-1.13.3-58.el6_9.x86_64
sssd-ipa-1.13.3-58.el6_9.x86_64
sssd-krb5-1.13.3-58.el6_9.x86_64
sssd-krb5-common-1.13.3-58.el6_9.x86_64
sssd-ldap-1.13.3-58.el6_9.x86_64
sssd-proxy-1.13.3-58.el6_9.x86_64
sssd-tools-1.13.3-58.el6_9.x86_64
Comment 2 Jakub Hrozek 2018-07-17 18:05:55 UTC 
What is the ldb version you have?

Are there any logs you can share or a coredump?
Comment 3 Kapetanakis Giannis 2018-07-18 07:28:04 UTC 
libldb-1.1.25-2.el6_7.x86_64

I've send the logs I had. Nothing import in /var/log/sssd
and no core

I didn't enable debug in sssd since this a production system and wanted to fix it asap.

I've also cleared sssd cache many times but nothing changed.
Comment 4 Jakub Hrozek 2018-07-18 07:55:57 UTC 
By default, no debug logs are generated unless you enable "debug_level", see https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html
Comment 5 M Sanderson 2018-10-14 17:46:14 UTC 
I just did an upgrade of a box to 6.10 + updates as of Oct 14 that was hit with this error as well.  Same versions of sssd (1.13.3-60) with libldb 1.1.25-2.  This is also a production box with a lot of authentications taking place.  We have other systems, which should be configured the same, which don't exhibit the problem.  I believe I have core dumps, but also have abrt report that I will attach.

Jakub, given privacy constraints here, is there a place where a coredump can be provided that isn't public?
Comment 6 M Sanderson 2018-10-14 17:48:30 UTC 
Created attachment 1493740 [details]
abrt report for sssd_pam

abrt report for sssd_pam with sssd_LDAP as the backend.
Comment 7 Jakub Hrozek 2018-10-15 07:05:38 UTC 
(In reply to M Sanderson from comment #5)
> I just did an upgrade of a box to 6.10 + updates as of Oct 14 that was hit
> with this error as well.  Same versions of sssd (1.13.3-60) with libldb
> 1.1.25-2.  This is also a production box with a lot of authentications
> taking place.  We have other systems, which should be configured the same,
> which don't exhibit the problem.  I believe I have core dumps, but also have
> abrt report that I will attach.
> 
> Jakub, given privacy constraints here, is there a place where a coredump can
> be provided that isn't public?

Normally this is done through a support case. I think bugzilla should support private attachments, but I also don't know how that works for a non-RH accounts.

btw given the support state of RHEL-6, currently we don't plan on another update except those backed by support cases, I'm sorry.
Comment 8 Dita 2018-10-29 08:34:36 UTC 
we have the same problem with sssd on RHEL 6.8 did find a solution ?
.
kernel: sssd_pam[1184] general protection ip:3e2d40dc6c sp:7ffc9b599490 error:0 in libldb.so.1.1.25[3e2d4000
sssd[pam]: Starting up
kernel: sssd_pam[5165] general protection ip:3e2d40dc6c sp:7ffc25868690 error:0 in libldb.so.1.1.25[3e2d4000
sssd[pam]: Starting up
kernel: sssd_pam[5468] general protection ip:3e2d40dc6c sp:7ffcaca73710 error:0 in libldb.so.1.1.25[3e2d4000
sssd[pam]: Starting up
kernel: sssd_pam[21804] general protection ip:3e2d40dc6c sp:7ffe81ce1b70 error:0 in libldb.so.1.1.25[3e2d400
sssd: Exiting the SSSD. Could not restart critical service [pam].
sssd[ssh]: Shutting down
Note You need to log in before you can comment on or make changes to this bug.