Maybe it is caused by the mixed slash type in the script path. Even on Windows it is normally better to use forward slashes in Java because you don’t have to care about escaping backslashes.
Here we have two different types in the same path definition.
mixed slashes work ok in windows. I had the same in the windows service installation (wrapper) config and there was no problem.
something else is wrong… something is adding “openHAB2userdata” in the path after "C:\openHAB2\userdata" (and before: “etc\shell.init.script”)
it looks like the karaf_etc variable is not set correctly somewhere… I still haven’t found it
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.
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?
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).
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.
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.