After some investigation, it seems the issue is
hdp-oozie/manifests/init.pp, line 82:
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
}
I have opened https://issues.apache.org/jira/browse/AMBARI-3126. I will
test removing the "force" parameter and submit a patch if that fixes the
problem.
Thanks,
Ximo
El 06/09/13 08:46, "JOAQUIN GUANTER GONZALBEZ" <[email protected]> escribió:
>Hello devs,
>
>Yesterday I pulled the latest changes from trunk and it seems Oozie is
>not working. 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:
>
>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(HadoopAcces
>sorService.java:227)
> at
>org.apache.oozie.service.HadoopAccessorService.preLoadActionConfigs(Hadoop
>AccessorService.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.jav
>a: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(LifecycleSupp
>ort.java:142)
>
>I have verified that /etc/oozie/conf/action-conf does not exist, but
>there is a similar folder called /etc/oozie/conf.dist/action-conf
>
>Is this a known issue in trunk or should I open a Jira issue for it?
>
>Thanks,
>Ximo.
>
>________________________________
>
>Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>nuestra pol?tica de env?o y recepci?n de correo electr?nico en el enlace
>situado m?s abajo.
>This message is intended exclusively for its addressee. We only send and
>receive email on the basis of the terms set out at:
>http://www.tid.es/ES/PAGINAS/disclaimer.aspx
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
nuestra política de envío y recepción de correo electrónico en el enlace
situado más abajo.
This message is intended exclusively for its addressee. We only send and
receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
