Currently with error conditions like:
[12/Jul/2017:07:50:44 -0700] - database index is corrupt; key *zon has a data item with the wrong size (5)
We don't notify which index is affected. THis means an admin can't resolve the issue. We should indicate which index has the issue.
1. 2. 3.
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.3.7.0
Metadata Update from @mreynolds: - Issue assigned to mreynolds
https://pagure.io/389-ds-base/pull-request/50563
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.1 (was: 1.3.7.0)
Commit 441d5ab relates to this ticket
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @firstyear: - Issue status updated to: Open (was: Closed)
It looks like this triggers an abort: I have contacted @mreynolds via email to discuss some ideas about fixing this. :)
Fix assert:
https://pagure.io/389-ds-base/pull-request/50569
Commit 8474a17 relates to this ticket
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/2383
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.