composer network start: No valid responses from any peers. Response from attempted peer comms was an error: Error: REQUEST_TIMEOUT

Question

I\'m trying to deploy a multiple organisations to Hyperledger fabric by following this tutorial -> https://hyperledger.github.io/composer/latest/tutorials/deploy-to-fabric-multi

Answer 1

Thanks for all the details.

Error: 14 UNAVAILABLE: Connect Failed

This is an error I have previously associated with errors in the connection.json file, with the CLI being unable to 'find' the Fabric containers - usually because they are not started. It is worth checking the connection.json file that you have the correct addresses, but I assume you have succeeded with composer network install for each of the Orgs.

This is a connection failure so you could well be on the right lines with the Docker networking.

Docker containers run on the default bridge unless you specify something different. You set the network within the docker compose .yaml file, or on the docker run command line.

You can use docker inspect bridge and docker inspect ba_multi_org_blockaviation to see which containers are on which network.

You can also start a shell session on any container e.g. docker exec -it peer0.org1.example.com /bin/sh and then use wget to test connectivity on different addresses and ports - this should help identify the connection problem.

wget is not the perfect network testing tool, but it is installed already in the Fabric containers! I would suggest trying these examples on your ubuntu host machine to get a feel for successful and failed connections:

wget www.ibm.com:80

wget www.ibm.com:9999

wget bad.bad.bad

Then from within the various containers try commands such as

wget peer0.org1.example.com:7051

wget peer0.org1.example.com:7053

If you see wget errors such error "(Connection reset by peer)" that is actually a success for our simple addressing/port/connectivity test ! (we don't really want a web get we just want to know we can 'hit' the other address/port)