Univention Bugzilla – Bug 37681
Traceback when opening UMC, adconnector initialization fails
Last modified: 2023-03-25 06:45:41 CET
The traceback pops up immediately when opening UMC (Bug #35870 initializes the module on startup to display some notification). Traceback: Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/univention/management/console/protocol/modserver.py", line 266, in handle self.__handler.init() File "/usr/lib/pymodules/python2.7/univention/management/console/modules/adconnector/__init__.py", line 118, in init self.__update_status() File "/usr/lib/pymodules/python2.7/univention/management/console/modules/adconnector/__init__.py", line 349, in __update_status self.status_running = self.__is_process_running('*python*univention/connector/ad/main.py*') File "/usr/lib/pymodules/python2.7/univention/management/console/modules/adconnector/__init__.py", line 355, in __is_process_running if proc.cmdline and fnmatch.fnmatch( ' '.join( proc.cmdline ), command ): File "/usr/lib/pymodules/python2.7/psutil/__init__.py", line 330, in cmdline return self._platform_impl.get_process_cmdline() File "/usr/lib/pymodules/python2.7/psutil/_pslinux.py", line 437, in wrapper raise NoSuchProcess(self.pid, self._process_name) NoSuchProcess: process no longer exists (pid=11525)
Also reported via external feedback (4.0-0 errata84 (Walle)) Remark: Aufruf der UMC über Firefox
*** This bug has been marked as a duplicate of bug 41619 ***
Yes, duplicate.