Andrii Tkach created AMBARI-2884:
------------------------------------
Summary: Oozie start fails - likely due to 'failed install'
Key: AMBARI-2884
URL: https://issues.apache.org/jira/browse/AMBARI-2884
Project: Ambari
Issue Type: Bug
Components: client
Affects Versions: 1.4.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
Fix For: 1.4.0
Oozie start failed with following in the log:
hadoop dfs -chmod -R 755 /user/oozie/share' returned 1 instead of one of 0
On the node:
chmod: `/user/oozie/share': No such file or directory
oozie@c6402 ~$ hadoop dfs -ls /user/
DEPRECATED: Use of this script to execute hdfs command is deprecated.
Instead use the hdfs command for it.
Found 3 items
drwxrwx--- - ambari-qa hdfs 0 2013-08-02 02:40 /user/ambari-qa
drwx------ - hive hdfs 0 2013-08-02 02:41 /user/hive
drwxrwxr-x - hdfs hdfs 0 2013-08-02 02:42 /user/oozie
oozie@c6402 ~$ hadoop dfs -ls /user/oozie
DEPRECATED: Use of this script to execute hdfs command is deprecated.
Instead use the hdfs command for it.
oozie@c6402 ~$
The reason, the oozie smoke is failing to run an oozie job with more than one
node in the cluster, due to bad settings in /etc/hadoop/core-site.xml:
<property>
<name>hadoop.proxyuser.oozie.hosts</name>
<value>host1</value>
</property>
host1, in my case is host on which oozie is not installed. After changing this
to host2 (where oozie server is installed), oozie smoke succeeded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
