Bug 50666 – Improve univention-translog check --fix

Bug 50666 - Improve univention-translog check --fix


Summary:	Improve univention-translog check --fix

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-12-20 09:38 CET by Arvid Requate
Modified:	2019-12-20 11:43 CET (History)
CC List:	0 users

See Also:	49225 50668
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):
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

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.