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 1268027 - ipa-dnskeysync-replica crash with backtrace - LimitsExceeded: limits exceeded for this query
Summary: ipa-dnskeysync-replica crash with backtrace - LimitsExceeded: limits exceeded...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
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:
Environment:
Last Closed: 2016-11-04 05:47:02 UTC
Target Upstream Version:
Embargoed:

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


Links
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
event_log:      
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=10.16.36.29 --hostname=ibm-dx360m4-01.testrelm.test -r TESTRELM.TEST -n testrelm.test -p xxxxxxxx -a xxxxxxxx --ip-address=10.16.67.102 -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=10.16.36.29 --hostname=ibm-dx360m4-01.testrelm.test -r TESTRELM.TEST -n testrelm.test -p xxxxxxxx -a xxxxxxxx --ip-address=10.16.67.102 -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:
https://fedorahosted.org/freeipa/ticket/5342
Comment 7 Martin Bašti 2015-10-07 12:59:10 UTC 
Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/0b797da56095801bfa80653465c04bae0809df8d
ipa-4-2:
https://fedorahosted.org/freeipa/changeset/5841d495f081c635394cda09abe36be020d32d84
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::
ipa-server-4.4.0-11.el7.x86_64

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.

https://rhn.redhat.com/errata/RHBA-2016-2404.html
Note You need to log in before you can comment on or make changes to this bug.