Date
1 - 4 of 4
manually building first network issues
|
dedishchev-av@...
Dear Colleagues,
We have successfully launched educational program for 20 hours based on hyperledger technology in the Russian Academy of National Economy http://www.ffb.ranepa.ru/en/povyshenie-kvalifikatsii/tekhnologiya-raspredelennogo-reestra-blockchain-na-finansovykh-rynkakh-bankovskij-biznes-strakhovanie-birzhevoe-delo We have made practical business case on Hyperledger Composer and now have started to develop a practical case on Hyperledger Fabric. Being a Faculty of Banking and Finance we are creating a case "Banking Consortium on Hyperledger Fabric" based on Building Your First Network case. During the process we have encountered the following mistakes: 1. When invoking configtxgen tool to create genesis block we have the following mistakes:A) 2019-05-19 13:55:38.043 NewChannelGroup -> WARN 006 Default policy emission is deprecated, please include policy specifications for the channel group in configtx.yaml B) and for NewOrdererGroup 2019-05-19 13:55:38.047 MSK [common.tools.configtxgen.encoder] NewOrdererOrgGroup -> WARN 008 Default policy emission is deprecated, please include policy specifications for the orderer org group OrdererOrg in configtx.yaml 2. When creating a channel transaction artifact we are getting the following mistakes: A) For NewChannelGroup -> WARN 006 Default policy emission is deprecated, please include policy specifications for the channel group in configtx.yaml B) For theNewApplicationGroup -> WARN 008 Default policy emission is deprecated, please include policy specifications for the application org group Bank1MSP in configtx.yaml 3) When starting the network with the command docker-compose -f docker-compose-cli.yaml up -d I am getting only two peers, but specified four including Bank1, Bank2, Regulator, Auditor, Org1 and Org2: peer0.org1.example.com is up-to-date
peer0.org2.example.com is up-to-date
peer1.org1.example.com is up-to-date
peer1.org2.example.com is up-to-date
orderer.example.com is up-to-date
I would be very grateful for your help. Educational Project Alexander |
|
|
|
Ben Longstaff
Hi Alexander, If you include your configtx.yaml file, docker-compose-cli.yaml file and what version of Hyperledger Fabric you are using it will be easier to assist. You can get more information about why your peers didn't start by looking in the docker logs something like docker logs peer0.bank1.example.com docker logs peer0.bank2.example.com docker logs peer0.regulator.example.com docker logs peer0.auditor.example.com Cheers Ben |
|
|
|
dedishchev-av@...
Hi Ben,
Thank you for your reply. I am using Hyperledger Fabric 1.4.1 Please find attached files -- Educational Project Alexander |
|
|
|
Ben Longstaff
If you want to remove the warning messages you need to add in policies to the organisations like You have defined organisations for Bank1, Bank2, Auditor and Regulator in the configtx.yaml file but you still need to add them to your docker file. On Sun, May 19, 2019 at 11:10 PM <dedishchev-av@...> wrote: Hi Ben, |
|
|