Bug 44928 – New check `logcheck.py`

Bug 44928 - New check `logcheck.py`


Summary:	New check `logcheck.py`

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - System diagnostic
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-07-04 12:30 CEST by Lukas Oyen
Modified:	2020-07-03 20:51 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Feature Request
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:

Flags:	oyen: Patch_Available+

Attachments
nt-diagnostic-logcheck.patch (12.00 KB, patch) 2017-07-04 12:30 CEST, Lukas Oyen	Details \| Diff
View All 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 Lukas Oyen

2017-07-04 12:30:36 CEST

Created attachment 8996 [details]
nt-diagnostic-logcheck.patch

This is a basic implementation of a `logcheck.py` for the diagnostic tool. This
is inspired by several log-file checks by Julian Hupertz.

We could improve this with proper markup in the diagnostic tool for structuring
the output as a list of results and maybe coloring the error markers (ERROR,
WARNING, BACKTRACE, ..).

The first half of the file could be pulled out into something like
`univention-logcheck` for a more general usage. This tool should maybe provide
some sort of JSON output for usage in this diagnostic check or the new
`univention-system-check`.

Finally this needs discussion of what logfiles are worth examining and what
constitutes a report-worthy error in which logfile.

Comment 1 Ingo Steuwer

2020-07-03 20:51:08 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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