You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1917444
The text was updated successfully, but these errors were encountered: