Hyperledger Fabric:错误:无法组装事务:ProposalResponsePayloads不匹配 [英] Hyperledger Fabric: Error: could not assemble transaction: ProposalResponsePayloads do not match

问题描述

尝试调用链码时，如何解决以下错误?

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\"]" > ...

当尝试使用peer chaincode invoke

推荐答案

检查是否已在peer chaincode invoke命令所针对的所有对等节点上安装了链码.这是最可能导致此错误的原因.

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:

• 您修改了链码，而不是安装新版本并升级链码，而是试图变得聪明，并用新文件覆盖链码，以为Fabric不会注意到.

• 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.

如果在目标对等节点上没有运行链式代码容器并且在尝试实例化容器或由于其他原因导致实例化失败的对等节点上找不到Docker守护程序时，也会发生这种情况

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

发生此错误的另一个原因是，如果某些对等节点使用LevelDB，而其他对等节点使用CouchDB

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.

这篇关于Hyperledger Fabric:错误:无法组装事务:ProposalResponsePayloads不匹配的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！