<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Unable to start NodeManager: no leveldbjni64-1.8 in java.library.path in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Unable-to-start-NodeManager-no-leveldbjni64-1-8-in-java/m-p/99488#M12665</link>
    <description>&lt;P&gt;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. &lt;/P&gt;</description>
    <pubDate>Wed, 16 Dec 2015 06:56:09 GMT</pubDate>
    <dc:creator>pardeep_kumar</dc:creator>
    <dc:date>2015-12-16T06:56:09Z</dc:date>
    <item>
      <title>Unable to start NodeManager: no leveldbjni64-1.8 in java.library.path</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Unable-to-start-NodeManager-no-leveldbjni64-1-8-in-java/m-p/99487#M12664</link>
      <description>&lt;P&gt;Cannot bring up 2 NodeMangers, the other 19 works fine.

I got this:

FATAL nodemanager.NodeManager (NodeManager.java:initAndStartNodeManager(465)) - Error starting NodeManager &lt;/P&gt;&lt;P&gt;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]
&lt;/P&gt;&lt;P&gt;It is not caused by "chmod 777 /tmp", any clue?&lt;/P&gt;</description>
      <pubDate>Wed, 16 Dec 2015 06:51:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Unable-to-start-NodeManager-no-leveldbjni64-1-8-in-java/m-p/99487#M12664</guid>
      <dc:creator>rxu</dc:creator>
      <dc:date>2015-12-16T06:51:40Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to start NodeManager: no leveldbjni64-1.8 in java.library.path</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Unable-to-start-NodeManager-no-leveldbjni64-1-8-in-java/m-p/99488#M12665</link>
      <description>&lt;P&gt;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. &lt;/P&gt;</description>
      <pubDate>Wed, 16 Dec 2015 06:56:09 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Unable-to-start-NodeManager-no-leveldbjni64-1-8-in-java/m-p/99488#M12665</guid>
      <dc:creator>pardeep_kumar</dc:creator>
      <dc:date>2015-12-16T06:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to start NodeManager: no leveldbjni64-1.8 in java.library.path</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Unable-to-start-NodeManager-no-leveldbjni64-1-8-in-java/m-p/99489#M12666</link>
      <description>&lt;P&gt;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? &lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2017 19:34:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Unable-to-start-NodeManager-no-leveldbjni64-1-8-in-java/m-p/99489#M12666</guid>
      <dc:creator>will_westing</dc:creator>
      <dc:date>2017-06-30T19:34:13Z</dc:date>
    </item>
  </channel>
</rss>

