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 2149241 - [sssd] SSSD enters failed state after heavy load in the system
Summary: [sssd] SSSD enters failed state after heavy load in the system
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.6
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: shridhar
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks: 2219351 2219352
TreeView+ depends on / blocked
 
Reported: 2022-11-29 10:19 UTC by Aleksandr Sharov
Modified: 2024-08-09 08:46 UTC (History)
12 users (show)

Fixed In Version: sssd-2.9.1-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2219351 2219352 (view as bug list)
Environment:
Last Closed: 2023-11-14 15:49:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)
debug sssd logs (16.82 MB, application/gzip)
2022-11-29 10:19 UTC, Aleksandr Sharov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 6803 0 None open [sssd] SSSD enters failed state after heavy load in the system 2023-06-30 08:19:26 UTC
Github SSSD sssd pull 6804 0 None open sbus: arm watchdog for sbus_connect_init_send() 2023-06-30 09:54:25 UTC
Red Hat Issue Tracker RHELPLAN-140762 0 None None None 2022-11-29 10:27:48 UTC
Red Hat Issue Tracker SSSD-6386 0 None None None 2023-07-03 13:35:57 UTC
Red Hat Knowledge Base (Solution) 7049056 0 None None None 2023-12-13 13:25:32 UTC
Red Hat Product Errata RHBA-2023:7127 0 None None None 2023-11-14 15:50:22 UTC

Description Aleksandr Sharov 2022-11-29 10:19:52 UTC
Created attachment 1928235 [details]
debug sssd logs

Description of problem:
After severe load on the system, including oom state, sssd's dbus looses ability to talk with it's data providers:

   *  ... skipping repetitive backtrace ...
(2022-11-26 12:18:08): [be[default]] [dp_client_handshake_timeout] (0x0040): Client [sssd.pam] timed out before identification [0x55cc9111b620]!
   *  ... skipping repetitive backtrace ...
(2022-11-26 12:18:08): [be[default]] [dp_client_handshake_timeout] (0x0040): Client [sssd.nss] timed out before identification [0x55cc91118770]!

This state remains until the sssd service is restarted.


Version-Release number of selected component (if applicable):
RHEL 8.6, sssd-2.6.2-4.el8_6.x86_64

How reproducible:
Couldn't reproduce the state in the lab. In client's environment, it's happening every 24 hours when custom cron script is running.

Steps to Reproduce:
1.
2.
3.

Actual results:

SSSD state is not recovered automatically

Expected results:

SSSD continues to work as expected after the system is out of heavy load and/or OOM.

Additional info:

Debug logs attached (nss trimmed to last 2000 lines, full logs in case). Issue happened around 5:39-5:41 AM , difficult to distinguish better because system appears to be hang at the time.

Additional data and sosreport are in the attached case.

Comment 50 Alexey Tikhonov 2023-06-30 09:51:21 UTC
Upstream PR: https://github.com/SSSD/sssd/pull/6804

Comment 53 Alexey Tikhonov 2023-07-04 13:39:07 UTC
Pushed PR: https://github.com/SSSD/sssd/pull/6804

* `master`
    * cca9361d92501e0be34d264d370fe897a0c970af - sbus: arm watchdog for sbus_connect_init_send()
    * 75f2b35ad3b9256de905d05c5108400d35688554 - watchdog: add arm_watchdog() and disarm_watchdog() calls
* `sssd-2-8`
    * 55564defec8fdbb4d9df6b0124a8b18b31743230 - sbus: arm watchdog for sbus_connect_init_send()
    * 2cd5a6a2c8fd1826177d6bb51e7d4f4ad368bcfb - watchdog: add arm_watchdog() and disarm_watchdog() calls
* `sssd-2-9`
    * 27987c791bc452f53696a3a33f0d607ab040e78d - sbus: arm watchdog for sbus_connect_init_send()
    * f16e570838d1c6cd30b5883f364b0f437c314b1f - watchdog: add arm_watchdog() and disarm_watchdog() calls

Comment 61 errata-xmlrpc 2023-11-14 15:49:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (sssd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:7127


Note You need to log in before you can comment on or make changes to this bug.