Hyperledger 패브릭 피어 체인 코드 인스턴스화 시간 초과

Question

그래서 "컨소시엄 단계에서 체인 코드를 인스턴스화하려고합니다". 나는 모든 동료 (200 대 전반)에 설치했습니다. 내가

===================================================================================================== 
peer chaincode instantiate -o orderer:7050 --tls true --cafile /crypto-config/ordererOrganizations/orderer.com/orderers/orderer.orderer.com/msp/tlscacerts/tlsca.orderer.com-cert.pem -C aac -n mycc -v 1.0 
-c '{"Args":["init","a", "100", "b","200"]}' -P "OR ('Org1MSP.member','Org2MSP.member','Org3MSP.member')" 
===================================================================================================== 
2017-10-28 02:02:56.853 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP 
2017-10-28 02:02:56.853 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity 
2017-10-28 02:02:56.867 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 
2017-10-28 02:02:56.868 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 
2017-10-28 02:02:56.869 UTC [msp/identity] Sign -> DEBU 005 Sign: plaintext: 0A9D070A7508031A0C08D0CACFCF0510...30300A000A04657363630A0476736363 
2017-10-28 02:02:56.869 UTC [msp/identity] Sign -> DEBU 006 Sign: digest: EDDBC0833DC1815A04B56C17D7D7DC6CAE967A8BA1C5082668234325F325F1C1 
Error: Error endorsing chaincode: rpc error: code = Unknown desc = Timeout expired while starting chaincode mycc:1.0(networkid:dev,peerid:peer0.org1.com,tx:dcd9c8c334467ee867fdd82fdbbec483532281364b20fda1fcd1298a66a836b3) 

아웃이 조금 후 응답하지 않습니다 조각 및 시간에 도착하면

가 피어 로그는 다음과 같이 종료 :

이

