Date   

Fabric Contributor Meeting - June 29, 2022

David Enyeart
 

Hyperledger Fabric Contributor Meeting

When: Every 4th Wednesday 9am US Eastern, 13:00 UTC

Where: https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

Agendas and Recordings: https://wiki.hyperledger.org/display/fabric/Contributor+Meetings

 

Agenda for June 29, 2022


Project status update – Dave Enyeart

 

Open mic – bring your topics!


Re: Minifab Peer Nodes Questions

Tong Li
 

That is correct in terms of the process. Please see the document in docs directory.


On Jun 28, 2022, at 5:41 PM, Brett Tiller <btiller@...> wrote:


Using minifabric how do I do the following? How do I view the ledger of each peer node to prove that each has received/processed transactions? When I run command "minifab up -s couch.db -e 7400", then command "minifab channelquery"
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd

Using minifabric how do I do the following?

 

  • How do I view the ledger of each peer node to prove that each has received/processed transactions?

 

  • When I run command "minifab up  -s couch.db  -e 7400", then command "minifab channelquery" I can see in the file mychannel_config.json section  channel_group.groups.Application.groups each organization from my spec.yaml file, but not the peers.  However, when I run command "minifab join" to add the peers to the channel I get an error "Error: proposal failed (err: bad proposal response 500: cannot create ledger from genesis block: ledger [mychannel] already exists with state [ACTIVE])" which I understand this message to mean that the peers already exist in mychannel which is not correct.  Am I missing a step?

 

  • Using minifab I want to add/remove individual peers from channels.  Do I need to edit each corresponding channel file then call channel_update, channel_sign to do this step?

 

Thanks,

 

Brett Tiller

Sr. Software Engineer

984-349-4239 (mobile)

btiller@...

 

image001.png

https://www.linkedin.com/company/securboration

 


Minifab Peer Nodes Questions

Brett Tiller
 

Using minifabric how do I do the following?

 

  • How do I view the ledger of each peer node to prove that each has received/processed transactions?

 

  • When I run command "minifab up  -s couch.db  -e 7400", then command "minifab channelquery" I can see in the file mychannel_config.json section  channel_group.groups.Application.groups each organization from my spec.yaml file, but not the peers.  However, when I run command "minifab join" to add the peers to the channel I get an error "Error: proposal failed (err: bad proposal response 500: cannot create ledger from genesis block: ledger [mychannel] already exists with state [ACTIVE])" which I understand this message to mean that the peers already exist in mychannel which is not correct.  Am I missing a step?

 

  • Using minifab I want to add/remove individual peers from channels.  Do I need to edit each corresponding channel file then call channel_update, channel_sign to do this step?

 

Thanks,

 

Brett Tiller

Sr. Software Engineer

984-349-4239 (mobile)

btiller@...

 

https://www.linkedin.com/company/securboration

 


Now: Private Chaincode Lab - 06/28/2022 #cal-notice

Group Notification <noreply@...>
 

Private Chaincode Lab

When:
06/28/2022
8:00am to 9:00am
(UTC-07:00) America/Los Angeles

Where:
https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

Organizer: Marcus Brandenburger bur@...

View Event

Description:
Two of the Hyperleger Labs projects (private data objects and private chain code) are collaborating to develop a "private smart contracts" capability.

Join Zoom Meeting https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Meeting ID: 518 494 7650 Passcode: 475869


networkObj error ------ Error: Error creating wallet database to store membership data: Error: No DB shards could be opened. #couchdb #fabric-kubernetes #hyperledger-fabric #kubernetes #fabric-sdk-node

Vijaya Bhaskar
 

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 create an user and make a txn with my smartcontract, I am facing this issue intermittently with the probability of 40-50% of the times.
the storage fileshare and the cluster are in the same region. it is using azure AKS with 2 nodes of standard_Ds2_v2. each node has 2 vCPUs and 7Gigs of ram.
apart from 2 peer nodes(with couchdb), 2-orderers , a docker dind pod, a CA, not much load is there on the cluster.
the storage is azurefileshare. 

