Bug 1936891

Summary: SSSD Error Msg Improvement: Bad address
Product: Red Hat Enterprise Linux 8 Reporter: Deepak Das <ddas>
Component: sssdAssignee: Iker Pedrosa <ipedrosa>
Status: CLOSED ERRATA QA Contact: shridhar <sgadekar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.3CC: aborah, atikhono, dlavu, grajaiya, ipedrosa, jhrozek, lslebodn, mzidek, pbrezina, sgoveas, thalman, tscherf
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard: sync-to-jira
Fixed In Version: sssd-2.5.2-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-09 19:47:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Deepak Das 2021-03-09 12:31:12 UTC 
Description of problem:

Reading SSSD logs it's not clear what "Bad address" message. For better analysis of the logs it would be helpful if more detail is available. Sample logs snip is given below.

-----------------------------------------------------------------------------------------------------------------------------------------
(2020-12-18 14:14:23): [be[example.com]] [ad_gpo_process_gpo_done] (0x0040): Unable to get GPO list: [14](Bad address)
-----------------------------------------------------------------------------------------------------------------------------------------
(2020-12-18 11:58:15): [be[example.com]] [be_resolve_server_done] (0x1000): Server resolution failed: [14]: Bad address
(2020-12-18 11:58:15): [be[example.com]] [sdap_id_op_connect_done] (0x0020): Failed to connect, going offline (5 [Input/output error])
(2020-12-18 11:58:15): [be[example.com]] [be_mark_offline] (0x2000): Going offline!
-----------------------------------------------------------------------------------------------------------------------------------------
(2020-12-30 15:37:14): [be[example.com]] [sdap_kinit_done] (0x0100): Could not get TGT: 14 [Bad address]
(2020-12-30 15:37:14): [be[example.com]] [sdap_cli_kinit_done] (0x0400): Cannot get a TGT: ret [1432158227](Authentication Failed)
(2020-12-30 15:37:14): [be[example.com]] [sdap_cli_connect_recv] (0x0040): Unable to establish connection [13]: Permission denied
-----------------------------------------------------------------------------------------------------------------------------------------
Nov 25 10:01:00 eo-rhel-dev1.example.com be[example.com][2298]: Failed to init Kerberos context [Improper format...le]
Nov 25 10:01:00 eo-rhel-dev1.example.com be[example.com][2298]: Failed to read keytab [default]: Bad address
-----------------------------------------------------------------------------------------------------------------------------------------




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

sssd-2.3.0-9.el8.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

"Bad address" message is not clear.

Expected results:

"Bad address" message show be provided with more detail.

Additional info:
Comment 5 Iker Pedrosa 2021-04-08 10:07:23 UTC 
Upstream ticket:
https://github.com/SSSD/sssd/issues/5577
Comment 13 Alexey Tikhonov 2021-07-08 09:38:03 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5600

* `master`
    * 7646ac958da5d0f3997c7655e39f7a2f43d6ec1f - SSSD Log: log_bad_address_msg_mod
Comment 19 shridhar 2021-07-16 13:15:21 UTC 
sanity tests are passing.
Comment 26 errata-xmlrpc 2021-11-09 19:47:10 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