Created attachment 1283280 [details]
crash stack trace
Description of problem:
A disk space was exhausted. After cleanup, a restart of 389-ds cannot complete due to a crash in adjust_idl_switch().
# cat /var/lib/dirsrv/slapd-XS-IPA-COOL/db/DBVERSION
Version-Release number of selected component (if applicable):
rpm -q 389-ds-base libdb
Attaching a stack trace.
Fixed upstream in https://pagure.io/389-ds-base/c/9e1a761b45dfc2d28199e39c514ea66764c3f127
Just discussing if we backport to 1.3.6/1.3.5 now (likely yes).
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.