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
Attachment:
Monthly
Description: Binary data
_______________________________________________ 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
