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

Sometimes I got this ORDERER error in java SDK - Caused by: java.util.concurrent.ExecutionException: java.lang.Exception: Channel ndmcgovtchannel failed to place transaction 5f708e4f1c0bf98d1da3afa5a7

#fabric-sdk-java #fabric-orderer #channel

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

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

Based on this comment about BlockValidation in configtx.yaml, you might want to double check if "SMARTBFT" is a valid Rule for BlockValidation at path Channel/Orderer: # BlockValidation specifies what

#fabric-orderer #policies

Hi , I am using HLF 2.2.3 and node sdk for sending concurrent transactions . i have disabled the concurrency limit of endorser in core.yaml to test High throughput, after sending many transactions in

#fabric-orderer #fabric-peer

You can try to telnet to the host:port, either from outside or from within the container.

#fabric-orderer

Upma

#channel #fabric-ca #fabric-peer #fabric-orderer

Hello, i have a question about peer and ordering orgs. In my scenario i have 1 tls CAs, 3 root CAs that have to manage the ordering services and 21 intermediate (7 for every root). Reading the docs i

#fabric-orderer #fabric-peer

I'm not very familiar with BAF. Is NodeOU enabled on the channels? https://hyperledger-fabric.readthedocs.io/en/release-2.2/msp.html?highlight=nodeou#organizational-units

#channel #configtxgen #fabric-peer #fabric-questions #fabric-orderer

The channels are not available in orderer1 since the TLS certificate for the orderer has been replaced with the new certificate. Since the timeshift is still active, the new certificate is in the futu

#fabric #fabric-orderer #hyperledger-fabric

Hi Yacov, Thanks, I saw the commits with that change so I tried that first, I generated the new certs using the same private keys and uploaded them without changing the configuration but I don't know

#consensus #configtxgen #fabric-orderer

Just in case if this helps: [FAB-18384] admin certs and tls certs expired after 1 year - Hyperledger JIRA Regards, Satheesh

#fabric #fabric-peer #fabric-orderer #fabric-ca #fabricca

Hello; On Approach #2.. > Do we still need to install the chaincode in the peer, if we are running the peer in dev mode inside a docker container ? No, the approach you are doing is basically correct;

#fabric #configtxgen #fabric-peer #fabric-orderer

THE PROBLEM HAS BEEN SOLVED. Thanks to @Kavin above for his help. Just in case it is useful to anyone out there, if you want to keep your local images when shutting down the local hlf network and have

#fabric-orderer #fabric-peer #orderer #organizations #channel

Hello, I'm currently working on a project with three organizations and an orderer. So in order to do this, I created a new network, with its own configuration files and with a script that sets up ever

#docker #fabric-ca #fabric-orderer #orderer #organizations

You can find docker file of Fabric peers here: https://github.com/hyperledger/fabric/blob/release-1.4/images/peer/Dockerfile.in Best regards, Artem Barger.

#fabric #fabric-peer #fabric-orderer #fabric-ca

Hi zhuxy Please see my comments inline. Thanks! Different sections are convenient to have corresponding policy controls on orderer orgs and app orgs. For example, you can set one default policy for or

#fabric-orderer #fabric

Good day, Thank you for your reply! And apologies for my late reply. For the TLS certificates, I used the registerEnroll.sh script that is included in the test-network files (in /test-network/organiza

#hyperledger-fabric #fabric-sdk-node #fabric-orderer #fabric-peer

Hi Ramesh, 1: In my situation I had all the certs expired, both admin (peer and orderers), TLS and MSP certs. 2: You need to sign with old certs in orderer tu run the update, if I recall correctly the

#fabric-questions #fabric-orderer #signcerts #fabric