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

Bruce Schuchardt commented on GEODE-4322:
-----------------------------------------

If you're going to shut down the whole cluster you can delete the .dat file 
when you stop each locator.  If you shut down the first locator and then change 
your mind that's okay, too.  If you restart it the locator will recover its 
state from the still-running locator.

I've asked Brian Baynes to talk with you about this ticket and am re-assigning 
it to him.

> Locator fails to start with NPE during join to the distributed system
> ---------------------------------------------------------------------
>
>                 Key: GEODE-4322
>                 URL: https://issues.apache.org/jira/browse/GEODE-4322
>             Project: Geode
>          Issue Type: Bug
>          Components: membership
>    Affects Versions: 1.2.0
>            Reporter: Vahram Aharonyan
>            Assignee: Brian Baynes
>            Priority: Major
>
> Found out that after setting security-udp-dhalgo=AES:128 in prorperties files 
> sometimes  locator is failing to come online with the following Exception:
> [severe 2018/01/19 04:22:12.194 PST <locator request thread[20]> tid=0x45] 
> Exception in processing request from 10.144.248.41
> java.lang.RuntimeException: Not found public key for member 
> 16nodedata6(d4b4f5d4-47d2-44b1-a07c-6a7f5755e52d:11493)<ec><v2>:10002
>  at 
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:177)
>  at 
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.getPublicKey(JGroupsMessenger.java:1365)
>  at 
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.processRequest(GMSLocator.java:271)
>  at 
> org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1256)
>  at 
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:401)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
>  at 
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258)
>  at 
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175)
>  ... 7 more
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
>  at 
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258)
>  at 
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175)
>  ... 7 more
> Please note, that generally this issue is hit after cluster restart. This is 
> important, as during poweroff locator can go offline first and one of other 
> members will become coordinator and update view file accordingly.



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

Reply via email to