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 884662 - GSS-API (or Kerberos) error while initializing kadmin interface
Summary: GSS-API (or Kerberos) error while initializing kadmin interface
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: krb5
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Robbie Harwood
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-06 14:06 UTC by Jian Li
Modified: 2015-09-09 22:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-09 22:19:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jian Li 2012-12-06 14:06:18 UTC 
Description of problem:
Fetch principal ticket from a krb5 client through `kadmin` tool, this command fails :

( after config krb5.conf )
# kadmin -p kadmin/admin -w redhat -q "ktadd root test0 test1 "  
kadmin: GSS-API (or Kerberos) error while initializing kadmin interface

This fail couldn't be reproduced 100%, all appear in automatic test, and manual test couldn't meet such problem.

And I have fix time with ntp
# ntpdate clock.redhat.com

Version-Release number of selected component (if applicable):
RHEL distro: RHEL6.4-20121203.n.0

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 3 Nalin Dahyabhai 2012-12-10 18:10:14 UTC 
There's not much to work with there.  Log messages from /var/log/kadmind.log on the KDC, output you see at the client when KRB5_TRACE=/dev/stderr, and packet captures might at least give us a place to start.
Comment 4 Nalin Dahyabhai 2012-12-10 19:54:49 UTC 
Also, since you mention that this is occurring during automated testing, I'm wondering if this is a consequence of having insufficient entropy available for kadmind to finish seeing its PRNG and start handling requests in a timely fashion, as we see in bug #874284.  The workaround there is to arrange for kadmind to be started with the undocumented -W flag to have it use /dev/urandom instead.
Comment 5 Jian Li 2012-12-11 02:03:26 UTC 
(In reply to comment #4)
> Also, since you mention that this is occurring during automated testing, I'm
> wondering if this is a consequence of having insufficient entropy available
> for kadmind to finish seeing its PRNG and start handling requests in a
> timely fashion, as we see in bug #874284.  The workaround there is to
> arrange for kadmind to be started with the undocumented -W flag to have it
> use /dev/urandom instead.

Yes, I will check that workaround, I think its the same issue, I would close this bug if it is.  thanks for reply.
Comment 6 RHEL Program Management 2012-12-14 08:15:01 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 8 Robbie Harwood 2015-09-09 22:19:38 UTC 
We could not reproduce, and reporter is unresponsive.
Note You need to log in before you can comment on or make changes to this bug.