New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java not enabled! on 2.2.0-1 after installation #41
Comments
Oh, It could be you need to make a Java update. Somewhere I read, that OH2.2.0 needs at least 1.8.101 |
Well, I would say that Java is not installed at all. The QPKG does not depend on any JRE package (https://github.com/openhab/openhab-qnap-qpkg/blob/master/qpkg.cfg#L18), because the QNAP packages for them was not up to date and I added to the service script a installation procedure to install a more recent version manually. |
oh.. my bad... |
Well, we are leaking a good documentation at this point. 2.1.0 also depends on a JRE installation. You most likely installed it in the past via service script and during update it gets removed together with openHAB itself ( that is intended and shall prevent creating data mess ). |
Does the script automatically install Java? |
Nope, the script is not installing it on its own, because you have to agree to Oracle's Java licence. So whenever the script can't find Java installed neither by QNAPs App Store nor via script, then it is showing the error message @melinko mentioned. |
I'm on Firmware 4.3.4.0435 on my TS-451
Since the 2.2.0 Package i get this error message right after the installation finished.
"Java not enabled! Please read the documentation about details. "
I did a clean install and confirmed that all "openHAB" folders where empty or deleted.
The installation of the old 2.1.0 package still works fine, except that it does not use the shared folder as an install path.
I tried to look for logs or anything, but the /userdata consists only of the folders /etc and /tmp nothing more.
Did something about the JRE change in 2.2.0? Or am I missing something big here?
I'm kind of clueless why the 2.1.0 works just fine but the 2.2.0 does not.
The text was updated successfully, but these errors were encountered: