2017-08-24 63 views
1

我試圖安裝從http://hyperledger-fabric.readthedocs.io/en/latest/write_first_app.html錯誤啓動hyperledger fabcar示例應用程序

我得到類似的錯誤,以張貼在這裏提到的hyperledger織物樣本應用程序:hyperledger fabric fabcar error

2017-08-24 07:47:16.826 UTC [grpc] Printf -> DEBU 005 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: Error while dialing dial tcp 172.18.0.5:7051: getsockopt: connection refused"; Reconnecting to {peer0.org1.example.com:7051 <nil>} 
Error: Error getting endorser client channel: PER:404 - Error trying to connect to local peer 

下面是日誌docker logs peer0.org1.example.com, apperantly peer無法連接到couchdb

2017-08-24 07:47:03.728 UTC [couchdb] handleRequest -> DEBU 011 HTTP Request: GET/HTTP/1.1 | Host: couchdb:5984 | User-Agent: Go-http-client/1.1 | Accept: multipart/related | Accept-Encoding: gzip | | 
2017-08-24 07:47:04.073 UTC [couchdb] handleRequest -> WARN 012 Retrying couchdb request in 125ms. Attempt:1 Error:Get http://couchdb:5984/: dial tcp 109.234.109.83:5984: getsockopt: connection refused 
2017-08-24 07:47:04.199 UTC [couchdb] handleRequest -> DEBU 013 HTTP Request: GET/HTTP/1.1 | Host: couchdb:5984 | User-Agent: Go-http-client/1.1 | Accept: multipart/related | Accept-Encoding: gzip | | 
2017-08-24 07:47:04.385 UTC [couchdb] handleRequest -> WARN 014 Retrying couchdb request in 250ms. Attempt:2 Error:Get http://couchdb:5984/: dial tcp 109.234.109.77:5984: getsockopt: connection refused 

我可以在端口上看到偵聽套接字5984

從搬運工EXEC - 它的CouchDB的bash 泊塢窗EXEC - 它的CouchDB的bash

[email protected]:~$ netstat -ntulpa 
Active Internet connections (servers and established) 
Proto Recv-Q Send-Q Local Address   Foreign Address   State  PID/Program name 
tcp  0  0 0.0.0.0:5984   0.0.0.0:*    LISTEN  6/beam.smp 
tcp  0  0 127.0.0.1:5986   0.0.0.0:*    LISTEN  6/beam.smp 
tcp  0  0 127.0.0.11:43471  0.0.0.0:*    LISTEN  - 
udp  0  0 127.0.0.11:52081  0.0.0.0:*       - 

從命令外殼沒有搬運工人

# netstat -ntulpa | grep 5984 
tcp6  0  0 :::5984     :::*     LISTEN  12877/docker-proxy 

爲什麼對不能夠連接到CouchDB的?

+0

如果你的主機上運行的「平CouchDB的」會發生什麼? –

+0

是的,我能ping通couchdb – Pras

+0

這可能是問題所在。似乎您的主機已設置爲自動執行某種類型的DNS搜索並解析未知的主機名。將發佈一個可能的解決方案作爲 –

回答

5

根據評論,我認爲您的主機系統配置爲使用自動解析未知主機名的DNS搜索域。您可能需要修改基本網絡/泊塢窗,compose.yml,並添加dns_search: .的配置價值,爲同行:

peer0.org1.example.com: 
    container_name: peer0.org1.example.com 
    image: hyperledger/fabric-peer:x86_64-1.0.0 
    dns_search: . 
    environment: 
     - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock 
     - CORE_PEER_ID=peer0.org1.example.com 
     - CORE_LOGGING_PEER=debug 
     - CORE_CHAINCODE_LOGGING_LEVEL=DEBUG 
     - CORE_PEER_LOCALMSPID=Org1MSP 
     - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/ 
     - CORE_PEER_ADDRESS=peer0.org1.example.com:7051 
     # # the following setting starts chaincode containers on the same 
     # # bridge network as the peers 
     # # https://docs.docker.com/compose/networking/ 
     - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=${COMPOSE_PROJECT_NAME}_basic 
     - CORE_LEDGER_STATE_STATEDATABASE=CouchDB 
     - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984 
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric 
    command: peer node start 
    # command: peer node start --peer-chaincodedev=true 
    ports: 
     - 7051:7051 
     - 7053:7053 
    volumes: 
     - /var/run/:/host/var/run/ 
     - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/msp/peer 
     - ./crypto-config/peerOrganizations/org1.example.com/users:/etc/hyperledger/msp/users 
     - ./config:/etc/hyperledger/configtx 
    depends_on: 
     - orderer.example.com 
    networks: 
     - basic 
+1

以下的答案謝謝,您提出的這些更正解決了我的問題! – Pras

相關問題