How to solve bind cannot assign requested address Error

Question

I am running a Hyperledger Fabric

My start-order.sh file to start the order looks like this:

ORDERER_GENERAL_LOGLEVEL=info \

ORDERER_GENERAL_LISTENADDRESS=orderer0 \

ORDERER_GENERAL_GENESISMETHOD=file \

ORDERER_GENERAL_GENESISFILE=/root/bcnetwork/conf/crypto-config/ordererOrganizations/ordererorg0/orderers/orderer0.ordererorg0/genesis.block \

ORDERER_GENERAL_LOCALMSPID=OrdererOrg0MSP \

ORDERER_GENERAL_LOCALMSPDIR=/root/bcnetwork/conf/crypto-config/ordererOrganizations/ordererorg0/orderers/orderer0.ordererorg0/msp \

ORDERER_GENERAL_TLS_ENABLED=false \

ORDERER_GENERAL_TLS_PRIVATEKEY=/root/bcnetwork/conf/crypto-config/ordererOrganizations/ordererorg0/orderers/orderer0.ordererorg0/tls/server.key \

ORDERER_GENERAL_TLS_CERTIFICATE=/root/bcnetwork/conf/crypto-config/ordererOrganizations/ordererorg0/orderers/orderer0.ordererorg0/tls/server.crt \

ORDERER_GENERAL_TLS_ROOTCAS=[/root/bcnetwork/conf/crypto-config/ordererOrganizations/ordererorg0/orderers/orderer0.ordererorg0/tls/ca.crt,/root/bcnetwork/conf/crypto-config/peerOrganizations/org0/peers/peer0.org0/tls/ca.crt,/root/bcnetwork/conf/crypto-config/peerOrganizations/org1/peers/peer2.org1/tls/ca.crt] \

CONFIGTX_ORDERER_BATCHTIMEOUT=1s \

CONFIGTX_ORDERER_ORDERERTYPE=kafka \

CONFIGTX_ORDERER_KAFKA_BROKERS=[kafka-zookeeper:9092] \

orderer

When I run this, I get the following error:

2018-02-19 12:53:31.597 UTC [orderer/main] main -> INFO 001 Starting orderer:

Version: 1.0.2

 Go version: go1.9

 OS/Arch: linux/amd64

2018-02-19 12:53:31.602 UTC [orderer/main] initializeGrpcServer -> CRIT 002 Failed to listen: listen tcp XX.XXX.XXX.XX:7050: bind: cannot assign requested address

How to solve this?

Answer 1

You must mention in your host.conf file for the orderer to resolve to any address. Add the following to your host.conf and it should work.

-e ORDERER_GENERAL_LISTENADDRESS=0.0.0.0 -e ORDERER_GENERAL_LISTENPORT=7050

To know more on how to setup Hyperledger Fabric on multiple hosts, visit:

https://medium.com/@wahabjawed/hyperledger-fabric-on-multiple-hosts-a33b08ef24f

Answer 2

Try restarting docker. Maybe you are getting this error because the address is already being used by a background process.

$ docker stop
$ docker start

Answer 3

You might have kept docker running and up before initializing the fabric. Bring the containers down and start again. To bring the containers down, use the following command:

$ docker rm $(docker ps -qa)

Answer 4

I was facing the same problem. After a lot of research, I realized that the reason for the problem was that I ran the command as sudo and this command requires to be run by a non-sudo user. When I ran the command without sudo, it worked fine. Hope this helps in your case too.