has anyone come across this or have any idea?
can we tweak any configs of db or others?

i am pasting the error log below

Error processing transaction. Error: Error creating wallet database to store membership data: Error: No DB shards could be opened.
  at Request._callback (/usr/src/asset/node_modules/fabric-client/node_modules/nano/lib/nano.js:252:15)
  at Request.self.callback (/usr/src/asset/node_modules/request/request.js:185:22)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at Request.<anonymous> (/usr/src/asset/node_modules/request/request.js:1154:10)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at IncomingMessage.<anonymous> (/usr/src/asset/node_modules/request/request.js:1076:12)
  at Object.onceWrapper (events.js:286:20)
  at IncomingMessage.emit (events.js:203:15)
  at IncomingMessage.EventEmitter.emit (domain.js:448:20)
  at endReadableNT (_stream_readable.js:1145:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)
Done connecting to network.
networkObj error ------ Error: Error creating wallet database to store membership data: Error: No DB shards could be opened.
  at Request._callback (/usr/src/asset/node_modules/fabric-client/node_modules/nano/lib/nano.js:252:15)
  at Request.self.callback (/usr/src/asset/node_modules/request/request.js:185:22)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at Request.<anonymous> (/usr/src/asset/node_modules/request/request.js:1154:10)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at IncomingMessage.<anonymous> (/usr/src/asset/node_modules/request/request.js:1076:12)
  at Object.onceWrapper (events.js:286:20)
  at IncomingMessage.emit (events.js:203:15)
  at IncomingMessage.EventEmitter.emit (domain.js:448:20)
  at endReadableNT (_stream_readable.js:1145:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)
  at dbClient.db.get (/usr/src/asset/node_modules/fabric-client/lib/impl/CouchDBKeyValueStore.js:79:21)
  at Request._callback (/usr/src/asset/node_modules/fabric-client/node_modules/nano/lib/nano.js:245:7)
  at Request.self.callback (/usr/src/asset/node_modules/request/request.js:185:22)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at Request.<anonymous> (/usr/src/asset/node_modules/request/request.js:1154:10)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at IncomingMessage.<anonymous> (/usr/src/asset/node_modules/request/request.js:1076:12)
  at Object.onceWrapper (events.js:286:20)
  at IncomingMessage.emit (events.js:203:15)
  at IncomingMessage.EventEmitter.emit (domain.js:448:20)
  at endReadableNT (_stream_readable.js:1145:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)
Error: Error creating wallet database to store membership data: Error: No DB shards could be opened.
  at Request._callback (/usr/src/asset/node_modules/fabric-client/node_modules/nano/lib/nano.js:252:15)
  at Request.self.callback (/usr/src/asset/node_modules/request/request.js:185:22)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at Request.<anonymous> (/usr/src/asset/node_modules/request/request.js:1154:10)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at IncomingMessage.<anonymous> (/usr/src/asset/node_modules/request/request.js:1076:12)
  at Object.onceWrapper (events.js:286:20)
  at IncomingMessage.emit (events.js:203:15)
  at IncomingMessage.EventEmitter.emit (domain.js:448:20)
  at endReadableNT (_stream_readable.js:1145:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)
  at dbClient.db.get (/usr/src/asset/node_modules/fabric-client/lib/impl/CouchDBKeyValueStore.js:79:21)
  at Request._callback (/usr/src/asset/node_modules/fabric-client/node_modules/nano/lib/nano.js:245:7)
  at Request.self.callback (/usr/src/asset/node_modules/request/request.js:185:22)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at Request.<anonymous> (/usr/src/asset/node_modules/request/request.js:1154:10)
  at Request.emit (events.js:198:13)
  at Request.EventEmitter.emit (domain.js:448:20)
  at IncomingMessage.<anonymous> (/usr/src/asset/node_modules/request/request.js:1076:12)
  at Object.onceWrapper (events.js:286:20)
  at IncomingMessage.emit (events.js:203:15)
  at IncomingMessage.EventEmitter.emit (domain.js:448:20)
  at endReadableNT (_stream_readable.js:1145:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)
