title: Hyperledger validating peer fails to restart
body: <p>I have a Hyperledger setup consisting of one membership service and one validating peer.</p>
  
  <p>I am able to run the membership service and validating peer using the following commands.</p>
  
  <p>Membership Service:</p>
  
  <pre><code>docker run   --name c_membersrvc   --net mynet   --ip 172.17.0.50   --rm -it -e MEMBERSRVC_CA_ACA_ENABLED=true   hyperledger/fabric-membersrvc   membersrvc
  </code></pre>
  
  <p>Validating Peer:</p>
  
  <pre><code>docker run   --name c_vp0   --net mynet --ip 172.17.0.100 -p 172.17.0.1:7050:7050 -p 172.17.0.1:7053:7053   --rm -it   -v /var/run/docker.sock:/var/run/docker.sock -e CORE_VM_ENDPOINT=unix:///var/run/docker.sock   -e CORE_PEER_ID=vp0   -e CORE_PEER_ADDRESSAUTODETECT=true   -e CORE_PEER_VALIDATOR_CONSENSUS_PLUGIN=noop   -e CORE_LOGGING_LEVEL=ERROR   -e CORE_SECURITY_ENABLED=true   -e CORE_SECURITY_PRIVACY=true   -e CORE_PEER_PKI_ECA_PADDR=172.17.0.50:7054   -e CORE_PEER_PKI_TCA_PADDR=172.17.0.50:7054   -e CORE_PEER_PKI_TLSCA_PADDR=172.17.0.50:7054   -e CORE_SECURITY_ENROLLID=test_vp0   -e CORE_SECURITY_ENROLLSECRET=MwYpmSRjupbT   hyperledger/fabric-peer   peer node start
  </code></pre>
  
  <p>However, when I stop the validating peer and restart it using the same command as indicated above, I encounter the following error:</p>
  
  <pre><code>Error: rpc error: code = 2 desc = Identity or token does not match.
  </code></pre>
  
  <p>I am able to restart the validating peer successfully if I restart the membership service first.  In an actual deployment, I don't think my approach of restarting the membership service every time a validating peer needs to restart is practical.</p>
  
  <p>Is there another way to successfully restart a validating peer without the need to restart the membership service?</p>
  
  <p>I saw a similar post on the error <b> Identity or token does not match </b> but this is due to a user/client logging-in through a validating peer.  The proposed solution is to use the Node.js SDK to register/enroll clients.  I am not sure if the same solution is applicable for the validating peer restart issue.</p>