You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2014/07/14 19:04:08 UTC
[jira] [Commented] (AMBARI-6478) Ambari installed JDK owned by uucp
user
[ https://issues.apache.org/jira/browse/AMBARI-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060859#comment-14060859 ]
Jonathan Hurley commented on AMBARI-6478:
-----------------------------------------
Most likely caused by using a TAR file instead of RPM/bin; --no-same-owner flag should fix this. Will implement and verify.
> Ambari installed JDK owned by uucp user
> ---------------------------------------
>
> Key: AMBARI-6478
> URL: https://issues.apache.org/jira/browse/AMBARI-6478
> Project: Ambari
> Issue Type: Bug
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 1.7.0
>
>
> On inspection of the JDK path after running ambari-setup, we notice that the JDK directory is owned by user "uucp" and group "143":
> $ ls -dl /usr/jdk64/jdk1.7.0_45/
> drwxr-xr-x. 8 uucp 143 4096 Oct 8 2013 /usr/jdk64/jdk1.7.0_45/
> This appears off because install of Oracle JDK from RPM makes the root user and group the owner of the JDK directory:
> $ ls -dl /usr/java/jdk1.7.0_51/
> drwxr-xr-x. 8 root root 4096 Apr 21 12:49 /usr/java/jdk1.7.0_51/
--
This message was sent by Atlassian JIRA
(v6.2#6252)