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.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47687
When using PAM Passthru plugin, and simply issuing a search in a loop will generate steady significant memory growth:
ldapsearch -D "uid=t001,dc=example,dc=com" -w pamPassword -xLLL -b "dc=example,dc=com" uid=t001 dn
DATE - [TIME] ------- PID VSZ RSS PCPU
01/31-[12:24:10] ------- 21603 2739424 336084 17.7 growth: 36852 k
...
01/31-[13:10:12] ------- 21603 3023616 1210036 33.5 growth: 65536 k
...
01/31-[13:39:13] ------- 21603 3443240 1617812 37.2 growth: 0 k
Total growth, over 1h 15m, of looping the same search: 703816 k
I don't see any of this growth when PAM Passthru is disabled:
DATE - [TIME] ------- PID VSZ RSS PCPU
01/31-[13:43:25] ------- 10684 2679656 31860 15.2 growth: 0 k
...
01/31-[13:56:26] ------- 10684 2679656 31892 20.0 growth: 0 k
I believe that this is a leak in one of the PAM modules, which we have encountered before. Specifically, we saw a leak in the fprintd module, which they declined to fix since it is not usually used in a long-running daemon process like ns-slapd. The leak can be avoided by using something like the password-auth PAM stack instead of system-auth (which includes fprintd).