Impala Daemon Not Starting - "Process" Directory Not Created

[#1]

One of our Impala daemons will not start.  There is no directory structure being created at:

/var/run/cloudera-scm-agent/process/nnnnnn-impala-IMPALAD

After the daemon fails to start, the stderr and stdout logs cannot be accessed because the directory structure does not exist.  Instead, there is an HTTP 403 error, referencing the expected path, indicating "The server declined access to the page or resource."  In addition, nothing is being written to the error, warning, or info logs at /hadoop/log/impalad.

What can be done to enable the creation of the directory structure?  Deleting and reinstalling the Impala role does not resolve it.  There are no issues with other roles on the host.  I am wondering whether it is necessary to re-initialize the host and re-install the roles.

Michael Reynolds

[#2]

Thank you very much for your reply.  According to the agent log, the service account responsible for running the Impala service does not exist on the host.  I appreciate your pointing me in the right direction.