Univention Bugzilla – Bug 32160
Complicated error message when trying to upload wrong license file
Last modified: 2013-12-03 09:00:53 CET
Created attachment 5357 [details] error when trying to upload a file Upon trying to upload a license file from another server using UMC following error is produced : Die Ausführung des Kommandos udm/license/import ist fehlgeschlagen: Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/univention/management/console/modules/__init__.py", line 204, in execute func( request ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/udm/udm_ldap.py", line 175, in wrapper_func ret = func( *args, **kwargs ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/udm/__init__.py", line 255, in license_import importer.write( self._user_dn, self._password ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/udm/tools.py", line 95, in write ldap_con.add_s( self.dn, self.addlist ) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 194, in add_s return self.result(msgid,all=1,timeout=self.timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 422, in result res_type,res_data,res_msgid = self.result2(msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 426, in result2 res_type, res_data, res_msgid, srv_ctrls = self.result3(msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 432, in result3 ldap_result = self._ldap_call(self._l.result3,msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 96, in _ldap_call result = func(*args,**kwargs) UNWILLING_TO_PERFORM: {'info': 'no global superior knowledge', 'desc': 'Server is unwilling to perform'} maybe it would be better to print a simpler error message like: Error uploading license, you cannot use a license of another server on this mashine. Every server needs its own license file, because the file is bound to the specific LDAP base.
*** Bug 30814 has been marked as a duplicate of this bug. ***
A customer (Ticket#: 2013081521042475) reported an objectclass violation traceback from license import (see below). I suppose he just missed the last line from the license file (which is "univentionObjectType: settings/license" in his case). We should catch those errors and show a helpful error message like "Please make sure that you have pasted the complete content of the license file" The UNWILLING_TO_PERFORM trace should point the user to check the base-dn/domain of his installation and, if possible, should contain the base-dn of the license file that caused the trace. Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/univention/management/console/modules/__init__.py", line 204, in execute func( request ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/udm/udm_ldap.py", line 175, in wrapper_func ret = func( *args, **kwargs ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/udm/__init__.py", line 255, in license_import importer.write( self._user_dn, self._password ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/udm/tools.py", line 95, in write ldap_con.add_s( self.dn, self.addlist ) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 194, in add_s return self.result(msgid,all=1,timeout=self.timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 422, in result res_type,res_data,res_msgid = self.result2(msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 426, in result2 res_type, res_data, res_msgid, srv_ctrls = self.result3(msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 432, in result3 ldap_result = self._ldap_call(self._l.result3,msgid,all,timeout) File "/usr/lib/python2.6/dist-packages/ldap/ldapobject.py", line 96, in _ldap_call result = func(*args,**kwargs) OBJECT_CLASS_VIOLATION: {'info': "object class 'univentionObject' requires attribute 'univentionObjectType'", 'desc': 'Object class violation'}
Still the same traceback in ucs 3.2
*** This bug has been marked as a duplicate of bug 30156 ***
Okay, should be fixed now
Duplicate