You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Michael Harp (JIRA)" <ji...@apache.org> on 2015/02/02 21:11:35 UTC
[jira] [Resolved] (AMBARI-9411) ambari-server setup fails when
using custom jdk and -s option
[ https://issues.apache.org/jira/browse/AMBARI-9411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Harp resolved AMBARI-9411.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Fixed in AMBARI-9434
> ambari-server setup fails when using custom jdk and -s option
> -------------------------------------------------------------
>
> Key: AMBARI-9411
> URL: https://issues.apache.org/jira/browse/AMBARI-9411
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Environment: sles11sp1
> Reporter: Michael Harp
> Assignee: Robert Levas
> Fix For: 2.0.0
>
>
> Looks like a regression from AMBARI-9228, jdk_num not getting set with the -s option?
> {code}
> # ambari-server setup -s -j /opt/teradata/jvm64/jdk7
> Using python /usr/bin/python2.6
> Setup ambari-server
> Checking SELinux...
> WARNING: Could not run /usr/sbin/sestatus: OK
> Ambari-server daemon is configured to run under user 'root'. Change this setting [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking iptables...
> Checking JDK...
> WARNING: JAVA_HOME /opt/teradata/jvm64/jdk7 must be valid on ALL hosts
> WARNING: JCE Policy files are required for configuring Kerberos security. If you plan to use Kerberos,please make sure JCE Unlimited Strength Jurisdiction Policy Files are valid on all hosts.
> Installing JCE policy...
> ERROR: Exiting with exit code 1.
> REASON: Installing JCE failed: 'Fatal exception: Fail during the extraction of /var/lib/ambari-server/resources/., exit code 1'. Exiting.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)