Univention Bugzilla – Bug 32855
Traceback: Invalid packet: missing Domaintemplate — probably threading issue
Last modified: 2023-03-25 06:41:22 CET
After restarting UMC-server and UVMM two requests "uvmm/node/query"s are sent in short succession from the web-frontent, where the 2nd call fails with the following traceback: ==> management-console-module-uvmm.log <== 11.10.13 22:51:42.376 MODULE ( PROCESS ) : An internal error occurred: File "/usr/lib/pymodules/python2.6/notifier/threads.py", line 82, in _run tmp = self._function() File "/usr/lib/pymodules/python2.6/notifier/__init__.py", line 104, in __call__ return self._function( *tmp, **self._kwargs ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/uvmm/uvmmd.py", line 84, in request raise UVMM_Error(str(ex)) UVMM_Error: Not a valid Packet: 'module' object has no attribute 'DomainTemplate' I could not reproduce it with "umcp-command uvmm/node/qeuery" or "uvmm nodes default". I think that src/univention/uvmm/protocol.py:23 creates a PicklingError, which is re-raised as a PacketError. This is translated to a ClientError in src/univention/uvmm/client.py to a ClientError, which is caught in umc/python/umv/uvmmd.py:81 The UMC Python backend process opens a new connection for each request, so there's probably a concurrency error somewhere in UVMMd or Python.
*** Bug 33173 has been marked as a duplicate of this bug. ***
Reported by traceback feedback from 3.2-2 errata125 (Borgfeld).
*** This bug has been marked as a duplicate of bug 44128 ***
Yes, duplicate!
This hit me today on laiva: (u"Die Verbindung zum univention-virtual-machine-manager-daemon-Dienst ist fehlgeschlagen: Not a valid Packet: 'module' object has no attribute 'DomainTemplate'",)