I am trying to update system channel configuration to add a new consortium. I have placed the org admin signcert in the map/admincerts folder. the system channel update is failing with the following e

#fabric-kubernetes #signcerts #x509 #organizations #orderer

Hello, I have a HLF running on azure AKS cluster. I have a couchdb acting as a wallet to store the identities of the blockchain admin and users. It is hosted along with all the other pods. when i crea

#couchdb #fabric-kubernetes #hyperledger-fabric #kubernetes #fabric-sdk-node

The system is working now. documenting just in case if any1 in future facing the same errors which I faced. 1)while doing a system channel update if you face the below error, check your admin cert in

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

@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

Your endorsement rule: LifecycleEndorsement: Type: ImplicitMeta Rule: "MAJORITY Endorsement" So, the commit command needs to be submitted to the Majority of peers using --peerAddresses and --tlsRootCe

#fabric-kubernetes #fabric-chaincode

To close the loop on this one... we found that two peers were configured to use a single CouchDB database, and therefore the peers were stepping on each other and getting inconsistency between peer da

#fabric #fabric-peer #fabric-sdk-node #fabric-endorser #fabric-kubernetes

Hi Marek, To add additional peers you don't need to do channel config updates (blockchain config updates). The only important channel config update you have to do is to add the anchor peers of the org

#fabric-sdk-java #fabric-kubernetes

Hi Team, I have a kubernetes setup of HLF2.2 with Golang Chaincode and Nodejs SDK. I am performing load test on the network, when i try with 250 Concurrent thread, it shows unexpectedly chaincode inst

#fabric-sdk-node #fabric-chaincode #docker #fabric-kubernetes #network

Hi, Thank you for reporting your issue. Hyperledger Explorer Group is right place where sharing this issue. This 'connection failure' issue has been reported in hyperledger explorer channel. I'm not s

#fabric-questions #blockchain-explorer #fabric-kubernetes

Hi Community, Whenever we deploy hlf peers in k8s, especially if there are more than 2-3 of them, the "context deadline exceeded" error happens from time to time while calling peer cli commands (like

#fabric-kubernetes #fabric-questions

Thanks Brett and Ross for the open source options. Fabric Automation Framework has support for 2.2 in fabric220 branch, it may not have support for external launcher. Ghan - Thanks for pointing to Zee

#fabric #fabric-kubernetes

After further investigation I can see a chaincode container is being created on one of the EKS nodes. Therefore it's not a container runtime issue. I have inspected the chaincode container which start

#fabric-chaincode #fabric #fabric-kubernetes

Hello, I've been attempting to establish a Fabric network utilizing the Blockchain Automation Framework. I'm currently deploying on a local Kubernetes cluster and am stuck at creation of the CA-server

#fabric-questions #fabric-kubernetes

You can start by having a look at this generic network. https://github.com/lepar/hyperledger-fabric-generic-network Other resources can include the fabric documentation network https://hyperledger-fab

#fabric #fabric-kubernetes #hyperledger-fabric

Hi Suresh, Check this one: https://github.com/APGGroeiFabriek/PIVT It's the most convenient way of running Fabric in Kube as of now. Best, Hakan

#fabric-kubernetes #fabric

I have a k8s cluster which is used to run fabric network，i have isntantiated chaincode successfully and invoke it before ,but recently, i got some error below so how can i solve it? ps：i have run ulin

#fabric-kubernetes #fabric

Hi, I'm currently deploying a network using HLF Fabric 1.4.0 and I've got a problem concerning the instantiation of a chaincode. In fact, the Kubernetes cluster on which I'm deploying it cannot access

#fabric #fabric-kubernetes

Hi I have deployed the fabric-cli in K8s and able to install the go chaincode on peer. But while instantiating the chaincode I am getting below error- Error: could not assemble transaction, err propos

#fabric #fabric-kubernetes

Hi You should attach your orderer and peer logs to give more details because the errors are often blurry in HLF :) You may have an issue inside your configtx.yaml file or in your K8S configuration (e.

#fabric #fabric-kubernetes #fabric-questions

Hi, In Kubernetes, the chaincode container management is currently difficult. You won't be able to easily access it because of the way the container is created. You can access it using two options: 1)

#fabric-kubernetes