[
https://issues.apache.org/jira/browse/HADOOP-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270501#comment-15270501
]
Steve Loughran commented on HADOOP-13018:
-----------------------------------------
* checkstyle is fussing about indentation and a javadoc lacking a "."; easy and
nice to fix
* test failure is, presumably, related
The test details are not appearing in the logs as its only failing on java 8,
and the test results are for java 7 The unit test logs are more informative
{code}
Tests in error:
TestKDiagNoKDC.testTokenFile:128->kdiagFailure:84 ? KerberosDiagsFailure JVM:
...
TestKDiagNoKDC.testKDiagStandalone:107->kdiagFailure:84 ? KerberosDiagsFailure
TestRPCWaitForProxy.testInterruptedWaitForProxy:74->Object.wait:-2 ? test
tim...
{code}
...
Looks like one is JCE settings, the other a failure of the new code.
{code}
testTokenFile(org.apache.hadoop.security.TestKDiagNoKDC) Time elapsed: 0.07
sec <<< ERROR!
org.apache.hadoop.security.KDiag$KerberosDiagsFailure: JVM: Java Cryptography
Extensions are not installed on this JVM. Maximum supported key length 128 -
minimum required 256
at org.apache.hadoop.security.KDiag.fail(KDiag.java:884)
at org.apache.hadoop.security.KDiag.verify(KDiag.java:911)
at org.apache.hadoop.security.KDiag.validateKeyLength(KDiag.java:419)
at org.apache.hadoop.security.KDiag.execute(KDiag.java:277)
at org.apache.hadoop.security.KDiag.run(KDiag.java:224)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at org.apache.hadoop.security.KDiag.exec(KDiag.java:993)
at
org.apache.hadoop.security.TestKDiagNoKDC.kdiagFailure(TestKDiagNoKDC.java:84)
at
org.apache.hadoop.security.TestKDiagNoKDC.testTokenFile(TestKDiagNoKDC.java:128)
testKDiagStandalone(org.apache.hadoop.security.TestKDiagNoKDC) Time elapsed:
0.059 sec <<< ERROR!
org.apache.hadoop.security.KDiag$KerberosDiagsFailure: TOKEN: token file does
not exist: SomeNonExistentFile
at org.apache.hadoop.security.KDiag.fail(KDiag.java:884)
at org.apache.hadoop.security.KDiag.verify(KDiag.java:911)
at org.apache.hadoop.security.KDiag.verifyFileIsValid(KDiag.java:735)
at
org.apache.hadoop.security.KDiag.validateHadoopTokenFiles(KDiag.java:496)
at org.apache.hadoop.security.KDiag.execute(KDiag.java:362)
at org.apache.hadoop.security.KDiag.run(KDiag.java:224)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at org.apache.hadoop.security.KDiag.exec(KDiag.java:993)
at
org.apache.hadoop.security.TestKDiagNoKDC.kdiagFailure(TestKDiagNoKDC.java:84)
at
org.apache.hadoop.security.TestKDiagNoKDC.testKDiagStandalone(TestKDiagNoKDC.java:107)
{code}
You need to downgrade the key length in the cli command, the way the other
tests do. Then lets see what happens to those tests
> Make Kdiag check whether hadoop.token.files points to existent and valid files
> ------------------------------------------------------------------------------
>
> Key: HADOOP-13018
> URL: https://issues.apache.org/jira/browse/HADOOP-13018
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Attachments: HADOOP-13018.01.patch, HADOOP-13018.02.patch,
> HADOOP-13018.03.patch
>
>
> Steve proposed that KDiag should fail fast to help debug the case that
> hadoop.token.files points to a file not found. This JIRA is to affect that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
