trying to solved troubles with VNC, restarted opennebula-novnc service.
It’s not possible to restart it any longer, because:
systemctl start opennebula-novnc.service A dependency job for opennebula-sunstone.service failed. See “systemctl status opennebula-novnc.service” and “journalctl -xe” for details.
● opennebula-novnc.service - OpenNebula noVNC Server
Loaded: loaded (/lib/systemd/system/opennebula-novnc.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mo 2017-12-11 18:08:46 CET; 19h ago
Process: 24439 ExecStart=/usr/bin/novnc-server start (code=exited, status=1/FAILURE)
Dez 11 18:08:46 f1 novnc-server[24439]: from /usr/lib/ruby/2.3.0/logger.rb:695:in set_dev' Dez 11 18:08:46 f1 novnc-server[24439]: from /usr/lib/ruby/2.3.0/logger.rb:635:ininitializ
Dez 11 18:08:46 f1 novnc-server[24439]: from /usr/lib/ruby/2.3.0/logger.rb:353:in new' Dez 11 18:08:46 f1 novnc-server[24439]: from /usr/lib/ruby/2.3.0/logger.rb:353:ininitializ
Dez 11 18:08:46 f1 novnc-server[24439]: from /usr/bin/novnc-server:53:in new' Dez 11 18:08:46 f1 novnc-server[24439]: from /usr/bin/novnc-server:53:in'
Dez 11 18:08:46 f1 systemd[1]: opennebula-novnc.service: Control process exited, code=exited status=
Dez 11 18:08:46 f1 systemd[1]: Failed to start OpenNebula noVNC Server.
Dez 11 18:08:46 f1 systemd[1]: opennebula-novnc.service: Unit entered failed state.
Dez 11 18:08:46 f1 systemd[1]: opennebula-novnc.service: Failed with result ‘exit-code’.
~
I think so. Because noVNC was working from time to time, but showing the connection time out too often. So I decided to restart the sunstone service with service opennebula-sunstone stop and can’t start it any longer.