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

Rakesh R commented on ZOOKEEPER-2712:
-------------------------------------

[~hanm], Yes the test cases are happily running in my Windows env. Later, I 
have tried running in Linux and it is failing. After putting the delay between 
the server startup, I could see it is passing consistently.

[~hanm], [~phunt], It would be really helpful if you could post your feedback 
on the proposed fix. Thanks!


> MiniKdc test case intermittently failing due to principal not found in 
> Kerberos database
> ----------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2712
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: tests
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>             Fix For: 3.4.10
>
>         Attachments: 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the 
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR 
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client 
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos 
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos 
> database (6)
> {code}
> Will attach the detailed log to jira.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to