Failure to run `nb.jar` on MacOS
See original GitHub issueWhen trying to use nb.jar
(either built locally or downloading latest release, currently 4.15.93
) on MacOS, I get stack trace like:
bin % java -jar ./nb-4.15.93.jar --list-drivers
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load library 'IOKit':
dlopen(libIOKit.dylib, 9): image not found
dlopen(libIOKit.dylib, 9): image not found
Native library (darwin/libIOKit.dylib) not found in resource path (./nb-4.15.93.jar)
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:302)
at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:455)
at com.sun.jna.Library$Handler.<init>(Library.java:192)
at com.sun.jna.Native.load(Native.java:596)
at com.sun.jna.Native.load(Native.java:570)
at com.sun.jna.platform.mac.IOKit.<clinit>(IOKit.java:51)
at com.sun.jna.platform.mac.IOKitUtil.<clinit>(IOKitUtil.java:39)
at oshi.hardware.platform.mac.MacCentralProcessor.queryArmCpu(MacCentralProcessor.java:262)
at oshi.hardware.platform.mac.MacCentralProcessor.initProcessorCounts(MacCentralProcessor.java:142)
at oshi.hardware.common.AbstractCentralProcessor.<init>(AbstractCentralProcessor.java:83)
at oshi.hardware.platform.mac.MacCentralProcessor.<init>(MacCentralProcessor.java:64)
at oshi.hardware.platform.mac.MacHardwareAbstractionLayer.createProcessor(MacHardwareAbstractionLayer.java:61)
at oshi.util.Memoizer$1.get(Memoizer.java:87)
at oshi.hardware.common.AbstractHardwareAbstractionLayer.getProcessor(AbstractHardwareAbstractionLayer.java:68)
at io.nosqlbench.nb.api.metadata.SystemId.getHostSummary(SystemId.java:81)
at io.nosqlbench.engine.cli.NBCLI.run(NBCLI.java:128)
at io.nosqlbench.engine.cli.NBCLI.main(NBCLI.java:66)
Suppressed: java.lang.UnsatisfiedLinkError: dlopen(libIOKit.dylib, 9): image not found
at com.sun.jna.Native.open(Native Method)
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:191)
... 16 more
Suppressed: java.lang.UnsatisfiedLinkError: dlopen(libIOKit.dylib, 9): image not found
at com.sun.jna.Native.open(Native Method)
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:204)
... 16 more
Suppressed: java.io.IOException: Native library (darwin/libIOKit.dylib) not found in resource path (./nb-4.15.93.jar)
at com.sun.jna.Native.extractFromResourcePath(Native.java:1095)
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:276)
... 16 more
the only invocation that succeeds is one without arguments; any command-line arguments trigger this exception.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Unable to execute JAR file - Apple Stack Exchange
I can launch it from Terminal by executing a Bash script (mentioned below), but double clicking on the JAR in Finder fails (right...
Read more >Cannot launch JAR file in Mac OS X 10.14.3 (Mojave)
I'm running an iMacPro running Mac OS X ver. 10.14.3 (Mojave). When I attempt to start a JAR file, all I get is...
Read more >Mac OS unable to run .Jar file - java - Stack Overflow
When you double click the MyProject.jar file, you actually launch it through jar launcher. The jar launcher will pass the files to the...
Read more >Is there a way to run this jar on Macos High Sierra?
In my case, I had a Netbeans app that I developed in Snow Leopard and was unable to open by double-clicking in High...
Read more >macOS arm64 support? · Issue #91 · developersu/ns-usbloader
I get this error: Java application launch failed. Can you upload some log for running this jar? Also print the version of java:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was a compatibility issue with the Java and OSHI runtimes. Correct versions were deployed and the problem appears to be resolved.
Correct, this was resolved. Thank you!