Bug 45494 – We should check, if a failed.ldif was mentioned in the listerner.log

Bug 45494 - We should check, if a failed.ldif was mentioned in the listerner.log


Summary:	We should check, if a failed.ldif was mentioned in the listerner.log

Status:	RESOLVED FIXED

Product:	USI
Classification:	Unclassified
Component:	usi-check tests
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal
Target Milestone:	---
Assigned To:	USI maintainer
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-10-06 16:32 CEST by Christina Scheinig
Modified:	2017-10-17 16:23 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
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:	2017100621000248
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 Christina Scheinig

2017-10-06 16:32:01 CEST

In a customer environment I have not found a failed.ldif message at first glance.
After a restart of the listener the message no longer occurs in the logfile. 

I added the logfile at the ticket

Comment 1 Christina Scheinig

2017-10-17 16:23:10 CEST

I implemented the check as an usi-check in ldap/03failed_ldif.py but we could also check in univention-support-info if /var/lib/univention-directory-replication/failed.ldif exists, in case the logmessage was already rotated.