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.

Description of problem:
kadmin takes approx 2mins to start

This is probably how kadmin has been behaving since many past releases I guess. But I am logging this bug to know if this is the expected behaviour.

Version-Release number of selected component (if applicable):
krb5-server-1.10.3-30.el6

How reproducible:
Always

Steps to Reproduce:
1. # service kadmin start
Starting Kerberos 5 Admin Server: [  OK  ]

The above command returns immediately and it seems kadmind has started.

2. Look at the kadmin.log

</snip>
Aug 06 06:18:06 krbserver.example.com kadmind[11676](info): set up 7 sockets
Aug 06 06:18:06 krbserver.example.com kadmind[16236](info): Seeding random number generator
Aug 06 06:19:57 krbserver.example.com kadmind[16236](info): starting
<snip>


Actual results:
From kadmin.log , kadmin actually starts after 111 seconds.

Expected results:


Additional info:

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