peer0.org1.com | 2017-10-28 02:02:56.896 UTC [shim] sendChannel -> DEBU 540 [dcd9c8c3]after send 
peer0.org1.com | 2017-10-28 02:02:56.896 UTC [shim] afterResponse -> DEBU 541 [dcd9c8c3]Received RESPONSE, communicated (state:ready) 
peer0.org1.com | 2017-10-28 02:02:56.896 UTC [shim] handlePutState -> DEBU 542 [dcd9c8c3]Received RESPONSE. Successfully updated state 
peer0.org1.com | 2017-10-28 02:02:56.896 UTC [shim] func1 -> DEBU 543 [dcd9c8c3]Transaction completed. Sending COMPLETED 
peer0.org1.com | 2017-10-28 02:02:56.897 UTC [shim] func1 -> DEBU 544 [dcd9c8c3]Move state message COMPLETED 
peer0.org1.com | 2017-10-28 02:02:56.897 UTC [shim] handleMessage -> DEBU 545 [dcd9c8c3]Handling ChaincodeMessage of type: COMPLETED(state:ready) 
peer0.org1.com | 2017-10-28 02:02:56.897 UTC [shim] func1 -> DEBU 546 [dcd9c8c3]send state message COMPLETED 
peer0.org1.com | 2017-10-28 02:02:56.897 UTC [chaincode] processStream -> DEBU 547 [dcd9c8c3]Received message COMPLETED from shim 
peer0.org1.com | 2017-10-28 02:02:56.898 UTC [chaincode] HandleMessage -> DEBU 548 [dcd9c8c3]Fabric side Handling ChaincodeMessage of type: COMPLETED in state ready 
peer0.org1.com | 2017-10-28 02:02:56.898 UTC [chaincode] HandleMessage -> DEBU 549 [dcd9c8c334467ee867fdd82fdbbec483532281364b20fda1fcd1298a66a836b3]HandleMessage- COMPLETED. Notify 
peer0.org1.com | 2017-10-28 02:02:56.898 UTC [chaincode] notify -> DEBU 54a notifying Txid:dcd9c8c334467ee867fdd82fdbbec483532281364b20fda1fcd1298a66a836b3 
peer0.org1.com | 2017-10-28 02:02:56.898 UTC [chaincode] Execute -> DEBU 54b Exit 
peer0.org1.com | 2017-10-28 02:02:56.898 UTC [ccprovider] NewCCContext -> DEBU 54c NewCCCC (chain=advertiseragencychannel,chaincode=mycc,version=1.0,txid=dcd9c8c334467ee867fdd82fdbbec483532281364b20fda1fcd1298a66a836b3,syscc=false,proposal=0xc421a6b310,canname=mycc:1.0 
peer0.org1.com | 2017-10-28 02:02:56.899 UTC [chaincode] Launch -> DEBU 54d launchAndWaitForRegister fetched 1183 bytes from file system 
peer0.org1.com | 2017-10-28 02:02:56.899 UTC [chaincode] launchAndWaitForRegister -> DEBU 54e chaincode mycc:1.0 is being launched 
peer0.org1.com | 2017-10-28 02:02:56.899 UTC [chaincode] getArgsAndEnv -> DEBU 54f Executable is chaincode 
peer0.org1.com | 2017-10-28 02:02:56.899 UTC [chaincode] getArgsAndEnv -> DEBU 550 Args [chaincode -peer.address=peer0.org1:7051] 
peer0.org1.com | 2017-10-28 02:02:56.900 UTC [chaincode] launchAndWaitForRegister -> DEBU 551 start container: mycc:1.0(networkid:dev,peerid:peer0.org1.com) 
peer0.org1.com | 2017-10-28 02:02:56.900 UTC [chaincode] launchAndWaitForRegister -> DEBU 552 start container with args: chaincode -peer.address=peer0.org1:7051 
peer0.org1.com | 2017-10-28 02:02:56.900 UTC [chaincode] launchAndWaitForRegister -> DEBU 553 start container with env: 
peer0.org1.com |  CORE_CHAINCODE_ID_NAME=mycc:1.0 
peer0.org1.com |  CORE_PEER_TLS_ENABLED=true 
peer0.org1.com |  CORE_CHAINCODE_LOGGING_LEVEL=info 
peer0.org1.com |  CORE_CHAINCODE_LOGGING_SHIM=warning 
peer0.org1.com |  CORE_CHAINCODE_LOGGING_FORMAT=%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message} 
peer0.org1.com | 2017-10-28 02:02:56.901 UTC [container] lockContainer -> DEBU 554 waiting for container(dev-peer0.org1.com-mycc-1.0) lock 
peer0.org1.com | 2017-10-28 02:02:56.901 UTC [container] lockContainer -> DEBU 555 got container (dev-peer0.org1.com-mycc-1.0) lock 
peer0.org1.com | 2017-10-28 02:02:56.903 UTC [dockercontroller] Start -> DEBU 556 Cleanup container dev-peer0.org1.com-mycc-1.0 
peer0.org1.com | 2017-10-28 02:02:56.904 UTC [dockercontroller] stopInternal -> DEBU 557 Stop container dev-peer0.org1.com-mycc-1.0(No such container: dev-peer0.org1.com-mycc-1.0) 
peer0.org1.com | 2017-10-28 02:02:56.910 UTC [dockercontroller] stopInternal -> DEBU 558 Kill container dev-peer0.org1.com-mycc-1.0 (No such container: dev-peer0.org1.com-mycc-1.0) 
peer0.org1.com | 2017-10-28 02:02:56.912 UTC [dockercontroller] stopInternal -> DEBU 559 Remove container dev-peer0.org1.com-mycc-1.0 (No such container: dev-peer0.org1.com-mycc-1.0) 
peer0.org1.com | 2017-10-28 02:02:56.912 UTC [dockercontroller] Start -> DEBU 55a Start container dev-peer0.org1.com-mycc-1.0 
peer0.org1.com | 2017-10-28 02:02:56.912 UTC [dockercontroller] createContainer -> DEBU 55b Create container: dev-peer0.org1.com-mycc-1.0 
peer0.org1.com | 2017-10-28 02:02:57.043 UTC [dockercontroller] createContainer -> DEBU 55c Created container: dev-peer0.org1.com-mycc-1.0-fb6be780039642ab28b06bc02e8e4cad69b480256333e2b3fc8a7877a9ffdf1d 
peer0.org1.com | 2017-10-28 02:02:57.528 UTC [dockercontroller] Start -> DEBU 55d Started container dev-peer0.org1.com-mycc-1.0 
peer0.org1.com | 2017-10-28 02:02:57.528 UTC [container] unlockContainer -> DEBU 55e container lock deleted(dev-peer0.org1.com-mycc-1.0) 

내가 생각할 수있는 유일한 것입니다 내 작곡가의 네트워크는 "consortium_poc"이라고 불리우며이 네트워크 ID는 다르게 보입니다. "dev"로 보이는 네트워크 ID이지만 똑같은지 확실하지 않습니다. 내 동료는 CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=consortium_poc 환경 변수를 사용하고 있습니다.

