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

SSSD Error Msg Improvement: Server resolution failed: [2]: No such file or directory #5614

Closed
ikerexxe opened this issue Apr 29, 2021 · 1 comment
Assignees
Labels
Closed: Fixed Issue was closed as fixed.

Comments

@ikerexxe
Copy link
Contributor

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1917444

Description of problem:

SSSD debug log snip following message is observed in support case 02835160
following.

----------------------------------------------------------------------------
(2020-12-31 11:19:39): [be[example.com]] [fo_resolve_service_send] (0x0100):
Trying to resolve service 'AD'
(2020-12-31 11:19:39): [be[example.com]] [get_server_status] (0x1000): Status
of server 'ad-dc3.example.com' is 'name resolved'
(2020-12-31 11:19:39): [be[example.com]] [fo_resolve_service_activate_timeout]
(0x2000): Resolve timeout set to 6 seconds
(2020-12-31 11:19:39): [be[example.com]] [resolve_srv_send] (0x0200): The
status of SRV lookup is resolved
(2020-12-31 11:19:39): [be[example.com]] [get_server_status] (0x1000): Status
of server 'ad-dc3.example.com' is 'name resolved'
(2020-12-31 11:19:39): [be[example.com]] [be_resolve_server_process] (0x0040):
The fail over cycled through all available servers
(2020-12-31 11:19:39): [be[example.com]] [be_resolve_server_done] (0x1000):
Server resolution failed: [2]: No such file or directory
(2020-12-31 11:19:39): [be[example.com]] [be_mark_dom_offline] (0x1000):
Marking back end offline
(2020-12-31 11:19:39): [be[example.com]] [be_mark_offline] (0x2000): Going
offline!
----------------------------------------------------------------------------

As per above error message, when "Server resolution failed" is observed it also
adds  "No such file or directory" which is not clear as to which file or
directory SSSD is referring to if any.

Version-Release number of selected component (if applicable):

sssd-2.3.0-9.el8.x86_64

How reproducible:

Always.

Actual results:

Message "No such file or directory" is confusing.

Expected results:

Message "No such file or directory" should not be displayed if the message is
false positive.

Additional info:

The object of this bugzilla is to request improvement of SSSD debug messages to
make it more customer friendly.
@ikerexxe ikerexxe self-assigned this Apr 29, 2021
DDDas7 added a commit to DDDas7/sssd that referenced this issue May 5, 2021
Replacing no such file or directory error code with alternate message

Resolves: SSSD#5614
DDDas7 added a commit to DDDas7/sssd that referenced this issue May 5, 2021
Replacing no such file or directory error code with alternate message

Resolves: SSSD#5614
DDDas7 added a commit to DDDas7/sssd that referenced this issue May 26, 2021
Replacing no such file or directory error code with alternate message

Resolves: SSSD#5614
DDDas7 added a commit to DDDas7/sssd that referenced this issue May 27, 2021
Replacing no such file or directory error code with alternate message

Resolves: SSSD#5614
@pbrezina
Copy link
Member

Pushed PR: #5622

  • master
    • 9c06088 - SSSD Log: no_such_file_or_directory_modification

@pbrezina pbrezina added the Closed: Fixed Issue was closed as fixed. label May 31, 2021
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.

2 participants