Lab3 Error can't read the block: &{NOT_FOUND}

[email protected]:/opt/gopath/src/github.com/hyperledger/fabric# peer channel fetch oldest allarewelcome.block -c allarewelcome --orderer orderer.example.com:7050
2019-12-16 23:44:18.741 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2019-12-16 23:44:18.743 UTC [cli.common] readBlock -> INFO 002 Got status: &{NOT_FOUND}
Error: can't read the block: &{NOT_FOUND}
What am i doing wrong? I fix one error just to find another.
Comments
-
@etrelz said:
[email protected]:/opt/gopath/src/github.com/hyperledger/fabric# peer channel fetch oldest allarewelcome.block -c allarewelcome --orderer orderer.example.com:70502019-12-16 23:44:18.741 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2019-12-16 23:44:18.743 UTC [cli.common] readBlock -> INFO 002 Got status: &{NOT_FOUND}
Error: can't read the block: &{NOT_FOUND}What am i doing wrong? I fix one error just to find another.
Hi, is this peer0 or peer1?
did you run the ./bootstrap.sh script when you started the network? Then peer0 should automatically join the channel.If you did not run the script, check your starterFiles ==> config folder, see if the allarewelcome.tx file is there. If it is not, then the channel has not been created yet.
You can also check the orderer log by typing docker logs --details ordererID
0 -
Thank you. made it through Lab 3.. and guess what another error. lol i'll read through the other threads to see if someone else had this error.
0 -
@etrelz In case you are still facing this issue, this is how i solved it.
1. Ran startup.sh, so that recreated the channel allarewelcome (and deleted all the existing peer containers)
2. For both the peer definitions in docker-compose.yml file, i changed image: hyperledger/fabric-peer to image: hyperledger/fabric-peer:1.4.4
After starting the peer containers, i was able to fetch the genesis block for allarewelcome channel, as also able to join it.
Hope that helps!2 -
@manjushaawasthi
it was a good advice, still in my case did not resolve it.
After logging into the peer1, the command:
peer channel fetch oldest allarewelcome.block -c allarewelcome --orderer orderer.example.com:7050gets me an error:
2020-01-24 03:05:58.059 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2020-01-24 03:05:58.061 UTC [cli.common] readBlock -> INFO 002 Got status: &{NOT_FOUND}
Error: can't read the block: &{NOT_FOUND}0 -
@LasToronto said:
@manjushaawasthi
it was a good advice, still in my case did not resolve it.
After logging into the peer1, the command:
peer channel fetch oldest allarewelcome.block -c allarewelcome --orderer orderer.example.com:7050gets me an error:
2020-01-24 03:05:58.059 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2020-01-24 03:05:58.061 UTC [cli.common] readBlock -> INFO 002 Got status: &{NOT_FOUND}
Error: can't read the block: &{NOT_FOUND}Hi @LasToronto ,
Please go into the orderer container and check its log, maybe there is an connection error.Also, please check that the channel allarewelcome is actually up and running. You can see that in the orderer log as well.
If both connection is fine & channel running, there migth be an issue with peer1 authorization. Please type 'printenv' inside peer1 container, and check that all environment variables are set correctly.
I hope this helps. If not, let me know!
0 -
@LasToronto said:
@manjushaawasthi
it was a good advice, still in my case did not resolve it.
After logging into the peer1, the command:
peer channel fetch oldest allarewelcome.block -c allarewelcome --orderer orderer.example.com:7050gets me an error:
2020-01-24 03:05:58.059 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2020-01-24 03:05:58.061 UTC [cli.common] readBlock -> INFO 002 Got status: &{NOT_FOUND}
Error: can't read the block: &{NOT_FOUND}Also, @LasToronto , seems like you are inside the CLI container when you try the fetch command. You should do this from the Peer1 container. Hope that helps.
0 -
@Niklaskkkk
I issued the command from the Peer1.0 -
@Niklaskkkk what does it make you think that I am in the CLI container?
0 -
@LasToronto said:
@Niklaskkkk
I issued the command from the Peer1.Hi @LasToronto , did you make it work? If not, what did the orderer log tell you? Also, check the Peer1 container log & please post both logs here, I will try to help you.
Maybe also try to reset your network first, by doing:
./teardown.sh
./bootstrap.shLet me know how it goes.
0 -
Spent a lot of time on this. Ultimately, the resolution was in the post above by manjushaawasthi, which was to change the peer image to HLF 1.4.4
1 -
I faced same issue, it happens whenever we clean the network, I resolve this issue by
go to Peer0 and create channel again
$ peer channel create -o orderer.example.com:7050 -c allarewelcome -f /etc/hyperledger/configtx/allarewelcome.tx
$ peer0.org1.example.com peer channel join -b allarewelcome.blockgo to Peer1 and join the channel
$ peer channel fetch oldest allarewelcome.block -c allarewelcome --orderer orderer.example.com:7050
$ peer channel join -b allarewelcome.blockThis works from rather than running bootstrap.sh every time.
0 -
@moolkothari said:
I faced same issue, it happens whenever we clean the network, I resolve this issue bygo to Peer0 and create channel again
$ peer channel create -o orderer.example.com:7050 -c allarewelcome -f /etc/hyperledger/configtx/allarewelcome.tx
$ peer0.org1.example.com peer channel join -b allarewelcome.blockgo to Peer1 and join the channel
$ peer channel fetch oldest allarewelcome.block -c allarewelcome --orderer orderer.example.com:7050
$ peer channel join -b allarewelcome.blockThis works from rather than running bootstrap.sh every time.
@moolkothari I followed the same, created the channel again, fetch and join channel in peer0 and for peer1 - fetch genesis block and join channel.
0 -
@moolkothari said:
I faced same issue, it happens whenever we clean the network, I resolve this issue bygo to Peer0 and create channel again
$ peer channel create -o orderer.example.com:7050 -c allarewelcome -f /etc/hyperledger/configtx/allarewelcome.tx
$ peer0.org1.example.com peer channel join -b allarewelcome.blockgo to Peer1 and join the channel
$ peer channel fetch oldest allarewelcome.block -c allarewelcome --orderer orderer.example.com:7050
$ peer channel join -b allarewelcome.blockThis works from rather than running bootstrap.sh every time.
Great suggestion @moolkothari . you can also adjust these commands inside the startup script. I did this during the tutorials, so basically the only command I had to run was startup, to restart the network (but remember to comment out generation of new keys etc since it is just demo netowork)
0
Categories
- 9.1K All Categories
- 15 LFX Mentorship
- 68 LFX Mentorship: Linux Kernel
- 380 Linux Foundation Boot Camps
- 233 Cloud Engineer Boot Camp
- 75 Advanced Cloud Engineer Boot Camp
- 30 DevOps Engineer Boot Camp
- 9 Cloud Native Developer Boot Camp
- 977 Training Courses
- 15 LFC110 Class Forum
- 16 LFD102 Class Forum
- 106 LFD103 Class Forum
- 6 LFD121 Class Forum
- 56 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 19 LFD254 Class Forum
- 450 LFD259 Class Forum
- 90 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 16 LFS200 Class Forum
- 713 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 282 LFS211 Class Forum
- 50 LFS216 Class Forum
- 27 LFS241 Class Forum
- 28 LFS242 Class Forum
- 19 LFS243 Class Forum
- 6 LFS244 Class Forum
- 12 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 113 LFS253 Class Forum
- 814 LFS258 Class Forum
- 8 LFS258-JP クラス フォーラム
- 54 LFS260 Class Forum
- 81 LFS261 Class Forum
- 18 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 10 LFS267 Class Forum
- 9 LFS268 Class Forum
- 6 LFS269 Class Forum
- 182 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 191 LFW211 Class Forum
- 114 LFW212 Class Forum
- 880 Hardware
- 207 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 205 Networking
- 98 Printers & Scanners
- 82 Storage
- 730 Linux Distributions
- 85 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 127 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 349 Ubuntu
- 450 Linux System Administration
- 33 Cloud Computing
- 64 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 76 Network Management
- 105 System Management
- 45 Web Management
- 51 Mobile Computing
- 19 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 501 Off Topic
- 121 Introductions
- 193 Small Talk
- 19 Study Material
- 756 Programming and Development
- 243 Kernel Development
- 479 Software Development
- 903 Software
- 247 Applications
- 178 Command Line
- 2 Compiling/Installing
- 73 Games
- 314 Installation
- 26 All In Program
- 26 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)