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

Following is the brief overview, the network is running on 2 kubernetes clusters. we have 3 orderers (2 in east US cluster and one in India cluster). we are using skupper to establish connection acros

#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

Thanks Jason for the response. This information is useful. Is there any way to identify application channel(s) that OSN is part of? In Fabric NodeJsSDK, there is "queryChannels" API but it work only f

#raft

For v1.4.x, there is no metric to check the set of active nodes. Usually, it's adequate to simply ensure that all OSNs are alive and have been online for a reasonable period of time to ensure that the

#raft

Wouldn't the doc https://hyperledger-fabric.readthedocs.io/en/release-2.0/operations_service.html help? Regards, Senthil

#raft

Hi, Would really appreciate if anybody has any thought/suggestion regarding my query. Thanks, Shruti

#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

We are indeed doing this on the server side (see attached certificates). If you ever wonder how it can work at all, I have put together a small example environment of what this would look like. Thank

#fabric-orderer #raft #fabric

I don't see why you don't want to specify the intermediate certificate, but - your workaround looks fine to me assuming it works. To do what you want (just specify the root cert and not the intermedia

#fabric-orderer #raft #fabric

Hey Yacov, thanks for your quick reply. As suggested, I have opened a new JIRA (https://jira.hyperledger.org/browse/FAB-17998). Regarding (3.), we have already added the intermediate certificates to t

#fabric-orderer #raft #fabric

Hi. Yes, with FAB-17733 implemented you need to do it in 2 stages- first expand the organizations and then add the new consenter. I guess it's possible to address your problem by speculatively looking

#fabric-orderer #raft #fabric

Hey, we are using an architecture where there is a TLS root CA and each organisation has its own intermediate TLS CA which is an immediate child to the TLS root CA (realized with fabric-ca v1.4.7). We

#fabric-orderer #raft #fabric

Hi, I want to add/remove orderer node in the network. I went through the orderer reconfiguration article. My question is how can the RAFT health be verified. I need it for two purpose: 1. Before addin

#raft

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

The desired solution for this is to allow peers to join channels starting from the latest config block rather than requiring starting from the genesis block. The checkpoint/archive feature will also h

#fabric-orderer #raft #hyperledger-fabric

I replied in the JIRA, I agree with your analysis that adding these parameters to configure the peer's channel joining might be useful. From: chintanr97@... To: fabric@... Date

#fabric-orderer #raft #hyperledger-fabric

@Yacov, I would like to highlight that why aren't we making using of peer CLI command for this? I mean to say that in "peer channel join" command we have an option of specifying the orderer endpoint,

#fabric-orderer #raft #hyperledger-fabric