启动fabric-samples实例时,在对节点进行排序时发生报错,但是100可正常输出
来源:2-4 fabric尝鲜

FutureNachos
2019-05-02
启动fabric-samples实例时,在对节点进行排序时发生报错,但是100可正常输出,该节点中的日志文件并无报错信息,orderer.example.com中有报错信息:“Error reading from 172.26.0.7:53870: rpc error: code = Canceled desc = context canceled
”,猜想可能时grpc除了问题,但是发现grpc相关的依赖环境都已经安装
报错信息:
===================== Querying on PEER0 on channel 'channel'... =====================
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=DEBUG
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
Attempting to Query PEER0 ...3 secs
Attempting to Query PEER0 ...50 secs
Attempting to Query PEER0 ...54 secs
Attempting to Query PEER0 ...57 secs
Attempting to Query PEER0 ...60 secs
2019-05-02 09:39:11.678 UTC [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-05-02 09:39:11.695 UTC [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
100
!!!!!!!!!!!!!!! Query result on PEER0 is INVALID !!!!!!!!!!!!!!!!
================== ERROR !!! FAILED to execute End-2-End Scenario ==================
orderer日志文件:
2019-05-02 09:37:01.694 UTC [common.deliver] Handle -> WARN 00b Error reading from 172.26.0.7:53798: rpc error: code = Canceled desc = context canceled
2019-05-02 09:37:01.694 UTC [comm.grpc.server] 1 -> INFO 00c streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.26.0.7:53798 error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.call_duration=34.797452ms
2019-05-02 09:37:14.849 UTC [orderer.common.broadcast] Handle -> WARN 00d Error reading from 172.26.0.7:53816: rpc error: code = Canceled desc = context canceled
2019-05-02 09:37:14.849 UTC [comm.grpc.server] 1 -> INFO 00e streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Broadcast grpc.peer_address=172.26.0.7:53816 error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.call_duration=34.949143ms
2019-05-02 09:37:14.849 UTC [common.deliver] Handle -> WARN 00f Error reading from 172.26.0.7:53814: rpc error: code = Canceled desc = context canceled
2019-05-02 09:37:14.849 UTC [comm.grpc.server] 1 -> INFO 010 streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.26.0.7:53814 error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.call_duration=37.519529ms
2019-05-02 09:37:18.027 UTC [orderer.common.broadcast] Handle -> WARN 011 Error reading from 172.26.0.7:53834: rpc error: code = Canceled desc = context canceled
2019-05-02 09:37:18.027 UTC [comm.grpc.server] 1 -> INFO 012 streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Broadcast grpc.peer_address=172.26.0.7:53834 error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.call_duration=40.349239ms
2019-05-02 09:37:18.027 UTC [common.deliver] Handle -> WARN 013 Error reading from 172.26.0.7:53832: rpc error: code = Canceled desc = context canceled
2019-05-02 09:37:18.027 UTC [comm.grpc.server] 1 -> INFO 014 streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.26.0.7:53832 error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.call_duration=43.126774ms
2019-05-02 09:37:22.669 UTC [comm.grpc.server] 1 -> INFO 015 streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=172.26.0.2:39846 grpc.peer_subject="CN=peer0.org2.example.com,L=San Francisco,ST=California,C=US" error="context finished before block retrieved: context canceled" grpc.code=Unknown grpc.call_duration=8.235053724s
2019-05-02 09:38:10.693 UTC [orderer.common.broadcast] Handle -> WARN 016 Error reading from 172.26.0.7:53870: rpc error: code = Canceled desc = context canceled
2019-05-02 09:38:10.693 UTC [comm.grpc.server] 1 -> INFO 017 streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Broadcast grpc.peer_address=172.26.0.7:53870 error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.call_duration=46.954841737s
写回答
1回答
-
亲,你好。两个问题,1,你使用的应该是1.4版本,一些特性会跟1.0有些不同;2,我觉得这个警告是正常的,这是因为客户端跟orderer的连接断开了,所以orderer输出一个警告告诉开发者有链接断开。一般我感觉不影响使用。祝你学习愉快!
022019-05-23
相似问题