192.169.4.98 - S6ESRCB-31QMQXK-MK1NHAP-KNAHEDQ [28/Jun/2022:06:55:59 +0000] "POST /fabric/persona/onboard HTTP/1.1" 400 2820 "-" "-"


Re: unable to fetch config block of system channel from the orderer pod #orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Vijaya Bhaskar
 

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 the map (which should be the admin sign cert from the org admin directory)

Error: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'syschannel': initializing channelconfig failed: could not create channel Consortiums sub-group config: setting up the MSP manager failed: admin 0 is invalid [The identity does not contain OU [CLIENT], MSP: [usisp],The identity does not contain OU [ADMIN], MSP: [usisp]]

2)on adding a consortium, if the error is indicating that the channel does not have capabilities (while deploying chaincode), check the configtx.yaml of the new org in the new consortium. It should include the below part and linked in the consortium definition

Capabilities:
Global: &ChannelCapabilities
V2_0: true
Orderer: &OrdererCapabilities
V2_0: true
Application: &ApplicationCapabilities
V2_0: true


Re: unable to fetch config block of system channel from the orderer pod #orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Vijaya Bhaskar
 

Thanks Satheesh, it worked. I had to specify the relative path for the tls cert, I was specifying the absolute path.

now I am trying to edit system channel and getting the following error. any idea about this?

Error: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'syschannel': initializing channelconfig failed: could not create channel Consortiums sub-group config: setting up the MSP manager failed: admin 0 is invalid [The identity does not contain OU [CLIENT], MSP: [usisp],The identity does not contain OU [ADMIN], MSP: [usisp]]

the steps I followed to edit the configuration is as follows

1) from new configtx.yaml I printed it to json format
configtxgen -printOrg usisp > ./usisp.json
2)convert sys channel config from pb to json and trim it

configtxlator proto_decode --input syschannel.pb --type common.Block | jq .data.data[0].payload.data.config > sys_config.json


3)append new consortium definition

jq -s ‘.[0] * {“channel_group”:{“groups”:{“Consortiums”:{“groups”: {“CEFI”: {“groups”: {“usisp”:.[1]}, “mod_policy”: “/Channel/Orderer/Admins”, “policies”: {}, “values”: {“ChannelCreationPolicy”: {“mod_policy”: “/Channel/Orderer/Admins”,”value”: {“type”: 3,”value”: {“rule”: “ANY”,”sub_policy”: “Admins”}},”version”: “0”}},”version”: “0”}}}}}}’ ./sys_config.json ./usisp.json > modified_config.json


4)convert original and new config to protobuf format
configtxlator proto_encode --input ./sys_config.json --type common.Config --output ./sys_config.pb
configtxlator proto_encode --input ./modified_config.json --type common.Config --output ./modified_config.pb

5)create protobuf with difference between the two

configtxlator compute_update --channel_id syschannel --original ./sys_config.pb --updated ./modified_config.pb --output ./usisp_update.pb


6)add header and tags
configtxlator proto_decode --input ./usisp_update.pb --type common.ConfigUpdate | jq . > ./usisp_update.json

echo ‘{“payload”:{“header”:{“channel_header”:{“channel_id”:”syschannel”, “type”:2}},”data”:{“config_update”:’$(cat ./usisp_update.json)’}}}’ | jq . > ./usisp_update_in_envelope.json

7)convert it back to pb format
configtxlator proto_encode --input ./usisp_update_in_envelope.json --type common.Envelope --output ./usisp_update_in_envelope.pb

8) and submit the update
peer channel update -f ./usisp_update_in_envelope.pb -c syschannel -o orderer0-service:7050 --tls --cafile   /etc/hyperledger/fabric/tls/server.crt

