I’d first check if /etc/apt/sources.list.d/20_ucs_online_component.list contains valid sources for all components. As far as I know it is safe to run the OX-Licence module from UMC to check if the OX-license is still valid.
/var/log/univention/updater.log may contain more information about the mentioned error itself, especially to identify what the “502” code is referring to.
updater.log doesn’t give any clue about the error posted on the GUI. Actually, that is an additional issue there are no logs of the source of this problem. Licensing is valid and rechecked.
Starting univention-upgrade. Current UCS version is 3.1-1 errata193
Checking for local repository: none
Checking for release updates: none
Checking for package updates: none
Setting update/available
Module: ox-config
root@mail:/var/log#
in the mentioned case the server was not able to connect to the App Center host with http directly. The system had to go through a proxy which was not possible. I dont have more details and can just guess that the 5xx response was thrown by the proxy. A solution depends on the specific environment.
Something to know about how the OX-Updates:
The file /etc/apt/sources.list.d/20_ucs-online-component.list of a system with OXSE4UCS contains a list of URLs like:
deb http://YOURLDBACCOUNT:YOURLDBPASSWORD@software.open-xchange.com/OX6/OXSEforUCS/3.1/maintained/component/frontend72/ ./
deb http://YOURLDBACCOUNT:YOURLDBPASSWORD@software.open-xchange.com/OX6/OXSEforUCS/3.1/maintained/component/backend72/ ./
100%[====================================================================================================================================================>] 734 --.-K/s in 0s
2013-10-29 16:14:27 (62.2 MB/s) - `index.html’ saved [734/734]
[/code]
The saved html-file should show entries like the “component” directory and the string “Apache Server at software.open-xchange.com Port 80”.