인스턴스화 호출에서 매개 변수 조합을 여러 번 시도했습니다.

나는 거의 모든 방법이 있습니다. 이 마지막 작은 발걸음이 나를 미치게합니다. 힌트 또는 포인터가 있습니까?

편집 : 조금 더 구글이 나를 NETWORKID 값이 올바른지처럼

CORE_PEER_NETWORKID=consortium_poc 

지금 보이는 피어이 매개 변수를 추가했지만, 여전히 모두가 "컨테이너의 잠금을 해제"메시지에서 정지 단지 이전과.

Edit2가 :

그래서 조금 더 많은 것을 시도하고 지금 아래 문제 설명 호출에 IP 주소를 사용하여 무엇을 참조로 :

2017-10-30 15:52:33.553 UTC [chaincode] launchAndWaitForRegister -> DEBU 8cc start container with args: chaincode -peer.address=172.24.0.6:7051 

가 만들려고 용기를

Error starting SimpleAsset chaincode: Error trying to connect to local peer: x509: cannot validate certificate for 172.24.0.6 because it doesn't contain any IP SANs 

난 단지 두 가지를 변경 : 다음 말한다

,691 피어에서 CORE_PEER_CHAINCODELISTENADDRESS 세트 - 피어

추가 다시 CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock 주문자에 추가 CORE_PEER_ADDRESSAUTODETECT=true 363,210

1. 는

2.

Answer 1

의 핵심은 다른 매개 변수를 가질 것으로 보인다.

나중에이 문제로 어려움을 겪는 다른 사람을 위해 필자의 유스 케이스에서 작동하는 config를 제공 할 것입니다. 이것이 4 개 기관을위한 것임을 기억하십시오 - 여기 Org1.com - Org4.com 편집자 2 명씩 및 Orderer.com의 주문 담당자가 있습니다.

이 내용에 더 익숙한 사람이라면 복제되거나 불필요한 속성에 대해 의견을 말할 수 있다면 나는 모두 귀입니다. 이것은 내가 일하기를 기대했던 것보다 훨씬 오래 걸렸습니다. 저는 분명히 천 전문가가 아닙니다 ...

피어 기반

services: 
    peer-base: 
    image: hyperledger/fabric-peer 
    environment: 
     - GOPATH=/opt/gopath 
     - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock 
     - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=${COMPOSE_PROJECT_NAME}_poc 
     - CORE_PEER_NETWORKID=${COMPOSE_PROJECT_NAME}_poc 
     - CORE_LOGGING_LEVEL=DEBUG 
     - CORE_PEER_ADDRESSAUTODETECT=true 
     - CORE_PEER_GOSSIP_ORGLEADER=true 
     - CORE_PEER_EXTERNALENDPOINT=true 
     - CORE_PEER_ENDORSER_ENABLED=true 
     - CORE_PEER_PROFILE_ENABLED=true 
     - CORE_PEER_TLS_ENABLED=true 
     - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt 
     - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key 
     - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt 
    working_dir: /opt/gopath/src/chaincode 
    command: peer node start --peer-defaultchain=false 
    volumes: 
     - /var/run/:/host/var/run/ 
     - ./chaincode/:/opt/gopath/src/chaincode/ 
     - ./crypto-config:/opt/gopath/src/mofabric/peer/crypto 
     - ./channel-artifacts:/opt/gopath/src/mofabric/peer/channel-artifacts 

주문자

