[jira] [Resolved] (AMBARI-10562) Issues when log/pid dirs are customized - Kafka and Knox

["Robert Levas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Levas resolved AMBARI-10562.
-----------------------------------
    Resolution: Fixed

Committed to trunk
{code}
commit 239d3ac7541ab3642c1031191e4bbafd5fd9a9e6
Author: Emil Anca <ea...@hortonworks.com>
Date:   Fri Apr 24 11:12:38 2015 -0400
{code}

> Issues when log/pid dirs are customized - Kafka and Knox
> --------------------------------------------------------
>
>                 Key: AMBARI-10562
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10562
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Emil Anca
>            Assignee: Emil Anca
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10562_01.patch, AMBARI-10562_02.patch
>
>
> I ran a number of tests before we do start where I ran Ambari 1.7 to install HDP 2.2 on a VM after changing all the /var/log, /var/run, /hadoop references form defaults to instead be under some other dir.  I am encountering a number of Ambari failures which I needed help on. 
> After the install wizard error out I noticed:
> * Starting Kafka/Knox from Ambari actually starts the processes but Ambari thinks they died and goes red. On further investigation the /mydisk/run/kafka and /mydisk/run/knox are empty so the pid files are not getting created. I re-installed on fresh VM and ran the below to give kafka/knox users access to those dirs before running install wizard but still got same error (even though as those users I can write to those dirs)
> {code}chmod +x /mydisk/run
> chmod +x /mydisk
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)