Bug 45296 – No handlers could be found for logger "univention.service_info"

Bug 45296 - No handlers could be found for logger "univention.service_info"


Summary:	No handlers could be found for logger "univention.service_info"

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	UCR
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:	2017-08-30 14:09 CEST by Sönke Schwardt-Krummrich
Modified:	2020-08-20 16:17 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.011
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 Sönke Schwardt-Krummrich

2017-08-30 14:09:28 CEST

During the last technical training the error message
> No handlers could be found for logger "univention.service_info"
was noticed on all UCS 4.2-1 systems:

root@dc0:~# ucr search --brief ^version/
version/erratalevel: 144
version/patchlevel: 1
version/releasename: Lesum
version/version: 4.2
root@dc0:~# ucr set listener/autostart='yes' 
Setting listener/autostart
Module: autostart
No handlers could be found for logger "univention.service_info"
root@dc0:~#

Comment 1 Ingo Steuwer

2020-07-03 20:52:41 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.

Comment 2 Florian Best

2020-08-20 16:17:33 CEST

I see this message very often, too.