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 1917444 - SSSD Error Msg Improvement: Server resolution failed: [2]: No such file or directory
Summary: SSSD Error Msg Improvement: Server resolution failed: [2]: No such file or di...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Iker Pedrosa
QA Contact: Anuj Borah
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-18 13:55 UTC by Deepak Das
Modified: 2024-03-25 17:53 UTC (History)
11 users (show)

Fixed In Version: sssd-2.5.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 19:46:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4435 0 None None None 2021-11-09 19:46:50 UTC

Description Deepak Das 2021-01-18 13:55:19 UTC
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.

Comment 7 Iker Pedrosa 2021-04-29 15:33:15 UTC
Upstream ticket:
https://github.com/SSSD/sssd/issues/5614

Comment 8 Alexey Tikhonov 2021-05-31 13:16:53 UTC
Pushed PR: https://github.com/SSSD/sssd/pull/5622

* `master`
    * 9c06088de65630f7407d505e015643fa656803d9 - SSSD Log: no_such_file_or_directory_modification

Comment 23 errata-xmlrpc 2021-11-09 19:46:34 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.