Bug 1268027 - ipa-dnskeysync-replica crash with backtrace - LimitsExceeded: limits exceeded for this query
Summary: ipa-dnskeysync-replica crash with backtrace - LimitsExceeded: limits exceeded...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
Depends On:
TreeView+ depends on / blocked
Reported: 2015-10-01 15:31 UTC by Kaleem
Modified: 2016-11-04 05:47 UTC (History)
6 users (show)

Fixed In Version: ipa-4.4.0-0.el7.1.alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-11-04 05:47:02 UTC
Target Upstream Version:

Attachments (Terms of Use)
crash detailed info (2.99 KB, text/plain)
2015-10-01 15:31 UTC, Kaleem
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2404 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2016-11-03 13:56:18 UTC

Description Kaleem 2015-10-01 15:31:20 UTC
Created attachment 1079191 [details]
crash detailed info

Description of problem:
Observed this crash while executing B&R automated regression run.

Crash shows time that it occured at 08:45:45 AM but when i looked into the beaker logs, i found that at that time ipa installation was in progress. Point to note is that it was in second test case. In First test case, i did install/full backup/uninstall/install/full restore/uninstall. 

snip from crash:
time:           Thu 01 Oct 2015 08:54:45 AM EDT
cmdline:        /usr/bin/python2 /usr/libexec/ipa/ipa-dnskeysync-replica
uid:            993 (ods)
abrt_version:   2.1.11
dso_list:       ipa-python-4.2.0-12.el7.x86_64
executable:     /usr/libexec/ipa/ipa-dnskeysync-replica
hostname:       ibm-dx360m4-01.testrelm.test
kernel:         3.10.0-320.el7.x86_64
last_occurrence: 1443704085
pid:            16985
pkg_arch:       x86_64
pkg_epoch:      0
pkg_name:       ipa-server
pkg_release:    12.el7
pkg_version:    4.2.0
runlevel:       N 3
username:       ods

beaker log snip with timestamp:

:: [ 08:49:57 ] ::   ipa-server-4.2.0-12.el7.x86_64
:: [  BEGIN   ] :: Running ' /usr/sbin/ipa-server-install --setup-dns --forwarder= --hostname=ibm-dx360m4-01.testrelm.test -r TESTRELM.TEST -n testrelm.test -p xxxxxxxx -a xxxxxxxx --ip-address= -U'
Be sure to back up the CA certificates stored in /root/cacert.p12
These files are required to create replicas. The password for these
files is the Directory Manager password
:: [   PASS   ] :: Command ' /usr/sbin/ipa-server-install --setup-dns --forwarder= --hostname=ibm-dx360m4-01.testrelm.test -r TESTRELM.TEST -n testrelm.test -p xxxxxxxx -a xxxxxxxx --ip-address= -U' (Expected 0, got 0)
:: [ 08:56:29 ] :: Check ldap_sasl_authid is not added to sssd.conf
:: [ 08:56:30 ] :: Verifying BZ 878420

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

How reproducible:

Steps to Reproduce:
1.See description section

Actual results:
Crash seen

Expected results:
No crash

Additional info:
Please find the attached crash detailed info

Comment 2 Petr Vobornik 2015-10-05 10:38:12 UTC
Kaleem, could you attach a DS error and access log from the time of the crash?

Comment 3 Petr Spacek 2015-10-06 07:47:09 UTC
This is most likely caused by weirness in IPA ldap2 class - DS did not respond in 2 second limit for configuration refresh and that caused this error.

This issue will manifest itself randomly. To workaround that we can easily change DNSSEC daemons to use different code from IPA framework to avoid the problematic query from withing ldap2 class.

Patch was sent to the ipa-devel list.

Comment 4 Martin Bašti 2015-10-06 07:50:14 UTC
Upstream ticket:

Comment 8 Mike McCune 2016-03-28 22:43:24 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 10 Abhijeet Kasurde 2016-09-23 09:30:03 UTC
Verified using IPA version::

Done SanityOnly using automation.

Comment 11 Kaleem 2016-09-23 10:32:04 UTC
Crash no more seen with automated test suite.

Comment 13 errata-xmlrpc 2016-11-04 05:47:02 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.


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