2022-06-26 10:49:33.889 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized Error: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'syschannel': initializing channelconfig failed: could not create channel Consortiums sub-group config: setting up the MSP manager failed: admin 0 is invalid [The identity does not contain OU [CLIENT], MSP: [usisp],The identity does not contain OU [ADMIN], MSP: [usisp]]


I am attaching configtx for new org and cert generation script.

thanks


Re: unable to fetch config block of system channel from the orderer pod #orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

satheesh
 

orderer host need to be fully qualified with domain name. And if orderer is running on a different host, you need to provide that instead of locallhost
along with port number where orderer is listening. Include tls parameter along with orderer ca file location as well.

Regards,
-Satheesh

On Sunday, June 26, 2022 at 10:56:21 AM GMT+5:30, Vijaya Bhaskar <vijaya@...> wrote:


thanks for the reply Satheesh.
I tried the suggestion. the orderer name is just orderer0 so instead of orderer.example.com, I have used just orderer0. (this is correct right?). the error still persists


Re: unable to fetch config block of system channel from the orderer pod #orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Vijaya Bhaskar
 

thanks for the reply Satheesh.
I tried the suggestion. the orderer name is just orderer0 so instead of orderer.example.com, I have used just orderer0. (this is correct right?). the error still persists


Re: unable to fetch config block of system channel from the orderer pod #orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

satheesh
 

you need to pass orderer details as well:
for e.g., -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com

On Saturday, June 25, 2022, 09:29:38 PM GMT+5:30, Vijaya Bhaskar <vijaya@...> wrote:




Hey guys,

overview of the problem
i need to add a new consortium to a an existing HLF setup.For that i need to fetch config block of the system channel and edit it to add the new consortium info.

I am trying to fetch the system channel config block directly from the orderer pod itself using 

"peer channel fetch config sys_config.pb -c syschannel"

I also did try with specifying tls and certs
"peer channel fetch config config_block.pb   -c syschannel --tls --cafile ./tls-cert.pem"
(i have copied the tls file of ca to test directory and trying from there)

I am running into connection refused errors shown below

/var/hyperledger/orderer # peer channel fetch config config_block.pb   -c syschannel --tls --cafile ./tls-cert.pem

Error: error getting deliver client for channel: failed to create deliver client for peer: deliver client failed to connect to 0.0.0.0:7051: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 0.0.0.0:7051: connect: connection refused"

attached is the orderer.yaml file.

Any help will be appreciated
Thanks


unable to fetch config block of system channel from the orderer pod #orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Vijaya Bhaskar <vijaya@...>
 



Hey guys,

overview of the problem
i need to add a new consortium to a an existing HLF setup.For that i need to fetch config block of the system channel and edit it to add the new consortium info.

I am trying to fetch the system channel config block directly from the orderer pod itself using 

"peer channel fetch config sys_config.pb -c syschannel"

I also did try with specifying tls and certs
"peer channel fetch config config_block.pb   -c syschannel --tls --cafile ./tls-cert.pem"
(i have copied the tls file of ca to test directory and trying from there)

I am running into connection refused errors shown below

/var/hyperledger/orderer # peer channel fetch config config_block.pb   -c syschannel --tls --cafile ./tls-cert.pem

Error: error getting deliver client for channel: failed to create deliver client for peer: deliver client failed to connect to 0.0.0.0:7051: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 0.0.0.0:7051: connect: connection refused"

attached is the orderer.yaml file.

Any help will be appreciated
Thanks


Re: rpc error when installing chaincode

satheesh
 

If we build chaincode using below steps repeatedly without removing .tar bundle each time, we can observe increase in bundle file size.
Eventually we encounter rpc error mentioned.

peer lifecycle chaincode package contract.tar.gz --path . --lang golang --label <label>

peer lifecycle chaincode install contract.tar.gz

I am using fabric 2.4.3

Regards,
Satheesh

On Friday, June 24, 2022, 10:56:45 PM GMT+5:30, David Enyeart <enyeart@...> wrote:


