Discussion:
problem with engine 3.3 on f19 and java path after update
Owen Williams
12 years ago
Permalink
Hello,
Sorry for the poor threading. I've just joined the list.

I edited:

/etc/ovirt-engine/notifier/notifier.conf.d/10-setup-java.conf
/etc/ovirt-engine/engine.conf.d/10-setup-java.conf

to fix this. This got ovirt-engine going again but the web interface
doesn't work yet...

Best regards,

Owen.
Sandro Bonazzola
12 years ago
Permalink
Post by Owen Williams
Hello,
Sorry for the poor threading. I've just joined the list.
/etc/ovirt-engine/notifier/notifier.conf.d/10-setup-java.conf
/etc/ovirt-engine/engine.conf.d/10-setup-java.conf
to fix this. This got ovirt-engine going again but the web interface
doesn't work yet...
Hi, the breakage after java update is a known issue, tracked by https://bugzilla.redhat.com/1009863 .
In the new implementation fixing it, java is detected at runtime using
/usr/share/ovirt-engine/bin/java-home.

if java-home.local is available, execute that script. this enables
distro specific customization.

if OVIRT_ENGINE_JAVA_HOME environment is set, validate java validity
and use/abort.

But looking at your comment it doesn't seems to be something related to java home.
Can you attach the engine and server logs?
Post by Owen Williams
Best regards,
Owen.
_______________________________________________
Users mailing list
http://lists.ovirt.org/mailman/listinfo/users
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
Continue reading on narkive:
Loading...