<?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: Impala Daemon Not Starting - &amp;quot;Process&amp;quot; Directory Not Created in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-Daemon-Not-Starting-quot-Process-quot-Directory-Not/m-p/35459#M13145</link>
    <description>&lt;P&gt;Thank you very much for your reply.&amp;nbsp; According to the agent log, the service account responsible for running the Impala service does not exist on the host.&amp;nbsp; I appreciate your pointing me in the right direction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 21 Dec 2015 20:35:54 GMT</pubDate>
    <dc:creator>Urantian</dc:creator>
    <dc:date>2015-12-21T20:35:54Z</dc:date>
    <item>
      <title>Impala Daemon Not Starting - "Process" Directory Not Created</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-Daemon-Not-Starting-quot-Process-quot-Directory-Not/m-p/35451#M13143</link>
      <description>&lt;P&gt;One of our Impala daemons will not start.&amp;nbsp; There is no directory structure being created at:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/var/run/cloudera-scm-agent/process/nnnnnn-impala-IMPALAD&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After the daemon fails to start, the stderr and stdout logs cannot be accessed because the directory structure does not exist.&amp;nbsp; Instead, there is an HTTP 403 error, referencing the expected path, indicating "The server declined access to the page or resource."&amp;nbsp; In addition, nothing is being written to the error, warning, or info logs at /hadoop/log/impalad.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What can be done to enable the creation of the directory structure?&amp;nbsp; Deleting and reinstalling the Impala role does not resolve it.&amp;nbsp; There are no issues with other roles on the host.&amp;nbsp; I am wondering whether it is necessary to re-initialize the host and re-install the roles.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Michael Reynolds&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 09:54:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-Daemon-Not-Starting-quot-Process-quot-Directory-Not/m-p/35451#M13143</guid>
      <dc:creator>Urantian</dc:creator>
      <dc:date>2022-09-16T09:54:12Z</dc:date>
    </item>
    <item>
      <title>Re: Impala Daemon Not Starting - "Process" Directory Not Created</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-Daemon-Not-Starting-quot-Process-quot-Directory-Not/m-p/35453#M13144</link>
      <description>&lt;P&gt;When using Cloudera Manager to start the daemons, Cloudera Manager creates a command to be run and tells the host on which the service will start to hearbeat into Cloudera Manager. &amp;nbsp;The agent heartbeat response from Cloudera Manager will tell the agent that a service needs to start.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is up to the agent, then to start the process. &amp;nbsp;If you see no /var/run/... directory being created, that means that something likely went wrong before that was supposed to occur. &amp;nbsp;Some places to check&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cloudera Manager. &amp;nbsp;If the command failed to be processed due to a timeout you should see an error in the Command itself. &amp;nbsp;What do you see there?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cloudera Manager log (/var/log/cloudera-scm-server.log ) What happens in the log when you try to start the daemon?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Agent log (/var/log/cloudera-scm-agent). &amp;nbsp;On the host where the Impala daemon should be running, check the agent log for clues. &amp;nbsp;Did the agent even know that it should start the service? &amp;nbsp;Are there errors or excpetions during hearbeat attempts?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's a good place to start.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2015 17:42:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-Daemon-Not-Starting-quot-Process-quot-Directory-Not/m-p/35453#M13144</guid>
      <dc:creator>bgooley</dc:creator>
      <dc:date>2015-12-21T17:42:39Z</dc:date>
    </item>
    <item>
      <title>Re: Impala Daemon Not Starting - "Process" Directory Not Created</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-Daemon-Not-Starting-quot-Process-quot-Directory-Not/m-p/35459#M13145</link>
      <description>&lt;P&gt;Thank you very much for your reply.&amp;nbsp; According to the agent log, the service account responsible for running the Impala service does not exist on the host.&amp;nbsp; I appreciate your pointing me in the right direction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2015 20:35:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-Daemon-Not-Starting-quot-Process-quot-Directory-Not/m-p/35459#M13145</guid>
      <dc:creator>Urantian</dc:creator>
      <dc:date>2015-12-21T20:35:54Z</dc:date>
    </item>
  </channel>
</rss>

