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

Robert Nettleton updated AMBARI-12385:
--------------------------------------
    Fix Version/s:     (was: 2.1.0)
                   2.1.1

> Oozie Service Fails After Downgrade Because Of Missing Falcon JAR In WAR
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-12385
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12385
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>             Fix For: 2.1.1
>
>         Attachments: AMBARI-12385.patch
>
>
> After upgrading from HDP 2.2 to HDP 2.3 and then downgrading back to HDP 2.2, 
> Oozie services shut down with the following:
> {noformat}
> INFO: Starting service Catalina
> Jul 10, 2015 3:22:36 PM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.41
> Jul 10, 2015 3:22:36 PM org.apache.catalina.startup.HostConfig 
> deployDescriptor
> INFO: Deploying configuration descriptor oozie.xml
> Jul 10, 2015 3:22:36 PM org.apache.catalina.loader.WebappClassLoader 
> validateJarFile
> INFO: 
> validateJarFile(/usr/hdp/current/oozie-server/oozie-server/webapps/oozie/WEB-INF/lib/servlet-api-2.5.jar)
>  - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: 
> javax/servlet/Servlet.class
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.2.0.0-2041/hadoop/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.2.0.0-2041/oozie/libserver/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.2.0.0-2041/oozie/libserver/slf4j-simple-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.2.0.0-2041/oozie/oozie-server/webapps/oozie/WEB-INF/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/grid/0/hdp/2.2.0.0-2041/oozie/oozie-server/webapps/oozie/WEB-INF/lib/slf4j-simple-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> log4j:WARN No appenders could be found for logger 
> (org.apache.curator.framework.imps.CuratorFrameworkImpl).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> ERROR: Oozie could not be started
> REASON: org.apache.oozie.service.ServiceException: E0113: class not found 
> [org.apache.oozie.extensions.OozieELExtensions]
> Stacktrace:
> -----------------------------------------------------------------
> org.apache.oozie.service.ServiceException: E0113: class not found 
> [org.apache.oozie.extensions.OozieELExtensions]
>         at org.apache.oozie.service.ELService.findMethod(ELService.java:225)
>         at 
> org.apache.oozie.service.ELService.extractFunctions(ELService.java:103)
>         at org.apache.oozie.service.ELService.init(ELService.java:134)
>         at 
> org.apache.oozie.service.Services.setServiceInternal(Services.java:383)
>         at org.apache.oozie.service.Services.setService(Services.java:369)
>         at org.apache.oozie.service.Services.loadServices(Services.java:302)
>         at org.apache.oozie.service.Services.init(Services.java:210)
>         at 
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:45)
>         at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4210)
>         at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4709)
>         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:583)
>         at 
> org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
>         at 
> org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
>         at 
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
>         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)
>         at 
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
>         at org.apache.catalina.core.StandardHost.start(StandardHost.java:822)
>         at 
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
>         at 
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
>         at 
> org.apache.catalina.core.StandardService.start(StandardService.java:525)
>         at 
> org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
>         at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method){noformat}
> This is caused by the missing Falcon JAR in the Oozie WAR
> {code:title=Falcon JAR exists in libext}
> [root@os-r6-grncus-c2dalunshadg-12 tmp]# ll 
> /usr/hdp/current/oozie-server/libext
> total 7608
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 10 11:34 ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop   23717 Jul 10 11:34 
> falcon-oozie-el-extension-0.6.0.2.2.0.0-2041.jar
> -rw-r--r--. 1 oozie hadoop  959987 Jul 10 11:34 mysql-connector-java.jar
> {code}
> {code:title=Building the Oozie WAR and verifying no falcon JAR exists}
> [root@os-r6-grncus-c2dalunshadg-12 tmp]# 
> /usr/hdp/current/oozie-server/bin/oozie-setup.sh prepare-war  -d 
> /usr/hdp/current/oozie-server/libext-customer
>   setting OOZIE_CONFIG=${OOZIE_CONFIG:-/etc/oozie/conf}
>   setting 
> CATALINA_BASE=${CATALINA_BASE:-/usr/hdp/current/oozie-client/oozie-server}
>   setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
>   setting OOZIE_CATALINA_HOME=/usr/lib/bigtop-tomcat
>   setting JAVA_HOME=/usr/jdk64/jdk1.7.0_67
>   setting JRE_HOME=${JAVA_HOME}
>   setting OOZIE_LOG=/grid/0/log/oozie
>   setting CATALINA_PID=/var/run/oozie/oozie.pid
>   setting OOZIE_DATA=/grid/0/hadoop/oozie/data
>   setting OOZIE_HTTP_PORT=11000
>   setting OOZIE_ADMIN_PORT=11001
>   setting 
> JAVA_LIBRARY_PATH=/usr/hdp/2.2.0.0-2041/hadoop/lib/native/Linux-amd64-64
>   setting OOZIE_CLIENT_OPTS="${OOZIE_CLIENT_OPTS} 
> -Doozie.connection.retry.count=5 "
>   setting CATALINA_OPTS="${CATALINA_OPTS} -Xmx2048m -XX:MaxPermSize=256m "
>   setting OOZIE_CONFIG=${OOZIE_CONFIG:-/etc/oozie/conf}
>   setting 
> CATALINA_BASE=${CATALINA_BASE:-/usr/hdp/current/oozie-client/oozie-server}
>   setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
>   setting OOZIE_CATALINA_HOME=/usr/lib/bigtop-tomcat
>   setting JAVA_HOME=/usr/jdk64/jdk1.7.0_67
>   setting JRE_HOME=${JAVA_HOME}
>   setting OOZIE_LOG=/grid/0/log/oozie
>   setting CATALINA_PID=/var/run/oozie/oozie.pid
>   setting OOZIE_DATA=/grid/0/hadoop/oozie/data
>   setting OOZIE_HTTP_PORT=11000
>   setting OOZIE_ADMIN_PORT=11001
>   setting 
> JAVA_LIBRARY_PATH=/usr/hdp/2.2.0.0-2041/hadoop/lib/native/Linux-amd64-64
>   setting OOZIE_CLIENT_OPTS="${OOZIE_CLIENT_OPTS} 
> -Doozie.connection.retry.count=5 "
>   setting CATALINA_OPTS="${CATALINA_OPTS} -Xmx2048m -XX:MaxPermSize=256m "
> New Oozie WAR file with added 'ExtJS library' at 
> /usr/hdp/current/oozie-client/oozie-server/webapps/oozie.war
> INFO: Oozie is ready to be started
> [root@os-r6-grncus-c2dalunshadg-12 tmp]# unzip -l 
> /usr/hdp/current/oozie-client/oozie-server/webapps/oozie.war | grep falcon
> [root@os-r6-grncus-c2dalunshadg-12 tmp]#
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to