Starting Studio. This may take a few minutes. You will be notified here when Studio is ready. Uncaught error from thread [Studio-eventuate.log.dispatchers.write-dispatcher-7] shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[Studio] java.lang.UnsatisfiedLinkError: Could not load library. Reasons: [no leveldbjni64-1.8 in java.library.path, no leveldbjni-1.8 in java.library.path, no leveldbjni in java.library.path, /tmp/libleveldbjni-64-1-9150286051047390226.8: /tmp/libleveldbjni-64-1-9150286051047390226.8: failed to map segment from shared object: Operation not permitted] at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:182) at org.fusesource.hawtjni.runtime.Library.load(Library.java:140) at org.fusesource.leveldbjni.JniDBFactory.<clinit>(JniDBFactory.java:48) at com.rbmhtechnology.eventuate.log.leveldb.LeveldbEventLog.<init>(LeveldbEventLog.scala:97) at com.rbmhtechnology.eventuate.log.leveldb.LeveldbEventLog$$anonfun$7.apply(LeveldbEventLog.scala:362) at com.rbmhtechnology.eventuate.log.leveldb.LeveldbEventLog$$anonfun$7.apply(LeveldbEventLog.scala:362) <truncated for readability>
Cause
This issue occurs when the user running the Java process does not having the necessary rights and cannot generate temporary files under the /tmp directory.
Solution
Solution 1- Allow the user running DataStax studio read/write/execute access on /tmp - Remove the noexec parameter when mounting /tmp - Change the execution rights on /tmp. ie: sudo chmod 777 /tmp
Solution 2- Change the temp directory used by DataStax Studio - As per the cause, create/use a folder on which the user has execution rights. In the example below, we insert the STUDIO_JVM_ARGS with temp directory pointing to /home/user/tmp in /home/user/datastax-studio-6.0.2/bin/setenv.sh:
echo STUDIO_JVM_ARGS='-Djava.io.tmpdir=/home/user/tmp' | tee -a /home/user/datastax-studio-6.0.2/bin/setenv.sh
Summary
'Uncaught error' when starting DataStax Studio on Linux.
Applies to
Symptoms
When starting DataStax Studio with
./server.sh
, the following error occursCause
This issue occurs when the user running the Java process does not having the necessary rights and cannot generate temporary files under the
/tmp
directory.Solution
Solution 1- Allow the user running DataStax studio read/write/execute access on
/tmp
- Remove the
noexec
parameter when mounting/tmp
- Change the execution rights on /tmp. ie:
sudo chmod 777 /tmp
Solution 2- Change the temp directory used by DataStax Studio
- As per the cause, create/use a folder on which the user has execution rights. In the example below, we insert the
STUDIO_JVM_ARGS
with temp directory pointing to/home/user/tmp
in/home/user/datastax-studio-6.0.2/bin/setenv.sh
:Related documentation
Specifying JVM settings for DataStax Studio