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
Per 389-ds-base ticket triage,
looks bad, prio depends on importance of use case
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1206311
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1206316
Most likely a PAM issue.
Set to FUTURE for the record.
Metadata Update from @nhosoi: - Issue set to the milestone: FUTURE
@mreynolds Is this issue still relevant? or can we close it?
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to new - Issue close_status updated to: None
It needs a follow up investigation. There was a significant leak, but it appeared to be in the PAM module, not DS.
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1023
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.