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 1936891 - SSSD Error Msg Improvement: Bad address
Summary: SSSD Error Msg Improvement: Bad address
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: shridhar
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-09 12:31 UTC by Deepak Das
Modified: 2024-03-25 18:13 UTC (History)
12 users (show)

Fixed In Version: sssd-2.5.2-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 19:47:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5577 0 None open SSSD Error Msg Improvement: Bad address 2021-04-30 09:51:46 UTC
Red Hat Product Errata RHBA-2021:4435 0 None None None 2021-11-09 19:47:40 UTC

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
Note You need to log in before you can comment on or make changes to this bug.