如何修复 Hyperledger Fabric 中的“FAILED to execute End-2-End Scenario”？

Question

我正在尝试运行此处提供的 Fabric 示例：https : //github.com/hyperledger/fabric-samples/tree/release-1.2/first-network

我按照 Fabric 文档的所有说明进行操作：https://hyperledger-fabric.readthedocs.io/en/release-1.2/build_network.html ，但遇到错误“无法执行 End-2-End Scenario”。以下是我进入./byfn.sh up终端后的输出。

我什至没有在 google 和 stackoverflow 上发现任何类似的问题

./byfn.sh up
Starting for channel 'mychannel' with CLI timeout of '10' seconds and CLI delay of '3' seconds
Continue? [Y/n] Y
proceeding ...
LOCAL_VERSION=1.2.0
DOCKER_IMAGE_VERSION=1.2.0
Starting peer1.org1.example.com ... done
Starting orderer.example.com    ... done
Starting peer0.org2.example.com ... done
Starting peer1.org2.example.com ... done
Starting peer0.org1.example.com ... done
Starting cli                    ... done

 ____    _____      _      ____    _____ 
/ ___|  |_   _|    / \    |  _ \  |_   _|
\___ \    | |     / _ \   | |_) |   | |  
 ___) |   | |    / ___ \  |  _ <    | |  
|____/    |_|   /_/   \_\ |_| \_\   |_|  

Build your first network (BYFN) end-to-end test

Channel name : mychannel
+ peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
Creating channel...
+ res=1
+ set +x
Error: failed to create deliver client: orderer client failed to connect to orderer.example.com:7050: failed to create new connection: context deadline exceeded
!!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!!
========= ERROR !!! FAILED to execute End-2-End Scenario ===========

ERROR !!!! Test failed

问题的根源是什么，我应该如何解决？

Answer 1

Error: failed to create deliver client: orderer client failed to connect to orderer.example.com:7050: failed to create new connection: context deadline exceeded

此错误表明对等点无法解析/连接到 orderer.example.com:7050 。尝试通过以下方式检查所有容器

docker ps -a

这将向您显示所有正在运行的容器和已退出的容器，您可以通过以下方式检查容器日志

docker logs your_container_name

如果您以前的容器在同一网络中运行或停止，并且您忘记将其删除，那么您可以尝试关闭整个网络，然后重新启动，也可能会发生这种情况。

./byfn.sh down
./byfn.sh up