getting error while starting Hyperleger fabric network on Aws server

0 votes

I want to set up a Hyperledger fabric network on the Aws server, the network is working in my local system but on the AWS server I am getting below error while starting Hyperleger fabric network.

1. ERROR: for peer0.org1.example.com Cannot start service peer0.org1.example.com: driver failed programming external connectivity on endpoint peer0.org1.example.com (21b20bf94e4e1856ea3c5b179dc7f4e5853dbe8b1bfa65e0c9011b0844c961f2): (COMMAND_FAILED: '/sbin/iptables -w2 -t filter -A DOCKER ! -i br-7df572901231 -o br-7df572901231 -p tcp -d 192.168.112.9 --dport 7051 -j ACCEPT' failed: Another app is currently holding the xtables lock. Stopped waiting after 2s.

2. Error: error getting endorser client for channel: endorser client failed to connect to peer0.org1.example.com:7051: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 192.168.144.12:7051: connect: connection refused" peer0.org1 failed to join the channel, Retry after 3 seconds.

Edit

3. .Endorser client failed to connect : connection refused Error

Error: error getting endorser client for channel: endorser client failed to connect to peer0.org1.example.com:7051: failed to create new
connection: connection error: desc = "transport: error while dialing:
dial tcp 192.168.144.12:7051: connect: connection refused" peer0.org1
failed to join the channel, Retry after 3 seconds

version:

> Hyperledger Version: 1.4.6
> Go version: go1.12.12  
> OS/Arch:linux/amd64  
> Chaincode:   Base Image Version: 0.4.18

while up the first network, by using the below command:

./byfn.sh up -a  -s couchdb

Please help me on how to resolve the above issues.

Mar 30 in Blockchain by nithin
• 140 points

edited Mar 31 by Gitika 147 views
Can you explain what are you trying to do?
I want to set up the fabric on Aws, everything is working in my local system, but getting the error on Aws server
Did you set authentication properly? It shows connection refused.
how can I set authentication

1 answer to this question.

0 votes

Hey, @Nithin,

It seems like you have stopped containers that were not removed/cleaned up from your previous executions/trials and therefore starting new containers with the same names concludes to the errors above. Could you please try to do the process given below:

  • You should clean up your environment.
docker rm -rf $
  • To verify that all docker containers have been removed or not use this:
 docker ps -a
  • Note down your docker networks and volumes using:
docker network prune -f
docker volume prune -f
  • Then look at your docker images:

docker images
  • If you have any chaincode docker images, remove them.  ​

  docker rmi -f <docker image id>

And then try to startup your network again. Let me know it worked or not.

answered Mar 30 by Gitika
• 29,290 points
It is not working, i am getting same error
Hey, @Nithin,

Could you please tell with which command you started your docker?
./byfn.sh up -a  -s couchdb
Hey, @Nithin,

Could you please tell me, are you using a TLS enabled network?
yes,TLS_ENABLED=true enabled

Hey, @Nithin,

I guess this issue is related to TLS only, you can try this:

Just disable the TLS in peer-base.yaml and docker-compose-cli.yaml and run the network:

CORE_PEER_TLS_ENABLED=false

ORDERER_GENERAL_TLS_ENABLED=false

And try to change grpcs to grpc inside the network configuration files. 

Related Questions In Blockchain

0 votes
1 answer
0 votes
1 answer

Getting error while building Bitcoind on MAC OS

First of all try building a non-GUI ...READ MORE

answered Aug 20, 2018 in Blockchain by slayer
• 29,280 points
79 views
+1 vote
2 answers
0 votes
1 answer
0 votes
1 answer
0 votes
3 answers
0 votes
1 answer