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 2100691 - ipa-healthcheck command display messages as "Unhandler rdtype 256"
Summary: ipa-healthcheck command display messages as "Unhandler rdtype 256"
Keywords:
Status: CLOSED DUPLICATE of bug 2037847
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa-healthcheck
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-24 02:13 UTC by Vinay Mishra
Modified: 2022-08-23 14:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-24 12:22:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-8420 0 None None None 2022-06-24 02:21:02 UTC
Red Hat Issue Tracker RHELPLAN-126189 0 None None None 2022-06-24 02:21:07 UTC

Description Vinay Mishra 2022-06-24 02:13:00 UTC
Description of problem:

Getting the message as below in ipa-healthcheck

[root@awsidml03 ~]# ipa-healthcheck

Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
Unhandler rdtype 256
...
...

Version-Release number of selected component (if applicable):
ipa-healthcheck-0.7-10.module+el8.6.0+14292+18b36d36.noarch

Expected results:
Invalid format in the configuration file should be detected or the user should be warned. 

Additional info:
https://github.com/freeipa/freeipa-healthcheck/commit/43d55b2d0fafafe9e128a832148dbec55f6ad2ac
https://github.com/freeipa/freeipa-healthcheck/issues/222

Comment 1 Rob Crittenden 2022-06-24 12:22:00 UTC
These messages are related to the DNS URI entries that IPA supports. This version of healthcheck doesn't understand them and emits a message for each one. It does not affect the output of healthcheck itself. This has absolutely nothing to do with the configuration file.

*** This bug has been marked as a duplicate of bug 2037847 ***


Note You need to log in before you can comment on or make changes to this bug.