orderer: 
    container_name: orderer 
    image: hyperledger/fabric-orderer 
    networks: 
     poc: 
      aliases: 
       - ${COMPOSE_PROJECT_NAME} 

    environment: 
     - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=${COMPOSE_PROJECT_NAME}_poc 
     - CORE_PEER_NETWORKID=${COMPOSE_PROJECT_NAME}_poc 
     - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock 
     - GRPC_TRACE=all=true, 
     - GRPC_VERBOSITY=debug 
     - ORDERER_GENERAL_LOGLEVEL=debug 
     - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0 
     - ORDERER_GENERAL_LISTENPORT=7050 
     - ORDERER_GENERAL_GENESISPROFILE=Genesis 
     - ORDERER_GENERAL_GENESISMETHOD=file 
     - ORDERER_GENERAL_GENESISFILE=/etc/hyperledger/orderer/genesis.block 
     - ORDERER_GENERAL_LOCALMSPID=OrdererMSP 
     - ORDERER_GENERAL_LOCALMSPDIR=/etc/hyperledger/orderer/msp 
     - ORDERER_GENERAL_TLS_ENABLED=true 
     - ORDERER_GENERAL_TLS_PRIVATEKEY=/etc/hyperledger/orderer/tls/server.key 
     - ORDERER_GENERAL_TLS_CERTIFICATE=/etc/hyperledger/orderer/tls/server.crt 
     - ORDERER_GENERAL_TLS_ROOTCAS=[/etc/hyperledger/orderer/tls/ca.crt ] 
    working_dir: /opt/gopath/src/ 
    command: orderer 
    volumes: 
     - /var/run/:/host/var/run/ 
     - ./chaincode/:/opt/gopath/src/ 
     - ./channel-artifacts/genesis.block:/etc/hyperledger/orderer/genesis.block 
     - ./crypto-config/peerOrganizations/:/etc/hyperledger/peers/ 
     - ./crypto-config/ordererOrganizations/orderer.com/orderers/orderer.orderer.com/msp:/etc/hyperledger/orderer/msp 
     - ./crypto-config/ordererOrganizations/orderer.com/orderers/orderer.orderer.com/tls:/etc/hyperledger/orderer/tls 
    ports: 
     - 7050:7050 

CLI

cli: 
    container_name: cli 
    image: hyperledger/fabric-tools 
    tty: true 
    stdin_open: true 
    environment: 
     - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org1.com:7052 
     - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=${COMPOSE_PROJECT_NAME}_poc 
     - CORE_PEER_NETWORKID=${COMPOSE_PROJECT_NAME}_poc 
     - GOPATH=/opt/gopath 
     - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock 
     - GRPC_TRACE=all=true, 
     - GRPC_VERBOSITY=debug 
     - CORE_PEER_ADDRESSAUTODETECT=true 
     - CORE_LOGGING_LEVEL=DEBUG 
     - CORE_PEER_ID=cli 
     - CORE_PEER_ADDRESS=peer0.org1.com:7051 
     - CORE_PEER_SERVERHOSTOVERRIDE=peer0.org1.com:7051 
     - CORE_PEER_LOCALMSPID=Org1MSP 
     - CORE_PEER_TLS_ENABLED=true 
     - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt 
     - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key 
     - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt 
     - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/mofabric/peer/crypto/peerOrganizations/org1.com/users/Admin@mediaocean.com/msp 
    working_dir: /opt/gopath/src/chaincode 
    volumes: 
     - /var/run/:/host/var/run/ 
     - ./chaincode/:/opt/gopath/src/chaincode 
     - ./crypto-config:/opt/gopath/src/mofabric/peer/crypto 
     - ./channel-artifacts:/opt/gopath/src/mofabric/peer/channel-artifacts 
     - ./crypto-config/peerOrganizations/org1.com/users:/etc/hyperledger/fabric/users 
     - ./crypto-config/peerOrganizations/org1.com/peers/peer0.org1.com/msp:/etc/hyperledger/fabric/msp 
     - ./crypto-config/peerOrganizations/org1.com/peers/peer0.org1.com/tls:/etc/hyperledger/fabric/tls 
     - ./crypto-config:/crypto-config 
     - ./channel-artifacts:/channel-artifacts 
     - ./scripts:/scripts/ 
    depends_on: 
     - orderer 
     - peer0.org1.com 
     - peer1.org1.com 
     - peer0.org2.com 
     - peer1.org2.com 
     - peer0.org3.com 
     - peer1.org3.com 
     - peer0.org4.com 
     - peer1.org4.com 
    networks: 
     poc: 
      aliases: 
       - ${COMPOSE_PROJECT_NAME} 

그래서 그냥 내가 한 일의 최종 목록 - 다시 전성 검사 등 :

generate genesis block 
generate channel 
generate anchor peers 

start fabric 

in cli: 
create channel 
have all peers join channel (the byfn script shows how). 
update anchor peers (byfn again). 

have org1 in channel package, then orgs 2-4 serially sign chaincode (the chaincode for operators document describes this). 

install chaincode on all peers. 
instantiate it on peer0.org1.com 

이것은 완벽하지 않을 수도 있고 (또는 정확할 수도 있습니다.) 마침내 효과가 있습니다.