Univention Bugzilla – Bug 44049
univention-management-console-server not running on slave after update to 4.2
Last modified: 2017-04-04 18:29:52 CEST
Update a slave to 4.2 and yes i restarted the server. -> systemctl status univention-management-console-server ● univention-management-console-server.service - LSB: Univention Management Console Server Loaded: loaded (/etc/init.d/univention-management-console-server) Active: failed (Result: resources) since Do 2017-03-23 16:31:03 CET; 5min ago Process: 5434 ExecStop=/etc/init.d/univention-management-console-server stop (code=exited, status=0/SUCCESS) Process: 5508 ExecStart=/etc/init.d/univention-management-console-server start (code=exited, status=0/SUCCESS) Main PID: 1252 (code=exited, status=1/FAILURE) Mär 23 16:31:03 slave systemd[1]: PID file /var/run/umc-server.pid not readable (yet?) after start. Mär 23 16:31:03 slave systemd[1]: Failed to start LSB: Univention Management Console Server. Mär 23 16:31:03 slave systemd[1]: Unit univention-management-console-server.service entered failed state. -> stop/start Mär 23 16:39:34 slave systemd[1]: Stopped LSB: Univention Management Console Server. Mär 23 16:39:37 slave systemd[1]: Starting LSB: Univention Management Console Server... Mär 23 16:39:37 slave systemd[1]: PID file /var/run/umc-server.pid not readable (yet?) after start. Mär 23 16:39:37 slave systemd[1]: Failed to start LSB: Univention Management Console Server. Mär 23 16:39:37 slave systemd[1]: Unit univention-management-console-server.service entered failed state.
I guess it is Bug #44052 as well. *** This bug has been marked as a duplicate of bug 44052 ***
Yes, duplicate.
UCS 4.2 has been released: https://docs.software-univention.de/release-notes-4.2-0-en.html https://docs.software-univention.de/release-notes-4.2-0-de.html If this error occurs again, please use "Clone This Bug".