阿里云ubuntu16.04运行Fabric1.2 e2e_cli
参加阿里云天池区块链比赛,在kubernetes运行fabric,但是总是遇到读不到块的问题,后打算,直接在阿里云服务器上先启动fabric网络,example中first network成功启动,但是运行e2e_cli时,遇到了一大堆坑
不得不说,现在kubernetes和fabric都在快速变化,总是有各种问题,需要踩坑解决
愿,坑越来越少
Q1:阿里云CES服务器 WARNING: Connection pool is full, discarding connection: localhost
- A:这是在阿里云CES服务器上遇到的,不影响运行结果,尚不清楚原因
Q2:阿里云CES上运行e2e_cli,Ordering Service is not available
A:
- 对docker-compose file中orderer的文件挂在配置加上引号
- 注释阿里云服务器上/etc/resconv.conf中的option选项
- 对于所有的fabric容器,加上GODEBUG=netdns=go环境变量
ref:
Q3:org3查询出现Error: error endorsing query: rpc error
- A: fabric1.2 bug,在e2e_cli/configtx.yaml org3配置下,添加’Org3MSP.member’
- ref:
Q4:CRIT 06c Error creating configtx, Unexpected key Capabilities
orderer.example.com | 2018-09-11 12:25:00.079 UTC [orderer/multichain] newLedgerResources -> CRIT 06c Error creating configtx manager and handlers: Error deserializing key Capabilities for group /Channel: Unexpected key Capabilities orderer.example.com | panic: Error creating configtx manager and handlers: Error deserializing key Capabilities for group /Channel: Unexpected key Capabilities orderer.example.com | orderer.example.com | goroutine 1 [running]: orderer.example.com | panic(0xb31bc0, 0xc42000db00)
- A: 之前因为Orderer服务失败的问题,重新拉取1.0.0版本的镜像,但是代码还是1.2,将镜像换回1.2,按Q2、Q3即可成功启动fabric1.2网络
以下是在阿里云CES ubuntu16.04上运行fabric1.2 e2e_cli网络遇到的各种问题及解决办法,最终all good
Q.1:Ordering Service is not available
Error: failed to create deliver client: orderer client failed to connect to orderer.example.com:7050: failed to create new connection: context deadline exceeded !!!!!!!!!!!!!!! Ordering Service is not available, Please try again ... !!!!!!!!!!!!!!!!
查询运行的容器发现没有orderer容器,但orderer单独拿出来作为orderer-test.yaml,查找问题