Exactly what chaincode build steps are you doing? Are you following one of the samples or docs? What component is the suspected bug in?

 

From: fabric@... <fabric@...> on behalf of satheesh via lists.hyperledger.org <ctsatheesh=yahoo.com@...>
Date: Friday, June 24, 2022 at 12:46 PM
To: Fabric <fabric@...>
Subject: [EXTERNAL] Re: [Hyperledger Fabric] rpc error when installing chaincode

Got resolution from this thread: Hyperledger Fabric Go chaincode size too big - Stack Overflow @Fabric team, Is this not a bug ? If the packaged tar is not removed, repeated builds are increasing the size of tar, eventually failing with this

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd

Got resolution from this thread:

 

 

@Fabric team,

 

Is this not a bug ? 

If the packaged tar is not removed, repeated builds are increasing the size of tar, eventually failing with this error.

 

Regards,

Satheesh

 

 

On Friday, June 24, 2022, 07:19:43 PM GMT+5:30, satheesh via lists.hyperledger.org <ctsatheesh=yahoo.com@...> wrote:

 

 

When installing chaincode in a fabric network, I get below error:

 

# peer lifecycle chaincode install contract.tar.gz

Error: failed to endorse chaincode install: rpc error: code = ResourceExhausted desc = trying to send message larger than max (122921707 vs. 104857600)

 

Strangely this happens even after I shutdown my complete vm and created the network from scratch.

 

Is there anything I am missing ? Any resource issue in the vm ?

Appreciate any pointers.

 

Regards,

Satheesh


Re: unable to fetch config block of system channel from the orderer pod #orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Vijaya Bhaskar
 

I would like to mention that this setup is spread between 2 clusters, I am exposing services between clusters to interconnect using skupper. 

the current running blockchain is on azure central India cluster and the new cluster where a new consortium of one org to be setup in US-east.

I also tried fetching the system config block from the new cluster with appropriate env variables and certs(shown below). 

export FABRIC_LOGGING_SPEC=INFO
export CORE_PEER_ID=orderercli
export CORE_PEER_TLS_ENABLED=true
export ORDERER_CA=/files/crypto-config/ordererOrganizations/orderer/msp/tlscacerts/orderers-ca-service-7054.pem
export CORE_PEER_TLS_CERT_FILE=/files/crypto-config/ordererOrganizations/orderer/orderers/orderer0/tls/server.crt
export CORE_PEER_TLS_KEY_FILE=/files/crypto-config/ordererOrganizations/orderer/orderers/orderer0/tls/server.key
export CORE_PEER_LOCALMSPID=orderer
export CORE_PEER_TLS_ROOTCERT_FILE=/files/crypto-config/ordererOrganizations/orderer/orderers/orderer0/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=/files/crypto-config/ordererOrganizations/orderer/orderers/orderer0/msp
export CORE_PEER_ADDRESS=orderer0-service:7050

and the error I am facing from the new cluster is as below
Error: failed to create deliver client for orderer: orderer client failed to connect to orderer0-service:7050: failed to create new connection: context deadline exceeded
 
 


unable to fetch config block of system channel from the orderer pod #orderer #fabric-orderer #fabric-kubernetes #fabric-questions #grpc

Vijaya Bhaskar
 

Hey guys,
 
overview of the problem
i need to add a new consortium to a an existing HLF setup.For that i need to fetch config block of the system channel and edit it to add the new consortium info.
 
I am trying to fetch the system channel config block directly from the orderer pod itself using 
 
"peer channel fetch config sys_config.pb -c syschannel"
 
I also did try with specifying tls and certs
"peer channel fetch config config_block.pb   -c syschannel --tls --cafile ./tls-cert.pem"
(i have copied the tls file of ca to test directory and trying from there)
 
I am running into connection refused errors shown below
 
/var/hyperledger/orderer # peer channel fetch config config_block.pb   -c syschannel --tls --cafile ./tls-cert.pem

