Univention Bugzilla – Bug 31233
Crippled login dialog after login attempt with missing UMC server
Last modified: 2014-11-28 11:02:27 CET
Created attachment 5204 [details] Login form with missing UMC server process Error szenario in UCS 3.1-1 errata91: the UMC server process is not running (UMC web server is running!) and a user tries to access the UMC. The login window is correctly displayed, the user enters his credentials and presses login. Result: The login fails and the user gets a crippled login form (see attachment).
The user should be prompted at least a meaningful error message instead of this login dialog.
How often does this happen? If it does not occur so often we should fix it later.
(In reply to comment #2) > How often does this happen? If it does not occur so often we should fix it > later. At the moment, Bug 31154 triggers this situation. It would help users to solve the situation by their own if they are affected by bug 31154. I haven't seen the problem in other situations yet.
(In reply to comment #2) > How often does this happen? If it does not occur so often we should fix it > later. Looking a bit closer at it during the QA of Bug 27989, it seemed to me that this problem with the dialogue should not really happen. IMHO there seems to be a generic problem with the handling of the iframe reload.
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2. As such, this bug is moved to the new target milestone.
Me too after IP reconfiguration: # pgrep -fl univention-management-console 8388 /usr/bin/python2.6 /usr/sbin/univention-management-console-web-server restart # tail /var/log/univention/management-console-server.log 31.10.13 11:29:41.188 MAIN ( PROCESS ) : Server started 31.10.13 11:38:06.305 MAIN ( ERROR ) : Traceback (most recent call last): File "/usr/sbin/univention-management-console-server", line 209, in <module> umc_daemon.do_action() File "/usr/lib/pymodules/python2.6/daemon/runner.py", line 186, in do_action func(self) File "/usr/sbin/univention-management-console-server", line 142, in _restart self._start() File "/usr/lib/pymodules/python2.6/daemon/runner.py", line 131, in _start self.app.run() File "/usr/sbin/univention-management-console-server", line 192, in run notifier.loop() File "/usr/lib/pymodules/python2.6/notifier/nf_generic.py", line 284, in loop step() File "/usr/lib/pymodules/python2.6/notifier/nf_generic.py", line 271, in step not __sockets[ cond ][ fd ]( sock_obj ): File "/usr/lib/pymodules/python2.6/univention/management/console/protocol/server.py", line 165, in _receive self._handle( state, msg ) File "/usr/lib/pymodules/python2.6/univention/management/console/protocol/server.py", line 279, in _handle state.processor = Processor( *state.credentials() ) File "/usr/lib/pymodules/python2.6/univention/management/console/protocol/session.py", line 213, in __init__ ldap_dn = self.lo.searchDn( '(&(uid=%s)(objectClass=posixAccount))' % self.__username ) File "/usr/lib/pymodules/python2.6/univention/admin/uldap.py", line 361, in searchDn raise univention.admin.uexceptions.noObject, _err2str(msg) noObject: No such object 31.10.13 11:38:06.367 MAIN ( PROCESS ) : Processor: dying
(In reply to Philipp Hahn from comment #6) > Me too after IP reconfiguration: > > # pgrep -fl univention-management-console > 8388 /usr/bin/python2.6 /usr/sbin/univention-management-console-web-server > restart > > # tail /var/log/univention/management-console-server.log > 31.10.13 11:29:41.188 MAIN ( PROCESS ) : Server started > 31.10.13 11:38:06.305 MAIN ( ERROR ) : Traceback (most recent call last): > ... Apart from the login dialogue issue, this traceback should not happen. I opened Bug 33086 for this. Otherwise, instead of a crippled login dialogue, the user needs a sensible error message to know what he can do. Would it make sense to restart the UMC server automatically in case it crashes?
*** Bug 33855 has been marked as a duplicate of this bug. ***
In UCS 4.0 this cannot happen to the login dialog anymore. As the iframe was moved into the hidden/invisible area.