[
https://issues.apache.org/jira/browse/AMBARI-12085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597458#comment-14597458
]
Hudson commented on AMBARI-12085:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2977 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2977/])
AMBARI-12085. Cannot stop HDFS components non-root agent + umask 027 (aonishuk)
(aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fece50c7232e2aefdfe7e04e3732e5c6ea521d57)
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/service_check.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_journalnode.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_datanode.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_zkfc.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_snamenode.py
> Cannot stop HDFS components non-root agent + umask 027
> ------------------------------------------------------
>
> Key: AMBARI-12085
> URL: https://issues.apache.org/jira/browse/AMBARI-12085
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.0
>
>
> SITUATION:
> 1) Ambari 2.1.0 build #1105
> 2) non-root server + non-root agents + umask 027
> 3) Installed HDP 2.3 core (see attached for components + layout)
> 4) customized service accounts (threw a "j" in front of everything)
> 5) visudo for non-root agent is setup as shown below
> 6) once cluster is installed, I went to the host with the namenode and from
> Ambari web, said to stop namenode. ambari returned green but the process was
> not killed (pid file was removed though).
> PROBLEM:
> Ambari is not able to read the .pid file unless the agent non-root user is in
> the "jhadoop" group (to get read access).
>
>
>
> [vagrant@c6401 jhdfs]$ ls -l
> total 12
> -rw-r----- 1 jhdfs jhadoop 6 Jun 16 17:51 hadoop-jhdfs-journalnode.pid
> -rw-r----- 1 jhdfs jhadoop 6 Jun 16 17:51 hadoop-jhdfs-namenode.pid
> -rw-r----- 1 jhdfs jhadoop 6 Jun 16 17:52 hadoop-jhdfs-zkfc.pid
> [vagrant@c6401 jhdfs]$ id ambari
> uid=502(ambari) gid=503(ambari) groups=503(ambari)
>
> SOLUTION:
> This part of Stop should not be run as agent non-root "ambari", but as the
> jhdfs user (because that use should be able to read the pid). Otherwise, we
> end up with ambari deleting the pid (because it can't read the pid file), so
> then the component stop fails.
>
>
>
> 2015-06-16 17:13:03,137 -
> u"File['/var/run/hadoop/jhdfs/hadoop-jhdfs-namenode.pid']" {'action':
> ['delete'], 'not_if': 'ls /var/run/hadoop/jhdfs/hadoop-jhdfs-namenode.pid
> >/dev/null 2>&1 && ps -p `cat
> /var/run/hadoop/jhdfs/hadoop-jhdfs-namenode.pid` >/dev/null 2>&1'}
>
> mahadev FYI
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
