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 1949149 - [RFE] Poor man's backtrace
Summary: [RFE] Poor man's backtrace
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Alexey Tikhonov
QA Contact: Dan Lavu
Josip Vilicic
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-13 14:38 UTC by Tomas Halman
Modified: 2022-05-27 12:43 UTC (History)
12 users (show)

Fixed In Version: sssd-2.5.0-1.el8
Doc Type: Enhancement
Doc Text:
.SSSD now logs backtraces by default With this enhancement, SSSD now stores detailed debug logs in an in-memory buffer and appends them to log files when a failure occurs. By default, the following error levels trigger a backtrace: * Level 0: fatal failures * Level 1: critical failures * Level 2: serious failures You can modify this behavior for each SSSD process by setting the `debug_level` option in the corresponding section of the `sssd.conf` configuration file: * If you set the debugging level to 0, only level 0 events trigger a backtrace. * If you set the debugging level to 1, levels 0 and 1 trigger a backtrace. * If you set the debugging level to 2 or higher, events at level 0 through 2 trigger a backtrace. You can disable this feature per SSSD process by setting the `debug_backtrace_enabled` option to `false` in the corresponding section of `sssd.conf`: ---- [sssd] debug_backtrace_enabled = true debug_level=0 ... [nss] debug_backtrace_enabled = false ... [domain/idm.example.com] debug_backtrace_enabled = true debug_level=2 ... ... ----
Clone Of:
Environment:
Last Closed: 2021-11-09 19:47:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd pull 5585 0 None open Poor man's backtrace. 2021-04-14 13:22:52 UTC
Red Hat Knowledge Base (Solution) 6591751 0 None None None 2022-05-09 07:12:51 UTC
Red Hat Product Errata RHBA-2021:4435 0 None None None 2021-11-09 19:47:44 UTC

Description Tomas Halman 2021-04-13 14:38:32 UTC 
Problem statement: when hard-to-reproduce issue occurs, we usually do not have any means to investigate the case, since default log level is rather low and doesn't have much information. And since issue is "hard-to-reproduce" it can take long time to gather logs with high level enabled (or might be impractical at all in high load environments).

Solution: in case SSSD is run with debug_level < full, log messages to a ring buffer in memory and flush the buffer to a log file on error (up to level 2).

Limitation: this will be only supported in case logger == files.
Comment 2 Alexey Tikhonov 2021-05-05 15:19:32 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5585

* `master`
    * 80963d683a0c7fd146fcfd21770990043b9d8449 - SBUS: changed debug level in sbus_issue_request_done() to avoid backtrace dump in case of 'ERR_MISSING_DP_TARGET'
    * 6fb987b5cf64675a42dfaaccc877ed867867bd73 - SERVER: decrease log level in `orderly_shutdown()` to avoid backtrace in this case.
    * f693078fe44ff0ae2f2c53180afaf532cfb92a1f - CERTMAP: removed "sss_certmap initialized" debug
    * 97f046e72bdec06356a5ed5295f283d0529eb440 - DEBUG: log IMPORTANT_INFO if any bit >= OP_FAILURE is on
    * 0aaf61c66b6f2758f89152f946360e00755a9846 - DEBUG: makes debug backtrace switchable
    * 6b78b7aa802529fc885877f326650fb7e6527607 - CACHE_REQ: fixed REVERSE_INULL warning
    * e3426ebeb52a821495ea5d34fdc408fe23df7416 - PAM: fixes a couple of covscan issues
    * 59ba14e5a70ed0b9253c7a881d664fcd28c337e7 - DEBUG: poor man's backtrace
    * f66b5aedab31f22642a50df8f7f458af8d3d7391 - DEBUG: got rid of most explicit DEBUG_IS_SET checks as a preliminary step for "logs backtrace" feature
Comment 16 errata-xmlrpc 2021-11-09 19:47:29 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-2021:4435
Note You need to log in before you can comment on or make changes to this bug.