im fairly new to OpenHAB2 and i installed Systeminfo at first.
The problem is it instantly throws the error “UNINITIALIZED - HANDLER_INITIALIZING_ERROR”
Native library (com/sun/jna/freebsd-x86-64/libjnidispatch.so) not found in resource path (/mnt/openhab2/runtime/lib/boot/org.apache.karaf.diagnostic.boot-4.0.8.jar:/mnt/openhab2/runtime/lib/boot/org.apache.karaf.jaas.boot-4.0.8.jar:/mnt/openhab2/runtime/lib/boot/org.apache.karaf.main-4.0.8.jar:/mnt/openhab2/runtime/lib/boot/org.osgi.core-6.0.0.jar
as far as i could find out its something about jnas native library not exported correctly. But how do i fix this issue myself and is it my fault ?
Im running OpenJDK 1.8 on FreeNAS 9.10
Hey @Benjy thanks for your reply.
Yes i already read the documentation and tried to do so. But i installed the binding through PaperUi and no plugins were put into the pluginfolder. So i did some research and found the called jar deep inside some temp folders and they are generated every startup from some packed jar inside “openhab2/runtime/lib/boot/” named org.osgi.core-6.0.0.jar. Do i need to dissasemble the jar now to update the files ? Do i need to unpack that jar and make those changes ? The instructions are pretty unclear about that if u come from the PaperUI.
Reading this myself I think this is more of a development task. The instructions are asking you to rebuild the binding after placing the files here, which is probably not the most constructive thing to ask the usual user to do.
Just to make sure, you’re on the latest version of openHAB right? If so, it might be best to make an issue report containing your error log at the upstream library here, you should state that you’re using the latest version of the systeminfo binding for openHAB. This is because openHAB looks to be using the latest version of OSHI anyway.
OSHI dev here. This error is associated with loading the JNI stub necessary for JNA to work, which is not so much OSHI per se, as JNA. And ultimately it’s a classpath problem. We need to get whatever code is starting this JVM to recognize the correct path to the JNI library listed in the error.
@jan_b are you okay to ask for a way build this on the Google support group as mentioned? If you can get a in date version of freebsd-x86-64.jar you should only need to place it in /mnt/openhab2/runtime/lib/boot/.
Hi @ewok21, what do you mean? Are you having the same issue as described above? Or are just seeking the latest version of it.
If the latter, currently the latest version is inside openHAB 2.1. You need only update to that to bring the binding up to date. When patches are added between openHAB versions and you want the latest changes immediately, you can either install the snapshot version of openHAB, or add the .JAR file related to the binding in your /runtime/addons folder.
Once this PR has gone from “Open” to “Merged”, then you can update to openHAB 2.2.0-SNAPSHOT the following day (which is the easiest option), or add the .JAR file found here (again, only a day after the PR is merged) to /usr/share/openhab2/addons
@ewok21, the fix has not been pushed to openHAB yet. I’d ignore using the jar file if you’re new to the command configurations. You’ll need to wait and then consider changing to the unstable release. If you’re using the prebuilt raspberry pi image then you can switch using the config tool, otherwise you need to follow the Linux instructions (apt-based >> snapshot).