search

bft-smart / fabric-orderingservice

Byzantine fault-tolerant ordering service for Hyperledger Fabric
Apache License 2.0
139 stars 57 forks source link

warn info removal #41

Closed Acmefocus closed 5 years ago

Acmefocus commented 5 years ago

[root@FJr-YZ-KVM-205-64 bft_abroad]# docker logs peer1.acacac.com 2018-11-05 13:26:19.200 UTC [msp] getMspConfig -> INFO 001 Loading NodeOUs 2018-11-05 13:26:19.222 UTC [nodeCmd] serve -> INFO 002 Starting peer: Version: 1.2.1 Commit SHA: 15ad406 Go version: go1.10.3 OS/Arch: linux/amd64 Experimental features: true Chaincode: Base Image Version: 0.4.10 Base Docker Namespace: hyperledger Base Docker Label: org.hyperledger.fabric Docker Namespace: hyperledger

2018-11-05 13:26:19.222 UTC [ledgermgmt] initialize -> INFO 003 Initializing ledger mgmt 2018-11-05 13:26:19.222 UTC [kvledger] NewProvider -> INFO 004 Initializing ledger provider 2018-11-05 13:26:19.240 UTC [couchdb] handleRequest -> WARN 005 Retrying couchdb request in 125ms. Attempt:1 Error:Get http://couchdb1.acacac.com:5984/: dial tcp 172.19.0.3:5984: connect: connection refused 2018-11-05 13:26:19.366 UTC [couchdb] handleRequest -> WARN 006 Retrying couchdb request in 250ms. Attempt:2 Error:Get http://couchdb1.acacac.com:5984/: dial tcp 172.19.0.3:5984: connect: connection refused 2018-11-05 13:26:19.617 UTC [couchdb] handleRequest -> WARN 007 Retrying couchdb request in 500ms. Attempt:3 Error:Get http://couchdb1.acacac.com:5984/: dial tcp 172.19.0.3:5984: connect: connection refused 2018-11-05 13:26:20.119 UTC [couchdb] handleRequest -> WARN 008 Retrying couchdb request in 1s. Attempt:4 Error:Get http://couchdb1.acacac.com:5984/: dial tcp 172.19.0.3:5984: connect: connection refused 2018-11-05 13:26:21.294 UTC [kvledger] NewProvider -> INFO 009 ledger provider Initialized 2018-11-05 13:26:21.294 UTC [ledgermgmt] initialize -> INFO 00a ledger mgmt initialized 2018-11-05 13:26:21.295 UTC [peer] func1 -> INFO 00b Auto-detected peer address: 172.19.0.4:7051 2018-11-05 13:26:21.295 UTC [peer] func1 -> INFO 00c Host is 0.0.0.0 , falling back to auto-detected address: 172.19.0.4:7051 2018-11-05 13:26:21.295 UTC [peer] func1 -> INFO 00d Auto-detected peer address: 172.19.0.4:7051 2018-11-05 13:26:21.295 UTC [peer] func1 -> INFO 00e Host is 0.0.0.0 , falling back to auto-detected address: 172.19.0.4:7051 2018-11-05 13:26:21.296 UTC [nodeCmd] serve -> INFO 00f Starting peer with TLS enabled 2018-11-05 13:26:21.298 UTC [eventhub_producer] start -> INFO 010 Event processor started 2018-11-05 13:26:21.299 UTC [nodeCmd] computeChaincodeEndpoint -> INFO 011 Entering computeChaincodeEndpoint with peerHostname: 172.19.0.4 2018-11-05 13:26:21.299 UTC [nodeCmd] computeChaincodeEndpoint -> INFO 012 Exit with ccEndpoint: 172.19.0.4:7052 2018-11-05 13:26:21.300 UTC [nodeCmd] createChaincodeServer -> WARN 013 peer.chaincodeListenAddress is not set, using 172.19.0.4:7052 2018-11-05 13:26:21.302 UTC [sccapi] registerSysCC -> INFO 014 system chaincode cscc(github.com/hyperledger/fabric/core/scc/cscc) registered 2018-11-05 13:26:21.302 UTC [sccapi] registerSysCC -> INFO 015 system chaincode lscc(github.com/hyperledger/fabric/core/scc/lscc) registered 2018-11-05 13:26:21.302 UTC [sccapi] registerSysCC -> INFO 016 system chaincode qscc(github.com/hyperledger/fabric/core/scc/qscc) registered 2018-11-05 13:26:21.305 UTC [gossip/service] func1 -> INFO 017 Initialize gossip with endpoint peer0.acacac.com:7051 and bootstrap set [peer0.acacac.com:7051 peer1.acacac.com:7051] 2018-11-05 13:26:21.307 UTC [msp] DeserializeIdentity -> INFO 018 Obtaining identity 2018-11-05 13:26:21.309 UTC [gossip/gossip] NewGossipService -> INFO 019 Creating gossip service with self membership of { [] [226 1 56 127 94 104 27 118 8 157 22 77 243 200 39 53 103 90 119 91 240 227 246 183 248 177 99 184 57 187 30 24] peer0.acacac.com:7051 } 2018-11-05 13:26:21.309 UTC [gossip/gossip] NewGossipService -> WARN 01a External endpoint is empty, peer will not be accessible outside of its organization 2018-11-05 13:26:21.310 UTC [gossip/gossip] start -> INFO 01b Gossip instance peer0.acacac.com:7051 started 2018-11-05 13:26:21.311 UTC [cscc] Init -> INFO 01c Init CSCC 2018-11-05 13:26:21.311 UTC [sccapi] deploySysCC -> INFO 01d system chaincode cscc/(github.com/hyperledger/fabric/core/scc/cscc) deployed 2018-11-05 13:26:21.312 UTC [sccapi] deploySysCC -> INFO 01e system chaincode lscc/(github.com/hyperledger/fabric/core/scc/lscc) deployed 2018-11-05 13:26:21.313 UTC [qscc] Init -> INFO 01f Init QSCC 2018-11-05 13:26:21.313 UTC [sccapi] deploySysCC -> INFO 020 system chaincode qscc/(github.com/hyperledger/fabric/core/scc/qscc) deployed 2018-11-05 13:26:21.313 UTC [nodeCmd] serve -> INFO 021 Deployed system chaincodes 2018-11-05 13:26:21.315 UTC [discovery] NewService -> INFO 022 Created with config TLS: true, authCacheMaxSize: 1000, authCachePurgeRatio: 0.750000 2018-11-05 13:26:21.315 UTC [nodeCmd] registerDiscoveryService -> INFO 023 Discovery service activated 2018-11-05 13:26:21.315 UTC [nodeCmd] serve -> INFO 024 Starting peer with ID=[name:"abroad" ], network ID=[dev], address=[172.19.0.4:7051] 2018-11-05 13:26:21.315 UTC [nodeCmd] serve -> INFO 025 Started peer with ID=[name:"abroad" ], network ID=[dev], address=[172.19.0.4:7051] 2018-11-05 13:26:21.316 UTC [nodeCmd] func9 -> INFO 026 Starting profiling server with listenAddress = 0.0.0.0:6060 2018-11-05 13:27:21.329 UTC [gossip/comm] func1 -> WARN 027 peer1.acacac.com:7051, PKIid:[226 1 56 127 94 104 27 118 8 157 22 77 243 200 39 53 103 90 119 91 240 227 246 183 248 177 99 184 57 187 30 24] isn't responsive: rpc error: code = Canceled desc = context canceled 2018-11-05 13:27:51.330 UTC [gossip/comm] func1 -> WARN 028 peer1.acacac.com:7051, PKIid:[226 1 56 127 94 104 27 118 8 157 22 77 243 200 39 53 103 90 119 91 240 227 246 183 248 177 99 184 57 187 30 24] isn't responsive: rpc error: code = Canceled desc = context canceled [root@FJr-YZ-KVM-205-64 bft_abroad]# 2018-11-05 13:27:21.329 UTC [gossip/comm] func1 -> WARN 027 peer1.acacac.com:7051, PKIid:[226 1 56 127 94 104 27 118 8 157 22 77 243 200 39 53 103 90 119 91 240 227 246 183 248 177 99 184 57 187 30 24] isn't responsive: rpc error: code = Canceled desc = context canceled

2018-11-05 13:27:51.330 UTC [gossip/comm] func1 -> WARN 028 peer1.acacac.com:7051, PKIid:[226 1 56 127 94 104 27 118 8 157 22 77 243 200 39 53 103 90 119 91 240 227 246 183 248 177 99 184 57 187 30 24] isn't responsive: rpc error: code = Canceled desc = context canceled

hi，
018-11-05 13:27:51.330 UTC [gossip/comm] func1 -> WARN 028 peer1.acacac.com:7051, PKIid:[226 1 56 127 94 104 27 118 8 157 22 77 243 200 39 53 103 90 119 91 240 227 246 183 248 177 99 184 57 187 30 24] isn't responsive: rpc error: code = Canceled desc = context canceled

This warn info how removal ？ Thanks！

jcs47 commented 5 years ago

Unfortunately we also do not know how to get rid of that warning. But as far as we can tell, it does not get in the way of normal execution.

Acmefocus commented 5 years ago

Thanks