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 1936902 - SSSD Error Msg Improvement: Invalid argument
Summary: SSSD Error Msg Improvement: Invalid argument
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-03-09 13:01 UTC by Deepak Das
Modified: 2024-03-25 18:13 UTC (History)
11 users (show)

Fixed In Version: sssd-2.5.1-2.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:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5578 0 None open SSSD Error Msg Improvement: Invalid argument 2021-06-02 18:19:43 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 13:01:39 UTC 
Description of problem:

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

----------------------------------------------------------------------------------------------------------------------------------------
(2020-12-22  0:03:13): [be[example.com]] [be_nsupdate_done] (0x0040): nsupdate child execution failed [1432158240]: Dynamic DNS update failed
(2020-12-22  0:03:13): [be[example.com]] [ad_dyndns_sdap_update_done] (0x0040): Dynamic DNS update failed [1432158240]: Dynamic DNS update failed
(2020-12-22  0:03:13): [be[example.com]] [be_ptask_done] (0x0040): Task [Dyndns update]: failed with [1432158240]: Dynamic DNS update failed
(2020-12-21 13:03:31): [be[example.com]] [gpo_cse_done] (0x0020): ad_gpo_parse_gpo_child_response failed: [22][Invalid argument]
----------------------------------------------------------------------------------------------------------------------------------------
(2020-12-10 13:39:05): [be[example.com]] [sdap_idmap_add_domain] (0x1000): Adding domain [S-1-5-21-560720425-791098809-1427889808] as slice [400]
(2020-12-10 13:39:05): [be[example.com]] [sdap_idmap_add_domain] (0x0020): BUG: Range maximum exceeds the global maximum: 2870330815 > 2000200000
(2020-12-10 13:39:05): [be[example.com]] [sdap_idmap_init] (0x0020): Could not add domain [uhs.uh.edu][S-1-5-21-560720425-791098809-1427889808][400] to ID map: [Invalid argument]
(2020-12-10 13:39:05): [be[example.com]] [ad_init_misc] (0x0010): Could not initialize ID mapping. In case ID mapping properties changed on the server, please remove the SSSD database
(2020-12-10 13:39:05): [be[example.com]] [sssm_ad_init] (0x0020): Unable to init AD module [22]: Invalid argument
(2020-12-10 13:39:05): [be[example.com]] [dp_module_run_constructor] (0x0010): Module [ad] constructor failed [22]: Invalid argument
(2020-12-10 13:39:05): [be[example.com]] [be_ptask_destructor] (0x0400): Terminating periodic task [Dyndns update]
(2020-12-10 13:39:05): [be[example.com]] [dp_load_module] (0x0020): Unable to create DP module.
(2020-12-10 13:39:05): [be[example.com]] [dp_target_init] (0x0010): Unable to load module ad
(2020-12-10 13:39:05): [be[example.com]] [dp_load_targets] (0x0020): Unable to load target [id] [80]: Accessing a corrupted shared library.
(2020-12-10 13:39:05): [be[example.com]] [dp_init_done] (0x0020): Unable to initialize DP targets [1432158209]: Internal Error
----------------------------------------------------------------------------------------------------------------------------------------


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:

"Invalid arguments" message is not clear.

Expected results:

"Invalid arguments" message show be provided with more detail.

Additional info:
Comment 7 Iker Pedrosa 2021-04-08 10:07:46 UTC 
Upstream ticket:
https://github.com/SSSD/sssd/issues/5578
Comment 17 Alexey Tikhonov 2021-06-21 14:41:15 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5668

* `master`
    * 89a40e77a1477a3957f4ddc47890eaecbc4d5c7c - SSSD Log: invalid_argument msg mod
Comment 22 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.