I have got the hyperledger fabric blockchain deployed on kubernetes in namespace: hfl-fabric and the client app using fabric-sdk-go is in another namespace: hlf-app. I am using the gateway api to

I figure out the issue with this. If anyone encounter the same problem then this might help. Make sure that you're copying the META-INF folder in the external build and release scripts. You can refer

https://hyperledger-fabric.readthedocs.io/en/release-2.2/kafka_raft_migration.html?highlight=stand%20by%20mode#entry-to-maintenance-mode Good luck. Carlos, I notice that you work @SERPRO GOV BR. I am

Hi David, Didn't know about this STATE_MAINTENANCE mode, thanks, I will keep this trick up my sleeve. By now, at weekends the network doesn't have any transactions, so we will use this

Hi Carlos. You may try to do it putting your network in STATE_MAINTENANCE mode. Please, let me know when you correct this problem. What was your workaround. Best regards. David David Faulstich Diniz

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

Hyperledger Fabric fix releases v2.2.4, v2.3.3, and Fabric CA v1.5.2 are now available. See details of the fixes in the release

The error seems to be quite self explanatory. Did you get the approvals from enough orgs (default is majority)? You can look at some helping commands in the docs -

Hi Carlos, You will have to experiment a bit with couchdb compaction configurations in your set up and evaluate what works best for your workload. As far as I recall, the default config is automatic

Thanks, Manish, The virtual server has 4 vCPUs, 8 GB of RAM and plenty of disk space (at 30% usage). It is running just 3 containers: peer, couchdb and cadvisor. Would that be

I am running a network with 3 peer orgs with two peers each 1 orderer org with 3 orderers PROBLEM FACED While committing the chaincode getting an error txid

---------- Forwarded message --------- From: Manish Sethi <manish.sethi@...> Date: Wed, Sep 8, 2021 at 4:27 PM Subject: Re: [Hyperledger Fabric] Channel snapshot failed on conclusion To: Carlos

Answers inline below. Also please take a look at the Key Concepts documentation that includes many of these answers - https://hyperledger-fabric.readthedocs.io/en/latest/key_concepts.html 1. Every

Assuming you are using the same credentials for each Org in multiple channels and using the same policies (reader/writer), then the same user credential will have access to those channels.

Hi, I have setup fabric network with 5 Orderers, and two Orgs with two pears each. Developed a chain code and deployed successfully. Please clarify the following things. 1. Every Orderer node

Hello all, After almost 10 hours of waiting for a snapshot completion, there is this error on the peer log and nothing in 'completed' neither in 'temp' dirs of 'snapshots' folder.

Hello, Has anyone experience in deploying and maintaining HLF with BAF? What is your opinion or thoughts on that? Should I try it? I have seen here that is suggested as

Voting for this year's Technical Steering Committee election starts on October 1 and closes on October 15. We ask that everyone take a couple of minutes now to confirm you are showing up correctly in

Private Chaincode Lab When: 09/07/2021 8:00am to 9:00am (UTC-07:00) America/Los Angeles Where: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Organizer: Marcus

You could do a post-check in the client application side, before submitting the transaction for ordering. For example open up the proposal response returned from the chaincode invocation and inspect