Problem: UMC service does not start anymore

Knowledge Base Community
,
#1

Problem:

UMC service does not start anymore You get the following traceback and message:

11.10.21 12:37:32.642  MAIN        ( ERROR   ) : Traceback (most recent call last):
  File "/usr/sbin/univention-management-console-server", line 285, in <module>
    umc_daemon.do_action()
  File "/usr/lib/python2.7/dist-packages/daemon/runner.py", line 267, in do_action
    func(self)
  File "/usr/lib/python2.7/dist-packages/daemon/runner.py", line 186, in _start
    self.app.run()
  File "/usr/sbin/univention-management-console-server", line 228, in run
    with self.server:
  File "/usr/lib/python2.7/dist-packages/univention/management/console/protocol/server.py", line 366, in __enter__
    self.__realunixsocket.listen(SERVER_MAX_CONNECTIONS)
  File "/usr/lib/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
error: [Errno 22] Das Argument ist ungültig
 
11.10.21 13:00:52.418  DEBUG_INIT
11.10.21 13:00:52.419  MAIN        ( PROCESS ) : Failed to shutdown server gracefully (may be its already dead): PID file '/var/run/umc-server.pid' not locked

Investigation:

Start the umc in terminal:
/usr/bin/python2.7 /usr/sbin/univention-management-console-server -n d4

Solution:

The service cannot create his socket. Looks similar to Bug 32255
In this case the directory /var/run/univention-management-console exists, but with the permission 755. This is the default permission, but in this case we had to set 777.

#2
Mastodon