-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.NoClassDefFoundError when java.io.tmpdir is not writable #1332
Comments
After following the instruction it worked... |
After follow this step. Got following error. java.lang.UnsatisfiedLinkError: /tmp/tmpjava/librocksdbjni1513379826889322410.so: libstdc++.so.6: cannot open shared object file: No such file or directory |
I think we should provide a more actionable error message by checking the permissions on the directory eagerly. Adding the fix-it-week label to this to make sure it gets tracked. |
I also received the same error message as mentioned in the org post. After applying the suggested fix chmod +w tmp and chmod +w /var/tmp on my temp directories I get the following error message. I am using confluent platform v 5.4.1 and OS is Ubuntu 18 with CIS hardened image from Azure.
|
Added scenario for java.lang.NoClassDefFoundError when java.io.tmpdir is not writable. For more information: confluentinc#1332
Fixed in #6897. |
KSQL leverages RocksDB which includes a C library. As part of the startup process of RocksDB, it has to extract the C library before it can be used. The location to extract the C library is determined by the
java.io.tmpdir
system property orROCKSDB_SHAREDLIB_DIR
environment variable.If this directory is not writable, then the user will see an error like
Could not initialize class org.rocksdb.Options
when running a query which needs a state store.Here is an example failure mode:
If the user runs into this, the best solution is to set
java.io.tmpdir
to a directory which is writable by all users.In the above example executing
chmod +w javatmp
fixes the issue.The text was updated successfully, but these errors were encountered: