Hyperledge Fabric V1.0.4 Pit Summary

Hyperledger Fabric problem Rollup when you read the document "Write a", you are performing./startfabric.sh may encounter the following error

Error:error getting endorser client channel:per:404-error trying to connect to local peer/opt/gopath/src/github.com/h yperledger/fabric/peer/common/common.go:116 Github.com/hyperledger/fabric/peer/common. getendorserclient/opt/gopath/src/github.com/hyperledger/fabric/peer/channel/channel.go:149 github.com/ Hyperledger/fabric/peer/channel. initcmdfactory/opt/gopath/src/github.com/hyperledger/fabric/peer/channel/join.go:138 github.com/hyperledger/ Fabric/peer/channel.join/opt/gopath/src/github.com/hyperledger/fabric/peer/channel/join.go:42 github.com/ hyperledger/fabric/peer/channel.joincmd.func1/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/ spf13/cobra/command.go:599 Github.com/hyperledger/fabric/vendor/github.com/spf13/cobra. (*command). execute/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:689 Github.com/hyperledger/fabric/vendor/github.com/spf13/cobra. (*command). Executec/opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/spf13/cobra/command.go:648 Github.com/hyperledger/fabric/vendor/github.com/spf13/cobra. (*command). execute/opt/gopath/src/github.com/hyperledger/fabric/peer/main.go:118 main.main/opt/go/src/runtime/proc.go:192 runtime.main/opt/go/src/runtime/asm_amd64.s:2087 Runtime.goexit caused by:context deadline exceeded Usage:peer Channe L join [Flags] Flags:-B,--blockpath string Path to file containing Genesis block Global flags:--cafile stri  ng Path to file containing pem-encoded trusted certificate (s) for the ordering endpoint String Default logging level and overrides, and the Core.yaml for full syntax-o,--orderer string orderi NG Service Endpoint--test.coverprofile string done (default "Coverage.cov")--tls Us e TLS when communicating with the Orderer endpoint-v,--version Display current version of Fabric PE ER Serv

Workaround, modify

fabric-samples/basic-network/start.sh

Export fabric_start_timeout=300  //Adjust this value appropriately to improve this problem

And then perform it again./startfabric.sh Golang Development Environment Problem

In accordance with the tutorial on the network to download some plug-ins, will be due to the network caused some plug-ins can not be installed, in fact, can be found because go-tools can not download caused by the following links to provide the method to solve
https://studygolang.com/articles/7922 Document "Building Your the network" issue

When you manually build network from this document, you need to modify the Docker-compose-cli.yaml annotation to remove the line shown below

...
      -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_mspconfigpath=/opt/gopath/src/ Github.com/hyperledger/fabric/peer/crypto/peerorganizations/org1.example.com/users/admin@org1.example.com/msp
    working_dir:/opt/gopath/src/github.com/hyperledger/fabric/peer
    #command:/bin/bash-c './scripts/ script.sh ${channel_name} ${delay} ${lang}; Sleep $TIMEOUT '
    volumes:
        -/var/run/:/host/var/run/
...

Edit File byfn.sh
Modify cli_timeout=10000 about Docker

Be sure to match Ali Docker Mirror Library. Refer to "https://www.cnblogs.com/anliven/p/6218741.html" about Chaincode-docker-devmode

When running this example, the direct start is always not starting normally. Report the following error

Error:an HTTP request took too long to complete. Retry with--verbose to obtain debug information.
If You are encounter this issue regularly because of slow network conditions, consider-setting compose_http_timeout to a Highe R value (current value:60).

This error does not affect our subsequent processes.
If you don't want to see this error, simply comment out all tty= true in the Docker-compose-simple.yaml file.
But according to the official document, in the "Terminal 2-build & Start the Chaincode" step, the command core_peer_address=peer:7052 core_chaincode_id_name=mycc:0 ./SACC always quote the following error

2018-03-19 05:57:10.162 UTC [shim] setupchaincodelogging-> INFO 001 Chaincode Log level is not provided; Defaulting To:info
2018-03-19 05:57:10.163 UTC [shim] setupchaincodelogging-> INFO 002 Chaincode (Build level:) Starting up ...
2018-03-19 05:57:13.164 UTC [shim] userchaincodestreamgetter-> erro Error 003 to connect to local trying Deadline exceeded
Error starting Simpleasset chaincode:error trying to connect to local Peer:context deadline Ded

The above order should be changed into core_peer_address=peer:7051 core_chaincode_id_name=mycc:0. /sacc
Note that it is peer:7051 instead of peer:7052 (the document is incorrectly written and may later be corrected)

If you skip this step and deploy directly and start Chaincode, you will report

Error:error endorsing Chaincode:rpc Error:code = Unknown desc = Failed to init chaincode (handler no found for Chaincod e mycc:0)
Usage:
  peer Chaincode instantiate [flags]

So this step cannot be omitted.