Univention Bugzilla – Bug 39268
exceptions in UCR module handler aren't printed
Last modified: 2020-07-29 17:09:27 CEST
If any exception occurs during a UCR module the only output is: """ E: your request could not be fulfilled try `univention-config-registry --help` for more information """ IMHO the traceback or at least the exception should be printed.
*** Bug 5303 has been marked as a duplicate of this bug. ***
Looks like --debug can be used: Administrator@master431:~$ /usr/sbin/ucr set foo=bar E: your request could not be fulfilled try `univention-config-registry --help` for more information Administrator@master431:~$ /usr/sbin/ucr --debug set foo=bar Traceback (most recent call last): File "/usr/sbin/ucr", line 68, in <module> ub.main(convertToUtf8(sys.argv[1:])) File "/usr/lib/pymodules/python2.7/univention/config_registry/frontend.py", line 691, in main handler_func(args, cmd_opts) File "/usr/lib/pymodules/python2.7/univention/config_registry/frontend.py", line 127, in handler_set with ucr: File "/usr/lib/pymodules/python2.7/univention/config_registry/backend.py", line 134, in __enter__ self.lock() File "/usr/lib/pymodules/python2.7/univention/config_registry/backend.py", line 121, in lock registry.lock() File "/usr/lib/pymodules/python2.7/univention/config_registry/backend.py", line 399, in lock self.lock_file = open(self.lock_filename, "a+") IOError: [Errno 13] Permission denied: '/etc/univention/base.conf.lock' Administrator@master431:~$
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. 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.
Still relevant!
Bug #51739 war hard to debug because the TypeError was not printed.