I am using Hyperledger fabric 1.4 with raft as ordering service. whenever I tried to instantiate the chaincode, the command get stucked and after waiting so long there is no output.
I am getting the warning like rejecting the delivering request for- because of constenser error.
please help me to fix this out.
below here image is attached that depict the error
Logs orderer
Related
I am quite new to Hyperledger Fabric. I have strictly followed all Prerequisites in addition to other steps to run the test-network. I am facing the following error:
**
(Error: endorsement failure during query. response: status:500
message:"make sure the chaincode fabcar has been successfully defined
on channel mychannel and try again: chaincode fabcar not found" ).
**
As inquired, the version of hyperledger fabric is as follows:
Please note that the solution here did not solve my problem. Furthermore, digging more on it I also note that I can not get any response if I try to check peer chaincode list --installed . I even tried the accepted answer but its not working. Kindly please guide me.
I would add to Kartik's question, are you using the test network to get started? If not, I would start with the tutorial first and if you get stuck, share the logs and we will do our best to help.
Im trying to create a channel using node SDK and get the following error.
Failed to evaluate transaction: Error: Orderer with name:orderer.example.com not found
A wild guess but you chang the exapmle to example.
Apart from that, the Error means the SDK cannot communicate with the Orderer. Either it is not up or it is known by a different url.
The orderer is not up.
The best thing you can do it to set the logging level for the orderer to DEBUG and check is logs.
It is crashing for some reason, you can see the logs and try to understand what happens.
If you post here the logs I'm happy to hlelp you.
what are the steps to troubleshoot below error when trying to invoke a chaincode?
Error: could not assemble transaction: ProposalResponsePayloads do not match - proposal response: version:1 response:<status:200 payload:"[\"00000\"]" > ...
we get this error when trying to invoke a chaincode using peer chaincode invoke
#morpheus: Has answered it excellently:
So I thought I will add to the above list of possible reasons:
I had by mistake added something like getting the current timestamp, and was using this for capturing the event date. This led to the different transaction responses by the endorsers, thus leading to the Response Payload not matching. The whole point to remember is that the result of execution should be deterministic as it is going to be run on all of the selected endorsing peers.
So use ctx.GetStub().GetTxTimestamp() for capturing the event time. This is the time when the transaction began and it will be constant across the endorser executions.
Check that you have installed the chaincode on all the peers your peer chaincode invoke command is targetting. That is the most likely cause of this error.
Other ways this error can occur:
You modified your chaincode and instead of installing a new version and upgrading the chaincode, you tried to be smart and overwrite the chaincode with the new file thinking that Fabric would not notice.
It can also happen if there is no chaincode container running on target peer and Docker daemon cannot be found on the peer node when it tries to instantiate a container or instantiation fails for some other reason
Another reason why this error can happen is if some peer nodes are using LevelDB and others are using CouchDB
The error itself originates from here. The first step to debug this error is to invoke the chaincode individually one-by-one on one peer node at a time.
Another reason that I forgot to check is using storing randomly generated values.
I never used random "Id" until now and didn't notice that it leads to ENDORSEMENT_MISMATCH
I have a hyperledger fabric network setup in multiple servers and I successfully installed chaincode in different peers(peer0.org1.com and peer0.org2.com) of different organizations.
When I call the chaincode with putState(key,value) from peer0.org1.com I am able to commit the change but when I call the same chaincode from peer0.org2.com putstate(key, value) is failing with endorsement error.
This might be because you didn't include peer0.org2.com in the endorsement policy while installing the chaincode.
Ex: Include OR/AND ('ORG1MSP.member','ORG2MSP.member') in chaincode installation step
I hope this solves the issue
I started a new composer network (two org setup), i.e. a second chaincode (one was already installed and running). I installed it and while starting, couple of chaincode containers were stuck while downloading node modules, and the command to start chaincode was timed out. To start again I removed the chaincode containers and tried to start again. But I am getting error : status: 500, message: chaincode exists.
That message from hyperledger fabric means that the chaincode has already been instantiated, so you do not need to invoke composer network start again. Any request you send to a peer will try to bring up a chaincode container to process that request if there isn't one already started.
composer network start sends the instantiate transaction to peers and as such the peers need to simulate the request proposal and to do that it needs a chaincode container so goes through the process of creating a chaincode container image and chaincode container to execute the request (but any transaction proposal causes the same process to be followed). So long as the instantiation policy is satisfied (and the default I believe is for 1 successful instantiation proposal) then the chaincode is then defined as instantiated.