<?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: Can't start yarn after cleaning /tmp in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280442#M208847</link>
    <description>&lt;P&gt;There is no file &lt;SPAN&gt;Jetty_0_0_0_0_8042_node&amp;nbsp;&lt;/SPAN&gt;in /tmp, the partition is been wiped out.&lt;/P&gt;&lt;P&gt;Is not a problem of permission, but of missing file.&lt;/P&gt;&lt;P&gt;How can I let yarn to remake those files?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 17 Oct 2019 08:27:38 GMT</pubDate>
    <dc:creator>Cico</dc:creator>
    <dc:date>2019-10-17T08:27:38Z</dc:date>
    <item>
      <title>Can't start yarn after cleaning /tmp</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280351#M208803</link>
      <description>&lt;P&gt;Searching on internet I found that I can clean the tmp directory without problem on a cloudera cluster, so I did it.&lt;/P&gt;
&lt;P&gt;Now, when I try to start the cluster all services goes up well, but yarn failed to start with this error:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;19/10/16 15:50:17 FATAL nodemanager.NodeManager: Error starting NodeManager
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: NMWebapps failed to start.
        at org.apache.hadoop.yarn.server.nodemanager.webapp.WebServer.serviceStart(WebServer.java:79)
        at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
        at org.apache.hadoop.service.CompositeService.serviceStart(CompositeService.java:120)
        at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceStart(NodeManager.java:329)
        at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
        at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:563)
        at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:609)
Caused by: org.apache.hadoop.yarn.webapp.WebAppException: Error starting http server
        at org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:279)
        at org.apache.hadoop.yarn.server.nodemanager.webapp.WebServer.serviceStart(WebServer.java:65)
        ... 6 more
Caused by: java.io.IOException: Unable to initialize WebAppContext
        at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:922)
        at org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:274)
        ... 7 more
Caused by: java.io.FileNotFoundException: /tmp/Jetty_0_0_0_0_8042_node____19tj0x/webapp/webapps/node/.keep (No such file or directory)
        at java.io.FileOutputStream.open0(Native Method)
        at java.io.FileOutputStream.open(FileOutputStream.java:270)
        at java.io.FileOutputStream.&amp;lt;init&amp;gt;(FileOutputStream.java:213)
        at java.io.FileOutputStream.&amp;lt;init&amp;gt;(FileOutputStream.java:162)
        at org.mortbay.resource.JarResource.extract(JarResource.java:215)
        at org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:974)
        at org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:832)
        at org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
        at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:489)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
        at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
        at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
        at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
        at org.mortbay.jetty.Server.doStart(Server.java:224)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
        at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:900)&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What can I do?&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2019 18:12:11 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280351#M208803</guid>
      <dc:creator>Cico</dc:creator>
      <dc:date>2019-10-16T18:12:11Z</dc:date>
    </item>
    <item>
      <title>Re: Can't start yarn after cleaning /tmp</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280439#M208844</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/70346"&gt;@Cico&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Error indicates that the yarn user is unable to access the file&amp;nbsp; /tmp/Jetty_0_0_0_0_8042_node____19tj0x/webapp/webapps/node/.keep&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems there is an issue with /tmp directory permissions on local.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Login to the particular Nodemanager node which reports the error and check if /tmp directory permissions are set to 777. This should allow yarn user to access the file&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;# chmod 777 /tmp&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2019 08:24:01 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280439#M208844</guid>
      <dc:creator>paras</dc:creator>
      <dc:date>2019-10-17T08:24:01Z</dc:date>
    </item>
    <item>
      <title>Re: Can't start yarn after cleaning /tmp</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280442#M208847</link>
      <description>&lt;P&gt;There is no file &lt;SPAN&gt;Jetty_0_0_0_0_8042_node&amp;nbsp;&lt;/SPAN&gt;in /tmp, the partition is been wiped out.&lt;/P&gt;&lt;P&gt;Is not a problem of permission, but of missing file.&lt;/P&gt;&lt;P&gt;How can I let yarn to remake those files?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2019 08:27:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280442#M208847</guid>
      <dc:creator>Cico</dc:creator>
      <dc:date>2019-10-17T08:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: Can't start yarn after cleaning /tmp</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280447#M208850</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/70346"&gt;@Cico&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the permissions are already set to 777 for /tmp , restart the particular node manager from Cloudera Manager. This should allow the creation of new file in /tmp.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2019 08:40:01 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280447#M208850</guid>
      <dc:creator>paras</dc:creator>
      <dc:date>2019-10-17T08:40:01Z</dc:date>
    </item>
    <item>
      <title>Re: Can't start yarn after cleaning /tmp</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280448#M208851</link>
      <description>&lt;P&gt;Thank you very much!&lt;/P&gt;&lt;P&gt;You saved the day.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2019 08:45:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Can-t-start-yarn-after-cleaning-tmp/m-p/280448#M208851</guid>
      <dc:creator>Cico</dc:creator>
      <dc:date>2019-10-17T08:45:57Z</dc:date>
    </item>
  </channel>
</rss>

