Hi, Based on the error messages, I suspect that the file ledger directory(FileLedger.Location = "/var/hyperledger/production/orderer") is corrupted or not initialized completely. Please check whether

#raft #tls #fabric-orderer #kubernetes

Hi All, Using BAF, I had a hyperledger fabric network v2.2.0 which has 11 orgs, 5 orderers and 5 channels. Org1 is a part of all the channels. Other than that each channel has 2 individual orgs. So to

#raft #configtxgen #hyperledger-fabric

After the expiration of tls and admin certs of the peer and orderers in the network, I'm trying to rotate the tls certificates of the orderer by making config updates in all the channels of which the

#fabric-ca #fabric-orderer #hyperledger-fabric #raft #tls

Not in Fabric v1.4.x. There is a recently approved RFC for an Orderer Channel Participation API. https://github.com/hyperledger/fabric-rfcs/pull/24 This new API will enable easier and more direct mana

#raft

oh I see now why it works, because tls.X509KeyPair https://github.com/hyperledger/fabric/blob/master/internal/pkg/comm/server.go#L74 iterates over the PEM and just put multiple certificates into the t

#fabric-orderer #raft #fabric

One quick question. What would happen in the scenario where peer is able to fetch the blocks of the channel from the genesis block orderers? I mean to say, how would the peer identify the Orderer Orga

#fabric-orderer #raft #hyperledger-fabric

I am adding a new orderer node by following the steps mentioned here: Reconfiguring the RAFT cluster. In the 5th step we can see that following is mentioned: Now, I went through a few options to perfo

#hyperledger-fabric #raft #fabric-orderer

Raft orderers only use the endpoints in that section for replication, but when exchanging consensus messages they use the host and port in the consenters section (the one with the TLS certificates). F

#fabric-orderer #hyperledger-fabric #raft

If you send a steady flow of updates for the same key, you will always have some transactions in flight (endorsement or ordering phase) while earlier transactions are committing on peers. Since the la

#hyperledger-fabric #fabric-chaincode #consensus #raft

I am trying to deploy HLF 1.4.3 on AWS EKS. I wanted to write domain name in configtx.yaml As domain name dont have port but Port is mandatory while generation of genesisi block. Any workaround?

#raft #configtxgen

Hi, Please find the following logs attached: 2-orderer-logs-leader-stopped: logs of the two online orderers working-orderer-logs: partial logs of all the orderers Note: I have two hosts and one of the

#raft #consensus

Hi members, I built my HLF network based on v2.0 test-network and have 3 instances in GCP. - Instance 1 : cli, peer0.meters, peer1.hq, ca.org1, orderer0 - Instance 2 : peer0.hq, peer1.meters, orderer1

#raft #tls #fabric #fabric-chaincode #fabric-orderer

Hi, We had the same issue in our network. To solve it, we found a way to persist the following folder in each orderer: /var/hyperledger/production/orderer/etcdraft Without it restored after a restart,

#fabric-orderer #raft #fabric

this is not a "bug", this is a natural product of messages being gossiped out of order which is how gossip works. This is a warning, not an error... if you see it repeatedly only then you should be wo

#hyperledger-fabric #configtxgen #raft

Hi, We are testing HLF 1.4.3 in raft configuration with 2 raft orderer nodes and 2 peer nodes. Here's some info: - TLS enabled (peer and orderers) - was able install, instantiate and query the chainco

#hyperledger-fabric #network #tls #raft

I have a question. Can orderers read all the transactions passing through them even from the channels of which their organization is not a part of If yes, then is there any solution to implement compl

#hyperledger-fabric #raft #fabric-questions #fabric-orderer

Hi suresh, Best thing would be store them into an external secured storage system like into a Private IPFS or azure. In case of IPFS the hash is generated which can be stored in fabric to access the p

#fabricca #fabric-ca #raft #couchdb #fabric

Hello everyone! Recently, I encountered a problem in setting up a Fabric environment in a virtual machine. I followed the steps on https://hyperledger-fabric-ca.readthedocs.io/en/latest/operations_gui

#raft #fabric-ca #fabric-orderer

Done :) Though I don't expect it to be solved anytime soon :( Thanks anyway, glad to see I'm not the only one in need of this

#hsm #raft

We have 5 orderers. We stop one of them and start it again. We get the following error. Any idea? 2019-12-05 09:27:01.096 UTC [orderer.consensus.etcdraft] becomeFollower -> INFO 057 1 became follower

#raft