I have the same problem and maybe one more
Does openHAB 2.2.0 snapshot build 1017 require a new Java VM ? I used openHAB 1 on the same Windows homeserver 2011 (based on Windows server 2008) for years without problems. Now I get a few errors from karaf.
I am migrating my installation with astro1,exec1,http1,network, plugwise,rfxcom and zwave to openHAB2.
I hope someone has a tip to help me proceed beyond this point.
Gert
you just need to go install the JDK to get rid of that warning. I updated to #1029 today and see this error too… my system seems fairly unusable though I’m not sure this is related.
There are no Items in paperUI, log:tail does nothing. is this on anyone’s radar to fix?
I did a fresh install of build #1029 on Windows 10 and apart from the Karaf error message, everything seems to work at first glance.
I am using Java 8 Build 144.
@Kai I am not sure whether these messages are a Karaf or ESH/openHAB problem and where to report it. What would you say?
I am not sure either. To find it out, it would be nice if you could try to start a plain Karaf 4.1.2 and see if it has the same issue.
I downloaded Karaf 4.1.2 and started it without seeing the issue.
Karaf 4.1.2 works fine. I have created an issue in the openHAB Distro repo: Error message in Karaf console on Windows 10 · Issue #530 · openhab/openhab-distro · GitHub
Not sure if it is related as I am running in a docker on an Ubuntu machine (not Windows), but I had exactly the same error running any build after 1024. The error seems to be related to an update in JLine and its corresponding interaction with the terminal I think.
To get openHAB to work properly, I had to specifically add a -t flag in the docker run command (which allocates a pseudo tty terminal).
I think this is a different problem and probably docker related. Starting the latest openHAB on Ubuntu Linux does not give any error messages.
Yes, that is quite possible/probable. It is odd though that the error is exactly the same and in the same file, hence partly why I think it may be jline related rather than karaf.
S1031 on a x64 Win10 with latest Oracle’s JVM has the same issue:
didn’t have time to dig deeper to see what could be the root cause
I made a diff between the original karaf.bat and karaf.bat delivered with openHAB. There are several differences and maybe there was a change in the original karaf.bat that was not taken into account in the openHAB karaf.bat.
Having the same error. I switched from Build 982 to 1039.
I “solved” the problem! I commented the following line in userdata\etc\system.properties:
# karaf.shell.init.script = ${karaf.etc}/shell.init.script
Now, the error is gone!
Can anyone confirm this, too?
Yes, indeed, the error message disappears. I hope that functionality is not affected…
I don’t know. How can I check, if the shell.script is running?
I have no idea. But since the scipt was not running all the time with the error message it cannot be that important for my installation…
I tested also with this in userdata\etc\system.properties:
karaf.shell.init.script = c:/Openhab2/userdata/etc/shell.init.script
or
karaf.shell.init.script = etc/shell.init.script
The error also is gone!
Hello,
the error ist still in the last Snapshot.
I searched in the Batch for a failure but … noting.
In the karaf.bat Java starts with the right argument
-Dkaraf.etc="D:\openhab\userdata\etc"
But then it shows
Error in initialization script: D:\openhab\userdata\openhabuserdataetc\shell.init.script: D:\openhab\userdata\openhabuserdataetc\shell.init.script
The system Proberties dosnt changed since my last Update. It is still
karaf.shell.init.script = ${karaf.etc}/shell.init.script
When i changed this to
karaf.shell.init.script = etc/shell.init.script
from Celaeno1 but is this right or is there another problem then?
If you want to keep the variable, changing this line to the following also worked for me.
karaf.shell.init.script = ${karaf}/etc/shell.init.script