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

Peter Cseh commented on OOZIE-3303:
-----------------------------------


So the build failed, but the test results are:
https://builds.apache.org/job/PreCommit-OOZIE-Build/696/console
{noformat}

Testing JIRA OOZIE-3303

Cleaning local git workspace

----------------------------

+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
    +1 the patch does not introduce any @author tags
    +1 the patch does not introduce any tabs
    +1 the patch does not introduce any trailing spaces
    +1 the patch does not introduce any line longer than 132
    -1 the patch does not add/modify any testcase
+1 RAT
    +1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 JAVADOC
    +1 the patch does not seem to introduce new Javadoc warning(s)
    WARNING: the current HEAD has 100 Javadoc warning(s)
    +1 the patch does not seem to introduce new Javadoc error(s)
+1 COMPILE
    +1 HEAD compiles
    +1 patch compiles
    +1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [fluent-job/fluent-job-api].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [client].
+1 BACKWARDS_COMPATIBILITY
    +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
    +1 the patch does not modify JPA files
+1 TESTS
    Tests run: 2908
+1 DISTRO
    +1 distro tarball builds with the patch 

----------------------------
-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/696/

Adding comment to JIRA
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0  3176    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (56) GnuTLS recv error (-54): Error in the pull function.
Failed to add comment to JIRA
{noformat}
I'm committing the change.

> Oozie UI does not work
> ----------------------
>
>                 Key: OOZIE-3303
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3303
>             Project: Oozie
>          Issue Type: Bug
>          Components: build, ui
>    Affects Versions: 5.1.0
>         Environment: Mac OS X
> Java 8 u171
> Hadoop 2.6.0
>            Reporter: Andras Salamon
>            Assignee: Andras Salamon
>            Priority: Blocker
>         Attachments: OOZIE-3303-1.patch, OOZIE-3303-2.patch
>
>
> When latest {{master}} Oozie is built locally with Hadoop version 2.6.0, and 
> {{bin/oozied.sh start}} is issued, reaching the UI or accessing CLI results 
> in following error message:
> {noformat}
> {"errorMessage":"org.apache.jasper.JasperException: Unable to compile class 
> for JSP","httpStatusCode":500}
> {noformat}
> Server side error message in {{logs/jetty.log}} is:
> {noformat}
> 2018-07-11 14:57:18,956  INFO Server:414 - Started @6514ms
> 2018-07-11 14:57:46,110  WARN ServletHandler:624 - 
> org.apache.jasper.JasperException: Unable to compile class for JSP
>         at 
> org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:116)
>         ...
>         at org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
>         at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:572)
>         at 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:542)
>         at org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
>         ...
>         at java.lang.Thread.run(Thread.java:748)
> Caused by: Unable to find a javac compiler;
> com.sun.tools.javac.Main is not on the classpath.
> Perhaps JAVA_HOME does not point to the JDK.
> It is currently set to 
> "/Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre"
>         at 
> org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.getCompiler(CompilerAdapterFactory.java:129)
>         ...
>         at 
> org.apache.jasper.compiler.AntCompiler.generateClass(AntCompiler.java:233)
>         ... 60 more
> {noformat}
> From CLI, following is the error message:
> {noformat}
> $ bin/oozie admin -oozie http://localhost:11000 -status
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.security.authentication.client.KerberosAuthenticator).
> 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: IO_ERROR : java.io.IOException: Error while connecting Oozie server. 
> No of retries = 1. Exception = Could not authenticate, Authentication failed, 
> status: 404, message: Not Found
> {noformat}
> Oozie 5.0.0 UI and CLI both work in the same environment.



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

Reply via email to