Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

backtrace in responder for error "Could not get account info" #5968

Closed
sgoveas opened this issue Jan 24, 2022 · 1 comment
Closed

backtrace in responder for error "Could not get account info" #5968

sgoveas opened this issue Jan 24, 2022 · 1 comment
Assignees
Labels
Closed: Fixed Issue was closed as fixed.

Comments

@sgoveas
Copy link
Contributor

sgoveas commented Jan 24, 2022

#5788
version sssd-2.6.1-1.el9.x86_64

2022-01-20  4:06:31): [nss] [cache_req_common_process_dp_reply] (0x0040): CR #0: Could not get account info [1432158212]: SSSD is offline
********************** PREVIOUS MESSAGE WAS TRIGGERED BY THE FOLLOWING BACKTRACE:
alexey-tikhonov added a commit to alexey-tikhonov/sssd that referenced this issue Jan 24, 2022
Don't trigger backtrace in responder log in case of backend fail.
(an addition to ca8b655)

Resolves: SSSD#5968
@pbrezina
Copy link
Member

pbrezina commented Feb 1, 2022

Pushed PR: #5970

  • master
    • 7f6c275 - debug: suppress backtrace for backend errors

@pbrezina pbrezina added the Closed: Fixed Issue was closed as fixed. label Feb 1, 2022
shridhargadekar pushed a commit to shridhargadekar/sssd that referenced this issue Apr 1, 2022
Don't trigger backtrace in responder log in case of backend fail.
(an addition to ca8b655)

Resolves: SSSD#5968

Reviewed-by: Iker Pedrosa <ipedrosa@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants