[
https://issues.apache.org/jira/browse/AMBARI-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763053#comment-13763053
]
Ximo Guanter commented on AMBARI-3126:
--------------------------------------
Hello [~dmitriusan]. I am reproducing this issue not by using the latest
released Ambari, but by using the latest code in the trunk. I am building the
Ambari RPMs using the instructions in
https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development on a
CentOS 6 machine.
I install those RPMs on a clean CentOS 6 machine and I am installing MapRed,
HDFS, Hive and Oozie through Ambari with the HDP 1.3.0 stack. After doing that,
this is what I'm seeing:
{code}
[ximo@cosmos-compute1 ~]$ ls -la /etc/oozie/
total 16
drwxr-xr-x 4 root root 4096 sep 10 09:00 .
drwxr-xr-x 81 root root 4096 sep 10 09:04 ..
drwxr-xr-x 2 oozie hadoop 4096 sep 10 09:02 conf
drwxr-xr-x 3 root root 4096 ago 29 03:44 conf.dist
[ximo@cosmos-compute1 ~]$ ls -la /etc/oozie/conf/
total 20
drwxr-xr-x 2 oozie hadoop 4096 sep 10 09:02 .
drwxr-xr-x 4 root root 4096 sep 10 09:00 ..
-rw-r--r-- 1 oozie hadoop 1935 sep 10 09:00 oozie-env.sh
-rw-r--r-- 1 oozie hadoop 3588 sep 10 09:00 oozie-log4j.properties
-rw-rw---- 1 oozie hadoop 3911 sep 10 09:02 oozie-site.xml
[ximo@cosmos-compute1 ~]$ oozie version
Oozie client build version: 3.3.2.1.3.0.0-107
{code}
On the other hand, if I get a clean node and I {{yum install oozie}} from HDP
1.3.0 (see
http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.3.0/bk_installing_manually_book/content/rpm-chap1-2.html#rpm-chap1-2-4)
I get the following:
{code}
[ximo@cosmos-compute1 ~]# ls -la /etc/oozie/
total 12
drwxr-xr-x 3 root root 4096 sep 10 09:52 .
drwxr-xr-x 81 root root 4096 sep 10 09:51 ..
lrwxrwxrwx 1 root root 28 sep 10 09:52 conf -> /etc/alternatives/oozie-conf
drwxr-xr-x 3 root root 4096 sep 10 09:51 conf.dist
[ximo@cosmos-compute1 ~]$ ls -la /etc/oozie/conf/
total 116
drwxr-xr-x 3 root root 4096 sep 10 10:05 .
drwxr-xr-x 3 root root 4096 sep 10 10:05 ..
drwxr-xr-x 2 root root 4096 sep 10 10:05 action-conf
-rw-r--r-- 1 root root 824 may 20 03:21 adminusers.txt
-rw-r--r-- 1 root root 1409 may 20 03:21 hadoop-config.xml
-rwxr-xr-x 1 root root 69230 may 20 03:21 oozie-default.xml
-rw-r--r-- 1 root root 2036 may 20 03:21 oozie-env.sh
-rw-r--r-- 1 root root 4559 may 20 03:21 oozie-log4j.properties
-rw-r--r-- 1 root root 13098 may 20 03:21 oozie-site.xml
{code}
>From what I'm seeing, it seem like the
{code}
hdp::directory { $oozie_config_dir:
service_state => $service_state,
force => true,
owner => $oozie_user,
group => $hdp::params::user_group,
override_owner => true
}
{code}
call in hdp-oozie/manifests/init.pp is removing the symlink and creating a new
directory (because puppet is not being instructed to follow symlinks), which is
only being populated with oozie-size, oozie-env and oozie-log4j.
> Oozie missing action-conf
> -------------------------
>
> Key: AMBARI-3126
> URL: https://issues.apache.org/jira/browse/AMBARI-3126
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Ximo Guanter
> Assignee: Ximo Guanter
> Fix For: 1.4.1
>
> Attachments: AMBARI-3126-1.patch
>
>
> Ambari will transition the service from INIT to INSTALLED and then STARTED
> with no problems, but the Oozie server won't actually be started. Here's the
> relevant part of the Oozie server's log:
> {code}
> 2013-09-06 02:37:36,821 FATAL Services:533 - USER[-] GROUP[-] E0100: Could
> not initialize service [org.apache.oozie.service.HadoopAccessorService],
> could not find action configuration directory: /etc/oozie/conf/action-conf
> org.apache.oozie.service.ServiceException: E0100: Could not initialize
> service [org.apache.oozie.service.HadoopAccessorService], could not find
> action configuration directory: /etc/oozie/conf/action-conf
> at
> org.apache.oozie.service.HadoopAccessorService.parseConfigDirs(HadoopAccessorService.java:227)
> at
> org.apache.oozie.service.HadoopAccessorService.preLoadActionConfigs(HadoopAccessorService.java:260)
> at
> org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:141)
> at
> org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:97)
> at
> org.apache.oozie.service.Services.setServiceInternal(Services.java:368)
> at org.apache.oozie.service.Services.setService(Services.java:354)
> at org.apache.oozie.service.Services.loadServices(Services.java:287)
> at org.apache.oozie.service.Services.init(Services.java:208)
> at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:39)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
> at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> {code}
> I suspect this is due to line 82 in hdp-oozie/manifests/init.pp:
> {code}
> hdp::directory { $oozie_config_dir:
> service_state => $service_state,
> force => true, // BUG: this will remove the actions-conf directory
> owner => $oozie_user,
> group => $hdp::params::user_group,
> override_owner => true
> }
> {code}
--
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
