Bug 48754 – Report presence of failed.ldif in univention-join and univention-check-join-status

Bug 48754 - Report presence of failed.ldif in univention-join and univention-check-join-status


Summary:	Report presence of failed.ldif in univention-join and univention-check-join-s...

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Join (univention-join)
Version:	UCS 5.0
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-02-25 16:00 CET by Arvid Requate
Modified:	2021-05-03 21:59 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
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-02-25 16:00:26 CET

It would be great if univention-check-join-status would report the presence of a failed.ldif, because, obviously the "join status" is not good any longer.

Also univention-join couls check, maybe directly after each individual join script and abort in case a failed.ldif was present.


Otherwise you always have to anticipate that you have to look into listener.log for a lines like:

25.02.19 15:48:15.814  LISTENER    ( ERROR   ) : 'failed.ldif' exists. Check for /var/lib/univention-directory-replication/failed.ldif