incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JOAQUIN GUANTER GONZALBEZ <x...@tid.es>
Subject Oozie broken in trunk?
Date Fri, 06 Sep 2013 06:46:30 GMT
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(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)

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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message