Hi Jean, What is the fabric version and the order type (kafka or raft) . Also can you attach the docker composefiles of your peer and orderers? Regards, Soumya

Yes of course. Here it is rca.example: container_name: rca.example.com image: hyperledger/fabric-ca:1.4.3 command: sh -c 'fabric-ca-server start -d -b admin:adminpw --port 7054

Hi, I'm trying to set up a one way TLS instead of a mutual one. So on my peers and orderer, the flags *_TLS_CLIENTAUTHREQUIRED are all set to false. When starting the network, everything seems to go

Hi Nicholas, the fabric-ca-server-config.yaml is set as follows: tls: # Enable TLS (default: false) enabled: false # TLS for the server's listening port certfile: keyfile: clientauth:

Hi Nicholas, thanks for answering. I'm trying to follow step-by-step the instructions described here: https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/users-guide.html#fabric-ca-server

Please give us more details on what you're trying to do. Are you just starting the server and it gives the error? Are you trying to enroll/register with fabric-ca-client? Get BlueMail for Android On

Affer removing the previous cert and key files, I started again the fabric-ca server discovering that new cert and key files were created: (base) marco@pc:~/fabric/fabric-ca$ fabric-ca-server start

Reminder: Hyperledger Fabric Quarterly Update Due #tsc-project-update When: Thursday, 3 October 2019 View Event Organizer: community-architects@... Description: The Hyperledger Fabric

As Will mentioned and I put up earlier, that if you are using CLI 'CORE_PEER_ADDRESS' is where you are executing the command **from**, I get that you don't want any peer to execute any command ,

Hello Siddaharth, you can specify the name of smart contract in command parameter -n and -c as parameter to chaindcode : peer chaincode invoke -o orderer.example.com:7050 -C mychannel -n

Hello, How do we specify what smart contract needs to be executed when using the peer chaincode invoke CLI in v1.4?

I think we'd need to see the entire compose file here ----------------------------------------- Gari Singh Distinguished Engineer, CTO - IBM Blockchain IBM Middleware 550 King St Littleton, MA

I tried that. Same problem. Also, in the fabric samples they use the same working directories. I also noticed they use the same orderer Genesis block for all 3 which I'm also doing. If I remove the

They all need different working directories. They can’t share leveldb files for obvious reasons.

Ok thanks. We'll try it with 1.4 and report if we run into the issue again. From: William T Lahti <wtlahti@...> Sent: Wednesday, September 25, 2019 12:04 PM To: siddjain@... <siddjain@...> Cc:

Right, as I mentioned, it appears to be caused by the same bug. There was some bad error logic in that code (that I was responsible for adding a number of years back) that could lead to the panic you

we are using 1.3 of Fabric. The error is similar to that bug although that bug is regarding a CORE_PEER_TLS flag also see inline. thanks: From: William T Lahti <wtlahti@...> Sent: Wednesday,

Can you clarify which version of Fabric you're using? This appears to be caused by the same bug you reported in https://jira.hyperledger.org/browse/FAB-15506, which was fixed in v1.4.2. In regards

Hey guys, I'm trying to deploy 3 orderers on the same organization and machine. I can't seem to get it working, two orderers gives me this error: panic: Error opening leveldb: resource temporarily

Sorry, I have no idea what this means. Some examples would be helpful. As stated in the question we are running thepeer chaincode invoke command (say on Joe's machine) to invoke chaincode on remote