Error: error getting deliver client for channel: failed to create deliver client for peer: deliver client failed to connect to 0.0.0.0:7051: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 0.0.0.0:7051: connect: connection refused"
 
attached is the orderer.yaml file.
 
Any help will be appreciated
Thanks


Re: rpc error when installing chaincode

David Enyeart
 

Exactly what chaincode build steps are you doing? Are you following one of the samples or docs? What component is the suspected bug in?

 

From: fabric@... <fabric@...> on behalf of satheesh via lists.hyperledger.org <ctsatheesh=yahoo.com@...>
Date: Friday, June 24, 2022 at 12:46 PM
To: Fabric <fabric@...>
Subject: [EXTERNAL] Re: [Hyperledger Fabric] rpc error when installing chaincode

Got resolution from this thread: Hyperledger Fabric Go chaincode size too big - Stack Overflow @Fabric team, Is this not a bug ? If the packaged tar is not removed, repeated builds are increasing the size of tar, eventually failing with this

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd

Got resolution from this thread:

 

 

@Fabric team,

 

Is this not a bug ? 

If the packaged tar is not removed, repeated builds are increasing the size of tar, eventually failing with this error.

 

Regards,

Satheesh

 

 

On Friday, June 24, 2022, 07:19:43 PM GMT+5:30, satheesh via lists.hyperledger.org <ctsatheesh=yahoo.com@...> wrote:

 

 

When installing chaincode in a fabric network, I get below error:

 

# peer lifecycle chaincode install contract.tar.gz

Error: failed to endorse chaincode install: rpc error: code = ResourceExhausted desc = trying to send message larger than max (122921707 vs. 104857600)

 

Strangely this happens even after I shutdown my complete vm and created the network from scratch.

 

Is there anything I am missing ? Any resource issue in the vm ?

Appreciate any pointers.

 

Regards,

Satheesh


Re: rpc error when installing chaincode

satheesh
 

Got resolution from this thread:


@Fabric team,

Is this not a bug ? 
If the packaged tar is not removed, repeated builds are increasing the size of tar, eventually failing with this error.

Regards,
Satheesh


On Friday, June 24, 2022, 07:19:43 PM GMT+5:30, satheesh via lists.hyperledger.org <ctsatheesh=yahoo.com@...> wrote:


When installing chaincode in a fabric network, I get below error:

# peer lifecycle chaincode install contract.tar.gz
Error: failed to endorse chaincode install: rpc error: code = ResourceExhausted desc = trying to send message larger than max (122921707 vs. 104857600)

Strangely this happens even after I shutdown my complete vm and created the network from scratch.

Is there anything I am missing ? Any resource issue in the vm ?
Appreciate any pointers.

Regards,
Satheesh


Re: Switching spec.yaml file causes error

email4tong@gmail.com
 

great. good to hear. Minifabric has been really heavily tested. It has been solid for past few years.

On Friday, June 24, 2022, 11:33:45 AM EDT, Brett Tiller <btiller@...> wrote:


Started working now.  I'm not sure if something in memory was causing the issue as rebooting my computer seems to have cleared up this issue - at least for now.


Re: Switching spec.yaml file causes error

Brett Tiller
 

Started working now.  I'm not sure if something in memory was causing the issue as rebooting my computer seems to have cleared up this issue - at least for now.


Block listener #fabric-sdk-java

jeff.jo95z@...
 

hi All,
This is my block listener implemented in fabric sdk:

Consumer<BlockEvent> blockListener = blockEvent -> {

//some lines

}

networkObj.addBlockListener(startBlockNumber, blockListener);

 

once added to the network object this listner object (blockListener) will listen to all the transactions,right?

Is there a chance that this listener object stops listening without getting removed from the network?

 


Why Leader is rotating after every block creation in Hyperledger fabric SBFT 2.3.0 #fabric-orderer #consensus

banerjeeprojat.pb@...
 

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 transactions in a block to 10 rather it is accumulating random number of transactions .
How can we configure batch size in SBFT. any suggestions.

321 - 340 of 11527