Re: Error: Enrollment information does not exist


cridev
 

Thanks for the flag Chris,

I'll look into that, though I am not (yet) trying Kubernetes, just using the out-of-the-box fabcar example from fabric-samples.

Do you think this might be related to the client error I am getting in Explorer?

[INFO] FabricClient - Error : Failed to connect client peer,  please check the configuration and peer status

Many thanks

-CR


On 2020-05-14 20:58, Chris Gabriel wrote:

I always recommend reading the docs in the Hyperledger Fabric CA section which has been updated recently.  Additionally, I have a video tutorial on YouTube (https://www.youtube.com/watch?v=PbMxqH6bNB8) for running the FABRIC CA on Kubernetes where your specific question is covered at about the 8:50 mark of the video.  There is an accompanying public github repo with a comprehensive README here.  

On May 14, 2020, at 1:44 PM, Chris Gabriel via lists.hyperledger.org <alaskadd=gmail.com@...> wrote:

You are not in the client binary directory when issuing the command. You can fix this by exporting the FABRIC_CA_CLIENT_HOME variable and run the command again. This used to get me too, so we updated the CA docs with better instructions.

 

On May 14, 2020, at 1:35 PM, cridev@... wrote:

Hi all.

I am trying to interact with Fabric through the "fabric-ca-client" binary. I have launched the fabcar, compiled the javascript and node enrollAdmin and node registerUser without errors. However, when I try to launch fabric-ca-client identity list to query the identities that were enrolled and registered by the fabcar (through test-network) this fails and I get a:

ERROR] Enrollment check failed: Idemix enrollment information does not exist
Error: Enrollment information does not exist. Please execute enroll command first. Example:
 fabric-ca-client enroll -u http://user:userpw@serverAddr:serverPort

Note that from the logs I had seen the same exact comment had already went through.

fabric-ca-client enroll -u https://admin:adminpw@localhost:7054 --caname ca-org1 --tls.certfiles /path/to/fabric-ca/org1/tls-cert.pem

Am I missing something obvious here?


Join fabric@lists.hyperledger.org to automatically receive all group messages.