Hello,
I have a server with OpenNebula 5.8.5 an Ruby 2.0.0.648-5 in a CentOS-7.6.1810 whre opennebula-sunstone fails and ends unexpectedly. This is the error logged at /var/log/message, because there are NO error at /var/log/one/sunstone.log
Oct 10 12:42:06 nebulacaos-clus ruby: pure virtual method called
Oct 10 12:42:06 nebulacaos-clus ruby: terminate called without an active exception
Oct 10 12:42:06 nebulacaos-clus systemd: opennebula-sunstone.service: main process exited, code=killed, status=6/ABRT
Oct 10 12:42:06 nebulacaos-clus systemd: Unit opennebula-sunstone.service entered failed state.
Oct 10 12:42:06 nebulacaos-clus systemd: opennebula-sunstone.service failed.
Oct 10 12:42:07 nebulacaos-clus systemd: opennebula-sunstone.service holdoff time over, scheduling restart.
Oct 10 12:42:07 nebulacaos-clus systemd: Stopped OpenNebula Web UI Server.
To allow that users could authenticatealways, I have added “Restart=on-failure” in opennebula-sunstone.service file, so when daemon fails, it restarts automatically…
…But it would be interesting to know why Sunstone fails. I have added “:debug_level 0” in sunstone-server.conf, but by the moment this file doesn’t exist.
Thanks.
Hi again,
two years ago, I had got that error… I decided to disable opennebula-sunstone and enable Passenger RackApp with memcached daemon. From that day, system has been working FINE, but some days ago, after updating system to OpenNebula 6.0.0.2, I decided to try again opennebula-sunstone… Yesterday, I got the same error:
Sep 28 10:34:20 nebula ruby: pure virtual method called
Sep 28 10:34:20 nebula ruby: terminate called without an active exception
Sep 28 10:34:20 nebula systemd: opennebula-sunstone.service: main process exited, code=killed, status=6/ABRT
Sep 28 10:34:20 nebula systemd: Unit opennebula-sunstone.service entered failed state.
Sep 28 10:34:20 nebula systemd: Triggering OnFailure= dependencies of opennebula-sunstone.service.
Sep 28 10:34:20 nebula systemd: opennebula-sunstone.service failed.
Sep 28 10:34:20 nebula systemd: Created slice system-opennebula\x2dsunstone\x2dnotify\x2demail.slice.
Sep 28 10:34:20 nebula systemd: Started crond failure email notification.
Sep 28 10:34:20 nebula systemd: opennebula-sunstone.service holdoff time over, scheduling restart.
Sep 28 10:34:20 nebula systemd: Stopped OpenNebula Web UI Server.
Sep 28 10:34:20 nebula systemd: Starting OpenNebula Web UI Server…
System is running a CentOS-7.9.2009.
What can I do (besides disabling opennebula-sunstone and enabling Passenger RackApp)?
Thanks.