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 1417066 - update to 7.3 IPA with otpd bugfixes, tomcat will not finish start, hangs
Summary: update to 7.3 IPA with otpd bugfixes, tomcat will not finish start, hangs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.3
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: RHCS Maintainers
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On: 1412681
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-27 07:25 UTC by Jaroslav Reznik
Modified: 2020-03-11 15:40 UTC (History)
16 users (show)

Fixed In Version: pki-core-10.3.3-17.el7_3
Doc Type: Bug Fix
Doc Text:
Previously, entry Update Sequence Numbers (USN) were parsed as bounded integer values. This caused the server to fail to start in cases when the USN exceeded 2147483647. With this update, USNs are parsed as unbounded BigInteger values, and the server now successfully starts if USNs exceed this value.
Clone Of: 1412681
Environment:
Last Closed: 2017-03-02 17:26:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0389 0 normal SHIPPED_LIVE pki-core bug fix and enhancement update 2017-03-02 22:06:41 UTC

Description Jaroslav Reznik 2017-01-27 07:25:04 UTC 
This bug has been copied from bug #1412681 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 3 Matthew Harmsen 2017-01-28 02:02:19 UTC 
Cherry-picked to DOGTAG_10_3_RHEL_BRANCH from DOGTAG_10_3_BRANCH:
* d37d1cb1a2d33d17f15cbf9565a4bba99050e59a

Cherry-picked to DOGTAG_10_3_RHEL_UNRELEASED_BRANCH from DOGTAG_10_3_BRANCH:
* 643c56d4a1d5632a5aeb81664882a1a55567171c
Comment 7 Fraser Tweedale 2017-02-06 07:08:14 UTC 
Steps to verify:

1. ensure DS entryUSN counter exceeds 2,147,483,647
   (consult a DS SME to see if there is a way to set this directly)

2. make a change to a lightweight authority entry.  This can be done
   via CLI or directly to an entry under ou=authorities,ou=ca,{basedn}.
   For example, you could just change the description.  This step is to make
   sure that the entryUSN exceeds 2,147,483,647

3. restart server.  Check that the server starts properly and
   that a NumberFormatException does not get logged in
   /var/log/pki/pki-tomcat/ca/debug or in
  `journalctl -u pki-tomcatd@pki-tomcat`.
Comment 8 thierry bordaz 2017-02-06 10:40:14 UTC 
Related to the first step to verify.
You should be able to set starting entryUSN using nsslapd-entryusn-import-initval (see http://directory.fedoraproject.org/docs/389ds/design/entry-usn.html#import-and-replica-initialization)

Before doing an import, set this value to something like
2,147,483,000.
Then import a ldif file and checks that 'entryUSN' values of the imported entries is taking into account that new starting point.
You then may be able to rapidly reach MAX_INT
Comment 9 Nikhil Dehadrai 2017-02-07 09:39:23 UTC 
IPA server: 
ipa-server-4.4.0-14.el7_3.6.x86_64

PKI packages:
pki-server-10.3.3-17.el7_3.noarch
pki-ca-10.3.3-17.el7_3.noarch

Tested the bug on the basis of following Observations:
1. Verified that when entryUSN has higher denomination (e.g: in the range of 2147485000)  within directory server, then ipa server service can be restarted successfully and it does not hang.

2. No error messages are observed for "NumberFormatException" within /var/log/pki/pki-tomcat/ca/debug or in `journalctl -u pki-tomcatd@pki-tomcat`.

Thus on the basis of above observations marking the status of bug to "VERIFIED".
Comment 11 Fraser Tweedale 2017-02-19 23:00:01 UTC 
Added doc text.
Comment 13 errata-xmlrpc 2017-03-02 17:26:56 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-2017-0389.html
Note You need to log in before you can comment on or make changes to this bug.