Hi, First a bit of context. CentOS 7, FreeIPA 389-ds-base-snmp-1.3.9.1-13.el7_7.x86_64 389-ds-base-libs-1.3.9.1-13.el7_7.x86_64 389-ds-base-1.3.9.1-13.el7_7.x86_64 A long time ago I was experiencing a deadlock during retro changelog cleanup and I was advised to disable it as a workaround. Disabling was done by setting nsslapd-changelogmaxage to -1. SInce then the number of entries grew to about 3 million. Last week I enabled maxage again. I set it to 470 days. I was hoping to limit this pile of old changelog entries., starting by cleaning very old entries. However, what I noticed is that it was removing entries with a pace of 16 entries per second. Meanwhile the server was doing nothing. Server load was very low. The real problem is that dirsrv (LDAP) is not responding to any requests anymore. I had to disable maxage again, which requires patience restarting the server when it is not responding ;-) Now my questions 1) is it normal dat removing repo changelog entries is slooow? 2) why is dirsrv not responding anymore when the cleanup kicks in? 3) are there alternatives to cleanup the old repo changelog entries? -- Kees _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
