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 1254262 - ipa-dnskeysync-replica crash cannot contact kdc
Summary: ipa-dnskeysync-replica crash cannot contact kdc
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 14:06 UTC by Scott Poore
Modified: 2015-11-19 12:05 UTC (History)
4 users (show)

Fixed In Version: ipa-4.2.0-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 12:05:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2362 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2015-11-19 10:40:46 UTC

Description Scott Poore 2015-08-17 14:06:07 UTC
Description of problem:

time:           Sun 16 Aug 2015 10:36:09 PM EDT
cmdline:        /usr/bin/python2 /usr/libexec/ipa/ipa-dnskeysync-replica
uid:            992 (ods)
abrt_version:   2.1.11
dso_list:       ipa-python-4.2.0-4.el7.x86_64
event_log:      
executable:     /usr/libexec/ipa/ipa-dnskeysync-replica
hostname:       dell-pe800-01.spoore3.test
kernel:         3.10.0-304.el7.x86_64
last_occurrence: 1439778969
pid:            18724
pkg_arch:       x86_64
pkg_epoch:      0
pkg_name:       ipa-server
pkg_release:    4.el7
pkg_version:    4.2.0
runlevel:       N 3
username:       ods

backtrace:
:ipautil.py:1231:kinit_keytab:Krb5Error: (-1765328228, 'Cannot contact any KDC for requested realm')
:
:Traceback (most recent call last):
:  File "/usr/libexec/ipa/ipa-dnskeysync-replica", line 144, in <module>
:    ipautil.kinit_keytab(PRINCIPAL, paths.IPA_DNSKEYSYNCD_KEYTAB, ccache_filename)
:  File "/usr/lib/python2.7/site-packages/ipapython/ipautil.py", line 1231, in kinit_keytab
:    ccache.init_creds_keytab(keytab=ktab, principal=princ)
:Krb5Error: (-1765328228, 'Cannot contact any KDC for requested realm')
:
:Local variables in innermost frame:
:attempts: 1
:e: Krb5Error(-1765328228, 'Cannot contact any KDC for requested realm')
:config: None
:old_config: None
rinc: <krb5.Principal instance at 0x428c290: ipa-dnskeysyncd/dell-pe800-01.spoore3.test>
:krbcontext: <krbV.Context instance at 0x5da6098>
:keytab: '/etc/ipa/dnssec/ipa-dnskeysyncd.keytab'
:ccache: <krbV.CCache instance at 0x428c3f8>
:ccache_name: '/tmp/ipa-dnskeysync-replica.ccache'
:attempt: 1
:errors_to_retry: set([-1765328228, -1765328355])
:ktab: <krbV.Keytab instance at 0x428cb00>
rincipal: 'ipa-dnskeysyncd/dell-pe800-01.spoore3.test'

environ:
:LANG=en_US.UTF-8
:SHELL=/sbin/nologin
:KRB5CCNAME=/tmp/ipa-dnskeysyncd.ccache
:LOGNAME=ods
:USER=ods
:SOFTHSM2_CONF=/etc/ipa/dnssec/softhsm2.conf
:HOME=//var/lib/softhsm
ATH=/bin:/sbin:/usr/kerberos/bin:/usr/kerberos/sbin:/usr/bin:/usr/sbin

machineid:
:systemd=5aa1af4015c6414b8e24c340c714face
:sosreport_uploader-dmidecode=7a582b64bcf1d6ce98c628748d4d7d7c720fb9731a08045d3b786aed9672d3ea

os_info:
:NAME="Red Hat Enterprise Linux Server"
:VERSION="7.2 (Maipo)"
:ID="rhel"
:ID_LIKE="fedora"
:VERSION_ID="7.2"
RETTY_NAME="Red Hat Enterprise Linux Server 7.2 Beta (Maipo)"
:ANSI_COLOR="0;31"
:CPE_NAME="cpe:/o:redhat:enterprise_linux:7.2:beta:server"
:HOME_URL="https://www.redhat.com/"
:BUG_REPORT_URL="https://bugzilla.redhat.com/"
:
:REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
:REDHAT_BUGZILLA_PRODUCT_VERSION=7.2
:REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
:REDHAT_SUPPORT_PRODUCT_VERSION="7.2 Beta"


Version-Release number of selected component (if applicable):
ipa-server-4.2.0-4.el7.x86_64

How reproducible:
unknown

Steps to Reproduce:
1.  ipa-server-install
2.
3.

Actual results:
server install seems to work but, afterwards I see this crash


Expected results:
no crash

Additional info:

Comment 4 Petr Vobornik 2015-08-17 15:25:43 UTC
in the message log we can see that the service get restarted and works ok - not a severe issue. 

In any case, it should not traceback.

Comment 5 Petr Vobornik 2015-08-17 15:26:45 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5229

Comment 8 Scott Poore 2015-09-02 19:37:07 UTC
Verified.

Version ::

4.2.0-5 thru 4.2.0-7

Results ::

We haven't seen this crash since the update.  Verifying Sanity only.

Comment 9 errata-xmlrpc 2015-11-19 12:05:34 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, 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://rhn.redhat.com/errata/RHBA-2015-2362.html


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