You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/06/11 17:29:00 UTC

[jira] [Commented] (AMBARI-24050) Oozie service check failed during EU on unsecure cluster due to presence of "ELService" configs

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

Hudson commented on AMBARI-24050:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9434 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9434/])
[AMBARI-24050] Oozie service check failed during EU on unsecure clust… (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=6fb7289a0f6e0e732f6bd647493f264ed8969d72])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/OozieConfigCalculation.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/OozieConfigCalculationTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentSupport.java


> Oozie service check failed during EU on unsecure cluster due to presence of "ELService" configs
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-24050
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24050
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> *STR*
> # Deployed an unsecure cluster with Ambari version: 2.6.2.0-155 and HDP version: 2.6.5.0-292 (cluster has Oozie, Falcon installed)
> # Upgrade Ambari to Target Version: 2.7.0.0-652
> # Start an Express Upgrade to HDP-3.0.0.0-1440, Falcon got deleted at one of the steps and later Oozie got restarted
> *Result*
> Afterwards observed Oozie service check failed during EU
> Further checked that Oozie logs say the following:
> {code}
> ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'log4j2.debug' to show Log4j2 internal initialization logging.
> log4j:WARN No appenders could be found for logger (org.apache.oozie.service.Services).
> 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:226)
>         at org.apache.oozie.service.ELService.extractFunctions(ELService.java:104)
>         at org.apache.oozie.service.ELService.init(ELService.java:135)
>         at org.apache.oozie.service.Services.setServiceInternal(Services.java:386)
>         at org.apache.oozie.service.Services.setService(Services.java:372)
>         at org.apache.oozie.service.Services.loadServices(Services.java:305)
>         at org.apache.oozie.service.Services.init(Services.java:213)
>         at org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
>         at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
>         at org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
>         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
> {code}
> Need to remove ELService properties during upgrade



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)