Thanks Satheesh, it worked. I had to specify the relative path for the tls cert, I was specifying the absolute path. now I am trying to edit system channel and getting the following error. any idea ab

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

orderer host need to be fully qualified with domain name. And if orderer is running on a different host, you need to provide that instead of locallhost along with port number where orderer is listenin

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

thanks for the reply Satheesh. I tried the suggestion. the orderer name is just orderer0 so instead of orderer.example.com, I have used just orderer0. (this is correct right?). the error still persist

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

you need to pass orderer details as well: for e.g., -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Hey guys, overview of the problem i need to add a new consortium to a an existing HLF setup.For that i need to fetch config block of the system channel and edit it to add the new consortium info. I am

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

If we build chaincode using below steps repeatedly without removing .tar bundle each time, we can observe increase in bundle file size. Eventually we encounter rpc error mentioned. peer lifecycle chai

I would like to mention that this setup is spread between 2 clusters, I am exposing services between clusters to interconnect using skupper. the current running blockchain is on azure central India cl

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Hey guys, overview of the problem i need to add a new consortium to a an existing HLF setup.For that i need to fetch config block of the system channel and edit it to add the new consortium info. I am

#orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Exactly what chaincode build steps are you doing? Are you following one of the samples or docs? What component is the suspected bug in? From: fabric@... <fabric@...

Got resolution from this thread: Hyperledger Fabric Go chaincode size too big - Stack Overflow @Fabric team, Is this not a bug ? If the packaged tar is not removed, repeated builds are increasing the

great. good to hear. Minifabric has been really heavily tested. It has been solid for past few years.

Started working now. I'm not sure if something in memory was causing the issue as rebooting my computer seems to have cleared up this issue - at least for now.

hi All, This is my block listener implemented in fabric sdk: Consumer<BlockEvent> blockListener = blockEvent -> { //some lines } networkObj.addBlockListener(startBlockNumber, blockListener); once adde

#fabric-sdk-java

We are using Hyperledger Fabric 2.3.0 and using SBFT Consensus, and leader is rotating after every block creation. and we set MaxMessageCount to 10 in configtx.yaml but it is not restricting no of tra

#fabric-orderer #consensus

Hi team, I am calling contract event in following way. ==================== await contract.addContractListener(listener, { checkpointer: await DefaultCheckpointers.file('checkpoint.json'), }); =======

When installing chaincode in a fabric network, I get below error: # peer lifecycle chaincode install contract.tar.gz Error: failed to endorse chaincode install: rpc error: code = ResourceExhausted des

A good starting point: https://www.udemy.com/course/hyperledger-fabric-network-design-setup/ Is 2.2 but with some adjustments, you can tailor it to 2.4.x version. And follow de docs: https://hyperledg

Hi All, Actually I was testing fabric sdk code. I have this blocklistener: Consumer<BlockEvent> blockListener = blockEvent -> { //some code } //outside //some code while testing it with JUNit testcase

#fabric-sdk-java

@Dave, Yes the NodeOUs are also configured. The logs state that the sub-policies are not being satisfied but there is evidently no such thing in the configtx.yaml which indicates/backs the claim. How

#fabric-kubernetes #hyperledger-fabric #chaincode

@Josh, I would love to see if fabric-operator and k8s-builder lifecycle make my life any easier. Need to find time to test them. Also, will keep my investigation of finding what went wrong with the fa

#fabric-kubernetes #hyperledger-fabric #chaincode