fabric链码无法运行成功

最新推荐文章于 2023-09-14 18:58:13 发布

原创最新推荐文章于 2023-09-14 18:58:13 发布 · 1.1k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#fabric #运维

区块链 fabric 同时被 2 个专栏收录

4 篇文章

订阅专栏

程序员日志

2 篇文章

订阅专栏

在Hyperledger Fabric联盟链环境中，遇到approve超时、store状态异常以及transaction commit被peer拒绝的问题。尝试清理网络并谨慎操作后，问题依然存在。错误日志显示可能存在的键版本冲突和MVCC_READ_CONFLICT，导致交易无效。寻求解决方案以根本解决网络稳定性问题。

现在已经不知道到底是为什么了，并且会出现很多莫名其妙的事情。比如approve超时，只有store在第二天会exited。

在controlCC中，

stub.putStringState(name,serialize);

putStringState似乎总是无法正确运行。

清理网络，每一步谨慎的来一次。

controlCC可以了，store不行了

bash-5.1# peer chaincode invoke -o orderer.example.com:7050 --ordererTLSHostnameOverride orderer.example.com --tls --cafile ${PWD}/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel --name store --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles ${PWD}/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:8051 --tlsRootCertFiles ${PWD}/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt --peerAddresses peer0.org3.example.com:9051 --tlsRootCertFiles ${PWD}/crypto/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/ca.crt -c '{"function":"createStore","Args":["cli0_epoch0","QmYtdsPA9BoaEyZLRbqBbvequaihRh9qdw22zZo5EkoQbE"]}'
Error: endorsement failure during invoke. response: status:500 message:"Undefined contract method called"
这个问题真的不知道为啥。

现在的问题是，我不知道问题是啥，就很奇怪，之前都是通过清理网络重启解决的，但是治标不治本。

Exception in thread "main" org.hyperledger.fabric.gateway.ContractException: Transaction commit was rejected by peer peer0.Org1.example.com
   at org.hyperledger.fabric.gateway.impl.commit.CommitHandlerImpl.onTxEvent(CommitHandlerImpl.java:104)
   at org.hyperledger.fabric.gateway.impl.commit.CommitHandlerImpl.access$000(CommitHandlerImpl.java:26)
   at org.hyperledger.fabric.gateway.impl.commit.CommitHandlerImpl$1.acceptCommit(CommitHandlerImpl.java:33)
   at org.hyperledger.fabric.gateway.impl.event.Listeners.lambda$transaction$7(Listeners.java:122)
   at java.base/java.lang.Iterable.forEach(Iterable.java:75)
   at org.hyperledger.fabric.gateway.impl.event.Listeners.lambda$fromTransaction$0(Listeners.java:32)
   at org.hyperledger.fabric.sdk.Channel.lambda$null$12(Channel.java:5974)
   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
   at java.base/java.lang.Thread.run(Thread.java:831)

2022-05-08 12:22:12.368 UTC 0f0e WARN [validation] validateKVRead -> Transaction invalidation due to version mismatch, key in readset has been updated in a prior transaction in this block namespace=control4 key=Z readVersion="{BlockNum: 413, TxNum: 0}"
2022-05-08 12:22:12.368 UTC 0f0f WARN [validation] validateAndPrepareBatch -> Block [422] Transaction index [1] TxId [03e645f72a0c1d16089a70b250bebb4ab318eeb62ade8144b515367f60fdcd00] marked as invalid by state validator. Reason code [MVCC_READ_CONFLICT]