On 5/26/21 8:15 AM, Mark Reynolds
wrote:
If this is the situation you are running into, then can change the compact interval to 0 for nsslapd-db-compactdb-interval under dn: cn=bdb,cn=config,cn=ldbm database,cn=plugins,cn=config. I would suggest stopping the server and manually editing the dse.ldif in this case because changing the value while the server is running with ldapmodify causes the compaction to start and it will crash your server again.HI Nelsen,
I'm working on a db compaction improvement., Now DB compaction occurs every 30 days, and I found a bug if you don't have replication set up then the server crashes when trying to compact a changelog (that does not exist). This only happens on 389-ds-base-1.4.3, or newer, and only if you don't have replication set up. Can you confirm if you are using replication on this server?
Mark
On 5/26/21 1:42 AM, Nelson Bartley wrote:
Good day, I previously messaged about this issue, but didn't have a core dump to provide. Almost exactly 1 month, to the minute, a scheduled task starts in our 389-ds which results in a seg-fault. We are currently using Fedora 33, 389 packages 1.4.4.15-1.fc33. This bug also occurred with an earlier package set as well (I do not remember the version, same FC33). We have experienced this exact segault now three times on schedule. I have attached to the email the cockpit information from the crash. You can get the coredump from this link: http://gofile.me/4kovq/KZB9Waixm I was hoping it was possible to identify what scheduled service is crashing, and if possible how to disable it temporarily until the actual cause of the crash can be fixed in an updated binary? Nelson
_______________________________________________ 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-- 389 Directory Server Development Team
_______________________________________________ 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
-- 389 Directory Server Development Team
_______________________________________________ 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
