transport: error while dialing: dial tcp 127.0.0.1:7050: connect: connection refused
Hi, I started the official course about Hyperledger Fabric Developer, but when I run ./network.sh up createChannel -ca -s couchdb
I get the following error:
Error: failed to create deliver client for orderer: orderer client failed to connect to localhost:7050: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 127.0.0.1:7050: connect: connection refused" Channel creation failed
I am running it from Ubuntu 20.04 in WSL2 (Windows).
Did anybody already face this problem? Any idea how to fix it?
Thank you!
Comments
-
OK never mind I found the cause. The instructions say to run
./network.sh up createChannel -ca -s couchdb
, but instead I tried to run first./network.sh up
and then./network.sh createChannel -ca -s couchdb
.0 -
Hi, I am getting the exact same error, but unfortunately it wasn't resolved by running the "up" and "createChannel" commands separately. If anyone has any ideas then please let me know.
0 -
@drcirculor,
Hello, Let's see if we can figure this out. This error usually occurs when one of the dependencies is out of sync. Please go back and check the versions of the dependencies, especially Docker. Let me know if this helps. Bobbi0 -
Thanks @Bobbijn
Yes, you were right - I noticed this error when I brought up the network, "Local fabric binaries and docker images are out of sync."
I ended up deleting the "fabric" and "fabric-samples" folders from "~/go/src/github.com/hyperledger", then repeating the curl and git steps in the "Hyperledger Fabric samples, binaries, and Docker images" section.
The network startup and channel creation worked fine after that.Thanks for your help.
1 -
@drcirculor shukran yoh...had gotten stuck there for a couple of hours.
0 -
I am still having this issue:
- My installation is on stand alone machine.- running Ubuntu 20.04.4
I have verified the dependencies (we can add versions here) and running the correct command, but
- docker --version
Docker version 20.10.13, build a224086
- docker-compose --version
docker-compose version 1.25.0, build unknown
For the last step, (running as a root)
cd ~/go/src/github.com/hyperledger/fabric-samples/test-network/
./network.sh up createChannel -ca -s couchdb
Creating channel 'mychannel'.
If network is not up, starting nodes with CLI timeout of '5' tries and CLI delay of '3' seconds and using database 'couchdb
Generating channel create transaction 'mychannel.tx'
+ configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/mychannel.tx -channelID mychannel
2022-03-14 22:22:36.335 EDT [common.tools.configtxgen] main -> INFO 001 Loading configuration
2022-03-14 22:22:36.376 EDT [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/go/src/github.com/hyperledger/fabric-samples/test-network/configtx/configtx.yaml
2022-03-14 22:22:36.376 EDT [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 003 Generating new channel configtx
2022-03-14 22:22:36.465 EDT [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 004 Writing new channel tx
+ res=0
Creating channel mychannel
Using organization 1
+ peer channel create -o localhost:7050 -c mychannel --ordererTLSHostnameOverride orderer.example.com -f ./channel-artifacts/mychannel.tx --outputBlock ./channel-artifacts/mychannel.block --tls --cafile /root/go/src/github.com/hyperledger/fabric-samples/test-network/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
+ res=1
+ peer channel create -o localhost:7050 -c mychannel --ordererTLSHostnameOverride orderer.example.com -f ./channel-artifacts/mychannel.tx --outputBlock ./channel-artifacts/mychannel.block --tls --cafile /root/go/src/github.com/hyperledger/fabric-samples/test-network/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
+ res=1
+ peer channel create -o localhost:7050 -c mychannel --ordererTLSHostnameOverride orderer.example.com -f ./channel-artifacts/mychannel.tx --outputBlock ./channel-artifacts/mychannel.block --tls --cafile /root/go/src/github.com/hyperledger/fabric-samples/test-network/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
+ res=1
+ peer channel create -o localhost:7050 -c mychannel --ordererTLSHostnameOverride orderer.example.com -f ./channel-artifacts/mychannel.tx --outputBlock ./channel-artifacts/mychannel.block --tls --cafile /root/go/src/github.com/hyperledger/fabric-samples/test-network/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
+ res=1
Error: failed to create deliver client for orderer: orderer client failed to connect to localhost:7050: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 127.0.0.1:7050: connect: connection refused"
Channel creation failed
Earlier, I took out "name: fabric_test" from docker/docker-compose-ca.yaml file, it was complaining about name field
0 -
@farukansari i also faced the similar issue and i resolved it by applying below changes in docker-compose yaml files
changed networks to this
networks:
fabric_test:Replaced
image: hyperledger/fabric-orderer:latest
image: hyperledger/fabric-peer:latest
image: hyperledger/fabric-tools:latestTO
image: hyperledger/fabric-orderer:2.2
image: hyperledger/fabric-peer:2.2
image: hyperledger/fabric-tools:2.2
Run ./network.sh down and then ./network.sh up createChannel -ca -s couchdb
0 -
I had the same issue. I didn't change anything but just take it down and restart, it worked.
Run ./network.sh down and then ./network.sh up createChannel -ca -s couchdb
0
Categories
- 8.8K All Categories
- 13 LFX Mentorship
- 66 LFX Mentorship: Linux Kernel
- 356 Linux Foundation Boot Camps
- 226 Cloud Engineer Boot Camp
- 69 Advanced Cloud Engineer Boot Camp
- 23 DevOps Engineer Boot Camp
- 5 Cloud Native Developer Boot Camp
- 727 Training Courses
- 14 LFC110 Class Forum
- 16 LFD102 Class Forum
- 96 LFD103 Class Forum
- 2 LFD121 Class Forum
- 55 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 14 LFD254 Class Forum
- 420 LFD259 Class Forum
- 78 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 15 LFS200 Class Forum
- 683 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 271 LFS211 Class Forum
- 50 LFS216 Class Forum
- 23 LFS241 Class Forum
- 26 LFS242 Class Forum
- 18 LFS243 Class Forum
- 4 LFS244 Class Forum
- 7 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 104 LFS253 Class Forum
- 753 LFS258 Class Forum
- 7 LFS258-JP クラス フォーラム
- 48 LFS260 Class Forum
- 75 LFS261 Class Forum
- 6 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 8 LFS267 Class Forum
- 8 LFS268 Class Forum
- 4 LFS269 Class Forum
- 173 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 184 LFW211 Class Forum
- 100 LFW212 Class Forum
- 875 Hardware
- 204 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 204 Networking
- 98 Printers & Scanners
- 82 Storage
- 716 Linux Distributions
- 78 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 125 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 344 Ubuntu
- 445 Linux System Administration
- 33 Cloud Computing
- 63 Command Line/Scripting
- Github systems admin projects
- 88 Linux Security
- 73 Network Management
- 105 System Management
- 45 Web Management
- 50 Mobile Computing
- 18 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 499 Off Topic
- 119 Introductions
- 193 Small Talk
- 19 Study Material
- 742 Programming and Development
- 237 Kernel Development
- 471 Software Development
- 898 Software
- 244 Applications
- 178 Command Line
- 2 Compiling/Installing
- 72 Games
- 313 Installation
- 19 All In Program
- 19 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)