Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
this description is mostly for the record as the LDAP logs did not correspond to the OOM timing ( to be added )
The IPA LDAP service was terminated as "Out of memory: Killed process 2184890 (ns-slapd)" after over 8 hours in a deployment with 6 RHEL IdM servers all with a CA and capable of PKINIT
ipa2 ( OOM )
|
ipa3 - ipa1 ( OOM ) - ipa5 - ipa6
|
ipa4
1-2K established connections, some time_wait, system had default settings for TCP Q (128), and LDAP fd and timeouts
unknown number of users, groups, hbac, sudo rules ( to be added )
Version-Release number of selected component (if applicable):
RHEL_8.4
389-ds-base-1.4.3.16-13.module+el8.4.0+10307+74bbfb4e.x86_64
ipa-server-4.9.2-3.module+el8.4.0+10412+5ecb5b37.x86_64
redhat-release-8.4-0.6.el8.x86_64
slapi-nis-0.56.6-2.module+el8.4.0+10615+2234cc2c.x86_64
How reproducible:
N/A, but appears in over 8 hours
Steps to Reproduce:
1. N/A, unknown scenario
2.
3.
Actual results:
[Wed Jul 21 02:10:00 2021] Out of memory: Killed process 2184890 (ns-slapd) total-vm:46361340kB, anon-rss:28366956kB, file-rss:0kB, shmem-rss:8kB, UID:389 pgtables:84344kB oom_score_adj:0
Expected results:
yes
Additional info:
- restart ipactl every eight hours
- collected LDAP logs did not correspond to the system OOM events
- till trying to collect 389-ds valigrind and/or jemalloc reports
Description of problem: this description is mostly for the record as the LDAP logs did not correspond to the OOM timing ( to be added ) The IPA LDAP service was terminated as "Out of memory: Killed process 2184890 (ns-slapd)" after over 8 hours in a deployment with 6 RHEL IdM servers all with a CA and capable of PKINIT ipa2 ( OOM ) | ipa3 - ipa1 ( OOM ) - ipa5 - ipa6 | ipa4 1-2K established connections, some time_wait, system had default settings for TCP Q (128), and LDAP fd and timeouts unknown number of users, groups, hbac, sudo rules ( to be added ) Version-Release number of selected component (if applicable): RHEL_8.4 389-ds-base-1.4.3.16-13.module+el8.4.0+10307+74bbfb4e.x86_64 ipa-server-4.9.2-3.module+el8.4.0+10412+5ecb5b37.x86_64 redhat-release-8.4-0.6.el8.x86_64 slapi-nis-0.56.6-2.module+el8.4.0+10615+2234cc2c.x86_64 How reproducible: N/A, but appears in over 8 hours Steps to Reproduce: 1. N/A, unknown scenario 2. 3. Actual results: [Wed Jul 21 02:10:00 2021] Out of memory: Killed process 2184890 (ns-slapd) total-vm:46361340kB, anon-rss:28366956kB, file-rss:0kB, shmem-rss:8kB, UID:389 pgtables:84344kB oom_score_adj:0 Expected results: yes Additional info: - restart ipactl every eight hours - collected LDAP logs did not correspond to the system OOM events - till trying to collect 389-ds valigrind and/or jemalloc reports