You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Emil Anca (JIRA)" <ji...@apache.org> on 2015/04/17 13:41:58 UTC
[jira] [Created] (AMBARI-10562) Issues when log/pid dirs are
customized - Kafka and Knox
Emil Anca created AMBARI-10562:
----------------------------------
Summary: 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
Affects Versions: 1.7.0
Reporter: Emil Anca
Assignee: Emil Anca
Fix For: 2.1.0
Hi all
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.
* The Knox pid dir did not created. Workaround by manually creating it.
Fail: Execution of 'chown -R knox:knox /var/lib/knox/data /var/log/knox /mydisk/run/knox /etc/knox/conf' returned 1. chown: cannot access `/mydisk/run/knox': No such file or directory
After the install wizard error out I also 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)
chmod +x /mydisk/run
chmod +x /mydisk
Thanks in advance for your help
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)