incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-3126) Oozie missing action-conf
Date Mon, 09 Sep 2013 20:32:53 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762247#comment-13762247
] 

Dmitry Lysnichenko commented on AMBARI-3126:
--------------------------------------------

[~edrevo], thank you for your patch. Can you please provide more details about the issue?

I could not get reproduce using repos mentioned at http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.3.2/bk_using_Ambari_book/content/ambari-chap2-1.html
. Installation was performed to clear Centos 6 node. Oozie started well, it listens port and
log does not contain the mentioned exception.


After installation, I get files:
{code}
[root@red3 ~]# ls -l /etc/oozie/conf/
total 92
drwxr-xr-x. 2 oozie hadoop  4096 Sep  9 20:41 action-conf
-rw-r--r--. 1 oozie hadoop   824 Aug 20 05:54 adminusers.txt
-rw-r--r--. 1 oozie hadoop  1409 Aug 20 05:54 hadoop-config.xml
-rwxr-xr-x. 1 oozie hadoop 69230 Aug 20 05:54 oozie-default.xml
-rw-r--r--. 1 oozie hadoop  1935 Sep  9 20:41 oozie-env.sh
-rw-r--r--. 1 oozie hadoop  3588 Sep  9 20:41 oozie-log4j.properties
-rw-rw-r--. 1 oozie hadoop  3475 Sep  9 20:58 oozie-site.xml

[root@red3 ~]# ls -la /etc/oozie/conf/action-conf/
total 12
drwxr-xr-x. 2 oozie hadoop 4096 Sep  9 20:41 .
drwxr-xr-x. 3 root  root   4096 Sep  9 20:58 ..
-rw-r--r--. 1 oozie hadoop 1305 Aug 20 05:54 hive.xml
{code}


What OS and repo url are you using? Are you performing install to a clear node or to a node
with existing Oozie config dir (or maybe a symlink to other location)?
                
> 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

Mime
View raw message