Bug 50666 - Improve univention-translog check --fix
Summary: Improve univention-translog check --fix
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: LDAP
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-20 09:38 CET by Arvid Requate
Modified: 2024-06-27 12:10 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.057
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019121921000565
Bug group (optional):
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2019-12-20 09:38:06 CET 
In Ticket #2019121921000565 the support had to handle a case where the transaction file got corrupted due to a harddisk storage overflow. The univention-translog check --fix was apparently unable to fix the file. We should improve the tool to handle that situation. The tool output is logged with the ticket and th efile should still be accessible in the customers domain.

Additionally it could be good if the "--fix" step could consider/restore the contents of cn=translog, which, due to the ACID qualities of the LMDB database, is less likely to suffer from corruption. In this case there where about 8 additional transactions in cn=translog compared to the file itself.
Comment 1 Jan-Luca Kiok univentionstaff 2024-06-27 12:10:11 CEST 
This issue has been filed against UCS 4.4.

UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.