Some umcpCommands may take very long, depending on some server-side I/O. If the time exceeds 300 seconds, Apache responds with an 502 error to the frontend while the command is still process in the backend (but noone will reads its result). While all these cases should be handled by separate bugs where one specific command should be split up and use some progress or whatever, it may be helpful to give customers the ability to fix this behaviour immediately until a real fix can be provided (which may take long to develop depending on the command) or until the issue is resolved on the customer side (e.g. slow internet connection). A variable umc/http/timeout could be introduced and used in /etc/univention/templates/files/etc/apache2/sites-available/univention-management-console: print 'ProxyTimeout %s' % int(configRegistry.get('umc/http/timeout', '300'))
(In reply to Dirk Wiesenthal from comment #0) > A variable umc/http/timeout could be introduced and used in > /etc/univention/templates/files/etc/apache2/sites-available/univention- > management-console: > print 'ProxyTimeout %s' % int(configRegistry.get('umc/http/timeout', '300')) → This can be confusing because there is a similar variable for the session timeout. Maybe apache/umc/timeout ?
(In reply to Florian Best from comment #1) > → This can be confusing because there is a similar variable for the session > timeout. Or we could reuse this very variable
Reported again: Ticket#: 2014030721001988
Fixed in univention-management-console-frontend 3.0.152-24.822.201403202249 Uses umc/http/session/timeout || 300 as ProxyTimeout
YAML file → OK Changes → OK, timeout works fine (tested with 30sec and 10min) → VERIFIED
http://errata.univention.de/ucs/3.2/100.html