Bug 54312 - univention-appcenter-listener-converter does not write tracebacks in the log file
univention-appcenter-listener-converter does not write tracebacks in the log ...
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-01-07 13:58 CET by Dirk Wiesenthal
Modified: 2022-01-07 13:58 CET (History)
0 users

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

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Wiesenthal univentionstaff 2022-01-07 13:58:55 CET
We should see a traceback in the log file of the univention-appcenter-listener-converter (which uses the log file of the corresponding listener module).

Instead, the service silently dies and is restarted by systemd. You have to search for the traceback in journalctl.

By the way: We should fix one traceback when we are at it:
 63 »···»···if docker.is_running():
 64 »···»···»···machine_password = open(docker.path('/etc/machine.secret')).read()
 65 »···»···logger.info('Using App account connection')
 66 »···»···return get_read_connection(machine_account, machine_password)


This fails if the App is not running. machine_password is not set by python. We should do the get_read_connection() inside the if and issue a critical log message else.