If you try and setup chaining using the root DN, the callback returns -2, which is incorrectly seen as a "disk full" error and the DS is automatically shutdown.
attachment 0001-Ticket-367-Invalid-chaining-config-triggers-a-disk-f.patch
Thanks for the review Noriko!
[mareynol@localhost servers]$ git merge ticket367 Updating ff601de..dc37983 Fast-forward ldap/servers/plugins/chainingdb/cb_instance.c | 192 +++--- ldap/servers/plugins/referint/referint.c | 903 ++++++++++------------ ldap/servers/plugins/replication/repl5_plugins.c | 7 +- 3 files changed, 527 insertions(+), 575 deletions(-)
[mareynol@localhost servers]$ git push Counting objects: 26, done. Delta compression using up to 4 threads. Compressing objects: 100% (16/16), done. Writing objects: 100% (16/16), 5.64 KiB, done. Total 16 (delta 11), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/ds.git ff601de..dc37983 master -> master
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=830334
Added initial screened field value.
Pushed to 389-ds-base-1.2.11: commit c73fc83
Metadata Update from @nkinder: - Issue assigned to mreynolds - Issue set to the milestone: 1.2.11.19
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/367
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 (was: Fixed)
Log in to comment on this ticket.