You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?
I want to use caliper to test the performance of the fabric network I built, but I'm having some trouble. When testing the creation of transactions with caliper, some errors are often reported randomly.
Please provide the error logs and their surroundings.
2023.03.13-23:01:09.037�[31m error�[39m [caliper] [connectors/v2/fabric-gateway] Failed to perform submit transaction [CreateRequest] using arguments [The 2 Message_13,444444444444,152601199604262615,123123123126,123123123135,152602200211117775], with error: Error: No valid responses from any peers. Errors:
peer=undefined, status=grpc, message=Peer endorsements do not match
at newEndorsementError (/home/jimson/go/hyperledger/eightNode/caliper-workspace/node_modules/fabric-network/lib/transaction.js:49:12)
at getResponsePayload (/home/jimson/go/hyperledger/eightNode/caliper-workspace/node_modules/fabric-network/lib/transaction.js:17:23)
at Transaction.submit (/home/jimson/go/hyperledger/eightNode/caliper-workspace/node_modules/fabric-network/lib/transaction.js:212:28)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async LegacyV2FabricGateway._performGatewayTransaction (/home/jimson/go/hyperledger/eightNode/caliper-workspace/node_modules/@hyperledger/caliper-fabric/lib/connector-versions/v2/fabric-gateway.js:489:26)
at async LegacyV2FabricGateway.sendRequests (/home/jimson/go/hyperledger/eightNode/caliper-workspace/node_modules/@hyperledger/caliper-core/lib/common/core/connector-base.js:78:28)
at async CreateMessageWorkload.submitTransaction (/home/jimson/go/hyperledger/eightNode/caliper-workspace/workload/create.js:36:9)
Please provide your benchmark configuration file content, if possible.
I found problem. My chaincode using golang. I used a function to quire time like time.Now().Unix(),So the time-out make the Peer endorsements do not match. I use outside timestamp function in javascript to take place chaincode. It works.
Firstly, I would recommend not using caliper 0.4.2 and use caliper 0.5.0 instead.
Secondly, caliper is outputting the reason for the failures
Failed to perform submit transaction [CreateRequest] using arguments [The 2 Message_13,444444444444,152601199604262615,123123123126,123123123135,152602200211117775], with error: Error: No valid responses from any peers. Errors:
peer=undefined, status=grpc, message=Peer endorsements do not match
Your endorsements received from 2 or more peers don't match. That means your chaincode is non-deterministic and so you have a problem with your chaincode implementation. Please search google and refer to the hyperledger fabric documentation about chaincode and the fact it must be deterministic. Examples of a chaincode that isn't deterministic would be
The chaincode generates a date object
The chaincode generates a random number
So this isn't an issue with caliper or fabric but how your chaincode is implemented
Firstly, I would recommend not using caliper 0.4.2 and use caliper 0.5.0 instead. Secondly, caliper is outputting the reason for the failures
Failed to perform submit transaction [CreateRequest] using arguments [The 2 Message_13,444444444444,152601199604262615,123123123126,123123123135,152602200211117775], with error: Error: No valid responses from any peers. Errors:
peer=undefined, status=grpc, message=Peer endorsements do not match
Your endorsements received from 2 or more peers don't match. That means your chaincode is non-deterministic and so you have a problem with your chaincode implementation. Please search google and refer to the hyperledger fabric documentation about chaincode and the fact it must be deterministic. Examples of a chaincode that isn't deterministic would be
The chaincode generates a date object
The chaincode generates a random number
So this isn't an issue with caliper or fabric but how your chaincode is implemented
Thank you, Its my chaincode problem.not caliper. And again, thank you for your reply!
Which Caliper version are you using?
V0.4.2
Which Node.JS version are you using?
v16.15.0
Which operating system are you using?
Ubuntu 20.04 LTS
Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?
I want to use caliper to test the performance of the fabric network I built, but I'm having some trouble. When testing the creation of transactions with caliper, some errors are often reported randomly.
What was the observed incorrect behavior?
SET function always has unsuccess
caliper.log
Please provide the error logs and their surroundings.
Please provide your benchmark configuration file content, if possible.
Please provide your network configuration file content, if possible.
Please provide your workload module content, if possible.
Please provide any additional information you deem relevant to the error.
thanks a lot
The text was updated successfully, but these errors were encountered: