incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ximo Guanter (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-3126) Oozie missing action-conf
Date Mon, 09 Sep 2013 11:07:52 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ximo Guanter updated AMBARI-3126:
---------------------------------

    Attachment: AMBARI-3126-1.patch

This patch fixes how hdp::directory works with symlinks: it will not follow them instead of
replacing them by an empty directory.
                
> 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.3.0
>
>         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

Mime
View raw message