Bug 43116 - retry connection to master in UCS@school installer
retry connection to master in UCS@school installer
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC - Installer
UCS@school 4.1 R2
Other Linux
: P5 normal (vote)
: UCS@school 4.1 R2 vXXX
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-12-05 14:53 CET by Florian Best
Modified: 2019-02-05 21:16 CET (History)
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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2016-12-05 14:53:22 CET
From Bug #41007 comment #8:

> On another VM there was:
> 
> 30.11.16 08:28:53.540  MODULE      ( PROCESS ) : Konnte nicht mit dem DC Master master300.autotest300.local verbinden: master300.autotest300.local: Authentication failed: {"status": 503, "message": "The Univention Management Console Server is currently not running. \nIf you have root permissions on the system you can restart it by executing the following command:\n * invoke-rc.d univention-management-console-server restart\nThe following logfile may contain information why the server is not running:\n * /var/log/univention/management-console-server.log\nOtherwise please contact an administrator or try again later."}
> 
> A retry after 10s/30s would be good, as those ldap-/umc-down situation tend to be temporary.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:16:37 CET
This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug 
and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

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