Unable to start NodeManager: no leveldbjni64-1.8 in java.library.path

[#1]

Cannot bring up 2 NodeMangers, the other 19 works fine. I got this: FATAL nodemanager.NodeManager (NodeManager.java:initAndStartNodeManager(465)) - Error starting NodeManager

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, Permission denied]

It is not caused by "chmod 777 /tmp", any clue?

[#2 · Accepted solution]

Please verify that /tmp on both hosts do not have the noexec option set. You can verify this by running /bin/mount and checking the mount options. If you are able to, remount /tmp without noexec and try starting the NodeManager again. I am sure its issue with noexec on /tmp.

[#3]

hello, we have security provisions that prevent us from removing the noexec from /tmp. also, this is not occuring on other nodes that have the noexec in use. is there another solution?