[ovirt-users] ovirt-engine service in hosted engine appliance cannot start properly
hello,
I have a problem with oVirt in my home lab - probably after power outage(all hypervisors +
hosted engine appliance went down)
Current state: hosted engine appliance is starting from OS perspective, however some jboss
related stuff seems to be malfunctioning.
/var/log/ovirt-engine:
grep ERROR engine.log | tail -n2
2020-03-17 17:35:52,769+01 ERROR
[org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster] (ServerService Thread Pool
-- 50) [] Error initializing: Duplicate key VM [***some_vm_name***]
2020-03-17 17:35:52,922+01 ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread
Pool -- 50) [] Error during initialization: javax.ejb.EJBException:
java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
grep ERROR server.log | tail -n2
2020-03-17 17:36:00,755+01 ERROR [org.jboss.as.controller.management-operation]
(Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address:
([("deployment" => "engine.ear")]) - failure description:
{"WFLYCTL0080: Failed services" =>
{"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START"
=> "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component
instance
2020-03-17 17:36:01,021+01 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026:
WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) started (with errors) in 56493ms -
Started 1492 of 1728 services (6 services failed or missing dependencies, 387 services are
lazy, passive or on-demand)
probably because of that I am receiving 503 while connecting to webgui
grep 503 /var/log/httpd/access_log | tail -n1
***some_intenal_ip*** - - [18/Mar/2020:13:01:26 +0100] "GET
/ovirt-engine/services/health HTTP/1.1" 503 299 "-"
"Python-urllib/2.7"
Ovirt Engine version: ovirt-engine-4.2.8.2-1.el7.noarch
if you could help me or at least give some hints/advice then it could be great. I tried to
google it however without any luck. thanks in advance.
btw - in this case ovirt-engine service status is "fine" when checking via
systemctl - not sure if it should reflect state "active (running)" when it is
working partially