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 2021196 - Make backtrace less "chatty" (avoid duplicate backtraces)
Summary: Make backtrace less "chatty" (avoid duplicate backtraces)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.5
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Alexey Tikhonov
QA Contact: Steeve Goveas
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks: 2021499
TreeView+ depends on / blocked
 
Reported: 2021-11-08 14:38 UTC by Tomas Halman
Modified: 2022-05-10 16:47 UTC (History)
8 users (show)

Fixed In Version: sssd-2.6.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2021499 (view as bug list)
Environment:
Last Closed: 2022-05-10 15:26:44 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-101989 0 None None None 2021-11-08 14:40:41 UTC
Red Hat Product Errata RHBA-2022:2070 0 None None None 2022-05-10 15:27:03 UTC

Description Tomas Halman 2021-11-08 14:38:59 UTC 
In case the same error(s) is repeated again and again repeating the same backtrace doesn't add much value. In this case let's add just a note.
Comment 1 Alexey Tikhonov 2021-11-08 15:56:51 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5862

* `master`
    * bb8da4303851642318b626aad507ab7c39f6a80d - DEBUG: avoid backtrace dups.
Comment 4 Steeve Goveas 2021-12-02 18:21:37 UTC 
[root@ci-vm-10-0-151-51 ~]# rpm -q sssd
sssd-2.5.2-2.el8_5.1.x86_64

[root@ci-vm-10-0-151-51 ~]# cat /etc/sssd/sssd.conf
[sssd]
config_file_version = 2
services = nss, pam
domains = example1

[domain/example1]
ldap_search_base = dc=example,dc=test
id_provider = ldap
auth_provider = ldap
ldap_user_home_directory = /home/%u
ldap_uri = ldaps://typo.ci-vm-10-0-149-164.hosted.upshift.rdu2.redhat.com
ldap_tls_cacert = /etc/openldap/cacerts/cacert.pem
use_fully_qualified_names = True
debug_level = 9

[root@ci-vm-10-0-151-51 ~]# systemctl start sssd

[root@ci-vm-10-0-151-51 ~]# getent passwd test@example1
[root@ci-vm-10-0-151-51 ~]# getent passwd test@example1
[root@ci-vm-10-0-151-51 ~]# getent passwd test@example1


[root@ci-vm-10-0-151-51 ~]# grep BACKTRACE /var/log/sssd/sssd_nss.log 
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
********************** BACKTRACE DUMP ENDS HERE *********************************
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
********************** BACKTRACE DUMP ENDS HERE *********************************
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
********************** BACKTRACE DUMP ENDS HERE *********************************
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
********************** BACKTRACE DUMP ENDS HERE *********************************
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
********************** BACKTRACE DUMP ENDS HERE *********************************
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
********************** BACKTRACE DUMP ENDS HERE *********************************
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
********************** BACKTRACE DUMP ENDS HERE *********************************
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
********************** BACKTRACE DUMP ENDS HERE *********************************
[root@ci-vm-10-0-151-51 ~]#



Verified with
[root@ci-vm-10-0-151-51 ~]# rpm -q sssd
sssd-2.6.1-1.el8.x86_64

[root@ci-vm-10-0-151-51 ~]# getent passwd test@example1
[root@ci-vm-10-0-151-51 ~]# getent passwd test@example1
[root@ci-vm-10-0-151-51 ~]# getent passwd test@example1

[root@ci-vm-10-0-151-51 ~]# grep BACKTRACE /var/log/sssd/sssd_nss.log 
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
********************** BACKTRACE DUMP ENDS HERE *********************************

[root@ci-vm-10-0-151-51 ~]# grep skipping /var/log/sssd/sssd_nss.log 
   *  ... skipping repetitive backtrace ...
   *  ... skipping repetitive backtrace ...
   *  ... skipping repetitive backtrace ...
   *  ... skipping repetitive backtrace ...
[root@ci-vm-10-0-151-51 ~]#
Comment 10 errata-xmlrpc 2022-05-10 15:26:44 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-2022:2070
Note You need to log in before you can comment on or make changes to this bug.