Date   

#fabric-sdk-node #hyperledger-fabric #fabric-sdk-node #hyperledger-fabric

Abhay Prasad
 

Error : Cannot find Module 'fabric-client' in fabric 1.2

Even after trying "npm update" command, still i am facing fabric-client error. The error details given below

Fabric version - 1.2 | OS - Amazon Linux2 | command - npm i

[root@ip-172-31-61-27 controller]# node app.js
module.js:538
    throw err;
    ^

Error: Cannot find module 'fabric-client'
    at Function.Module._resolveFilename (module.js:536:15)
    at Function.Module._load (module.js:466:25)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/ec2-user/AWSNodeApp/controller/app.js:27:11)
    at Module._compile (module.js:635:30)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)

 


Re: #fabric-chaincode #hyperledger-fabric #fabric-sdk-node , peer lifecycle chaincode install issue #fabric-chaincode #hyperledger-fabric #fabric-sdk-node

Bozhidar Ignatov
 

Hi Chris,

Here is the package command:

# peer lifecycle chaincode package chaincode.tar.gz --path chaincode/chaincode/javascript/ --lang nod
e --label counter_v1
2020-08-28 06:04:04.548 UTC [bccsp] GetDefault -> DEBU 001 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP.
2020-08-28 06:04:04.585 UTC [bccsp] GetDefault -> DEBU 002 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP.
2020-08-28 06:04:04.587 UTC [main] InitCmd -> DEBU 003 peer lifecycle chaincode package does not need to init crypto
2020-08-28 06:04:04.589 UTC [chaincode.platform.node] GetDeploymentPayload -> DEBU 004 Packaging node.js project from path chaincode/chaincode/javascript
2020-08-28 06:04:04.589 UTC [chaincode.platform.util] WriteFolderToTarPackage -> DEBU 005 writing folder to package rootDirectory=chaincode/chaincode/javascript
2020-08-28 06:04:04.589 UTC [chaincode.platform.util] WriteFileToPackage -> DEBU 006 Writing file to tarball: src/index.js
2020-08-28 06:04:04.592 UTC [chaincode.platform.util] WriteFileToPackage -> DEBU 007 Writing file to tarball: src/lib/counter.js
2020-08-28 06:04:04.593 UTC [chaincode.platform.util] WriteFileToPackage -> DEBU 008 Writing file to tarball: src/lib/fabcar.js
2020-08-28 06:04:04.594 UTC [chaincode.platform.util] WriteFileToPackage -> DEBU 009 Writing file to tarball: src/package.json

I was reading the article and use it.

Thank you in advance,
Bozhidar

На чт, 27.08.2020 г. в 15:32 Gmail <alaskadd@...> написа:

Hi Bozhidar,
Can you share the commands/output from when you packaged the chaincode? You may also find it helpful if you have not already done so, to review the tutorial “Deploying a Smart Contract to a Channel” in the fabric docs to confirm you completed the necessary steps in order. 

Chris


On Aug 27, 2020, at 6:41 AM, Bozhidar Ignatov <ignatov@...> wrote:

Hello All,

The peer has joined the channel and chaincode is packed on.

I have a problem with instantiating chaincode in Hyperledger fabric Network version 2:
# peer lifecycle chaincode install chaincode.tar.gz

It gives me:
2020-08-27 11:21:53.851 UTC [bccsp] GetDefault -> DEBU 001 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP.
2020-08-27 11:21:53.862 UTC [bccsp] GetDefault -> DEBU 002 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP.
2020-08-27 11:21:53.865 UTC [bccsp_sw] openKeyStore -> DEBU 003 KeyStore opened at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/keystore]...done
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 004 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/signcerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 005 Inspecting file /etc/hyperledger/msp/users/Admin@d.as.com/msp/signcerts/Admin@d.as.com-cert.pem
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 006 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/cacerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 007 Inspecting file /etc/hyperledger/msp/users/Admin@d.as.com/msp/cacerts/ca.d.as.com-cert.pem
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 008 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/admincerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 009 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/intermediatecerts
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 00a Intermediate certs folder not found at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/intermediatecerts]. Skipping. [stat /etc/hyperledger/msp/users/Admin@d.as.com/msp/intermediatecerts: no such file or directory]
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00b Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlscacerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00c Inspecting file /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlscacerts/tlsca.d.as.com-cert.pem
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00d Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlsintermediatecerts
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 00e TLS intermediate certs folder not found at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/tlsintermediatecerts]. Skipping. [stat /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlsintermediatecerts: no such file or directory]
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00f Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/crls
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 010 crls folder not found at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/crls]. Skipping. [stat /etc/hyperledger/msp/users/Admin@d.as.com/msp/crls: no such file or directory]
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 011 Loading NodeOUs
2020-08-27 11:21:53.866 UTC [msp] newBccspMsp -> DEBU 012 Creating BCCSP-based MSP instance
2020-08-27 11:21:53.866 UTC [msp] New -> DEBU 013 Creating Cache-MSP instance
2020-08-27 11:21:53.866 UTC [msp] loadLocaMSP -> DEBU 014 Created new local MSP
2020-08-27 11:21:53.866 UTC [msp] Setup -> DEBU 015 Setting up MSP instance DMSP
2020-08-27 11:21:53.866 UTC [msp.identity] newIdentity -> DEBU 016 Creating identity instance for cert -----BEGIN CERTIFICATE-----
--cert--
-----END CERTIFICATE-----
2020-08-27 11:21:53.866 UTC [msp.identity] newIdentity -> DEBU 017 Creating identity instance for cert -----BEGIN CERTIFICATE-----
--cert--
-----END CERTIFICATE-----
2020-08-27 11:21:53.867 UTC [msp.identity] newIdentity -> DEBU 018 Creating identity instance for cert -----BEGIN CERTIFICATE-----
--cert--
-----END CERTIFICATE-----
2020-08-27 11:21:53.867 UTC [msp] setupSigningIdentity -> DEBU 019 Signing identity expires at 2030-08-19 07:54:00 +0000 UTC
2020-08-27 11:21:53.868 UTC [msp] GetDefaultSigningIdentity -> DEBU 01a Obtaining default signing identity
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01b parsed scheme: ""
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01c scheme "" not registered, fallback to default scheme
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01d ccResolverWrapper: sending update to cc: {[{127.0.0.1:7051  <nil> 0 <nil>}] <nil> <nil>}
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01e ClientConn switching balancer to "pick_first"
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01f Channel switches to new LB policy "pick_first"
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 020 Subchannel Connectivity change to CONNECTING
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 021 Subchannel picks a new address "127.0.0.1:7051" to connect
2020-08-27 11:21:53.870 UTC [grpc] UpdateSubConnState -> DEBU 022 pickfirstBalancer: HandleSubConnStateChange: 0xc000382c30, {CONNECTING <nil>}
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 023 Channel Connectivity change to CONNECTING
2020-08-27 11:21:53.874 UTC [grpc] Infof -> DEBU 024 Subchannel Connectivity change to READY
2020-08-27 11:21:53.874 UTC [grpc] UpdateSubConnState -> DEBU 025 pickfirstBalancer: HandleSubConnStateChange: 0xc000382c30, {READY <nil>}
2020-08-27 11:21:53.874 UTC [grpc] Infof -> DEBU 026 Channel Connectivity change to READY
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 027 parsed scheme: ""
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 028 scheme "" not registered, fallback to default scheme
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 029 ccResolverWrapper: sending update to cc: {[{127.0.0.1:7051  <nil> 0 <nil>}] <nil> <nil>}
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02a ClientConn switching balancer to "pick_first"
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02b Channel switches to new LB policy "pick_first"
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02c Subchannel Connectivity change to CONNECTING
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02d Subchannel picks a new address "127.0.0.1:7051" to connect
2020-08-27 11:21:53.875 UTC [grpc] UpdateSubConnState -> DEBU 02e pickfirstBalancer: HandleSubConnStateChange: 0xc0005267f0, {CONNECTING <nil>}
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02f Channel Connectivity change to CONNECTING
2020-08-27 11:21:53.877 UTC [grpc] Infof -> DEBU 030 Subchannel Connectivity change to READY
2020-08-27 11:21:53.877 UTC [grpc] UpdateSubConnState -> DEBU 031 pickfirstBalancer: HandleSubConnStateChange: 0xc0005267f0, {READY <nil>}
2020-08-27 11:21:53.877 UTC [grpc] Infof -> DEBU 032 Channel Connectivity change to READY
2020-08-27 11:21:53.878 UTC [msp.identity] Sign -> DEBU 033 Sign: plaintext: 0ACA070A6208031A0C08D1AE9EFA0510...FDFBFE160000FFFF0DCA33DD00120000 
2020-08-27 11:21:53.878 UTC [msp.identity] Sign -> DEBU 034 Sign: digest: 2715703A70596B688F7C36B592747957EB324AF0B142BD3F91B1A9CFA5F30903 

Error: chaincode install failed with status: 500 - error in simulation: failed to execute transaction 104b0c8f47f02adb3103a8c537f81ebd74275969a0d97aacad10f9e83bd7e33c: could not launch chaincode _lifecycle.syscc: error building chaincode: error building image: failed to get chaincode package for external build: could not get legacy chaincode package '_lifecycle.syscc': open /var/hyperledger/production/chaincodes/_lifecycle.syscc: no such file or directory


In the log of the peer - nothing interesting.


Hope someone face the same or will help solving with the issue!

Thanks in advance,
Bozhidar Ignatov


--

CST LTD
Bozhidar Ignatov

Software Team Lead

 

Mladost 4, blok 426A, vh G, et. 2, office G3, Sofia

+359 888 208 418 (Mobil)

E-Mail: ignatov@...

cst-bg.net  


Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere - Fri, 08/28/2020 #cal-notice

fabric@lists.hyperledger.org Calendar <noreply@...>
 

Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere

When:
Friday, 28 August 2020
6:00am to 7:00am
(GMT+01:00) Europe/London

Where:
https://zoom.us/j/6223336701

Organizer:
a_o-dowd@... +441962816761

Description:
Documentation workgroup call.
Agenda, minutes and recordings: https://wiki.hyperledger.org/display/fabric/Documentation+Working+Group


Documentation Workgroup: Agenda for Friday, 28 Aug

Anthony O'Dowd <a_o-dowd@...>
 

Hi All,

We will hold the documentation workgroup East hemisphere and Western hemisphere calls as usual this Friday.  Please attend, you are very welcome! Thanks again to Pam and Joe for hosting and recording the most recent Western hemisphere calls.

You can read about last week's calls at https://wiki.hyperledger.org/display/fabric/2020+08+21+DWG+Agenda You'll see significant minutes for both the Eastern and Western hemisphere calls, and recordings for both sessions. You can catch up with the full recordings and other sessions: https://wiki.hyperledger.org/display/fabric/Recordings

Our Eastern and Western hemisphere calls are very well attended at the moment -- thanks to all for your contributions and collaboration.

On our Eastern hemisphere call this week we will be reviewing:
  • Malayalam Translation progress
  • Japanese Language progress
  • Asia Pacific Study Circle
  • Contribution Video and Blog - review outline

Our Western hemisphere call will be equally busy:
  • Release progress
  • Sample overview
  • Google Analytics discussion
  • Spanish translation progress
  • Brazilian Portuguese translation progress
  • French translation
  • Outlook for a new Russian translation

See https://wiki.hyperledger.org/display/fabric/2020+08+28+DWG+Agenda for this week's agenda for the eastern and western hemisphere calls.

Please feel free to contribute using the wiki, including helping to build next week's agenda: https://wiki.hyperledger.org/display/fabric/2020+09+04+DWG+Agenda

Thanks!

Pam,  Joe, Anthony

Meeting Details
-------------
Please use the following link to attend the meeting:  https://zoom.us/j/6223336701

The meeting times are as follows: https://wiki.hyperledger.org/display/fabric/Documentation+Working+Group

Meeting 143A: Friday 24 Aug
                   1130 India Standard Time
                   1400 China Standard Time
                   1500 Japan Standard Time
                   1700 Australia Eastern Time
                   1400 Singapore Time
                   1100 Gulf Standard Time
                   1000 Moscow Standard Time
                   0700 Greenwich Mean Time
                   0800 Central European Time    

Meeting 143B: Friday 24 Aug
              1100 Central Daylight Time
                   1200 Eastern Daylight Time
                   0900 Pacific Daylight Time
                   1400 Brasil Time (BRT)
                   1600 Greenwich Mean Time
                   1700 Central European Time
                   1800 Moscow Standard Time

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


Re: Search for an endorsement policy translator for Node.js SDK v1.4

Mr.Phuwanai Thummavet
 

Thank you for your response. 

But I'm not sure if your script generates the correct format for sendInstantiateProposal()​ or sendUpgradeProposal()​?

As the output is different from the JSON object according to this reference: https://hyperledger.github.io/fabric-sdk-node/release-1.4/global.html#ChaincodeInstantiateUpgradeRequest

Please pardon me for my innocent.


On Thu, 27 Aug 2020, 18:20 Matthew White, <WHITEMAT@...> wrote:
Hello - I do have a pegjs grammar for policies that could be useful.
 
 
 
Regards, Matthew.
Matthew B White  IBM Blockchain Solutions Architect
 
Email me at WHITEMAT@...
Find me on StackOverflow, and generally at  calanais.me.uk
 
Note: restricted availability for meetings 14:30 to 17:00 UK Tuesday 
IBM United Kingdom Limited, Hursley Park, Winchester, Hampshire, SO21 2JN

"The wrong answers are the ones you go looking for when the right answers stare you in the face"
 
 
 
----- Original message -----
From: "Mr.Phuwanai Thummavet" <mr.thummavet@...>
Sent by: fabric@...
To: fabric <fabric@...>
Cc:
Subject: [EXTERNAL] [Hyperledger Fabric] Search for an endorsement policy translator for Node.js SDK v1.4
Date: Thu, Aug 27, 2020 11:36 AM
 
Hi Everyone,

I'm using Node.js Fabric SDK v1.4 for managing chaincode operations such as installing, instantiating, and upgrading. When to instantiate or upgrade a chaincode, I have to provide an endorsement policy in terms of a JSON object like the following.
{
  identities: [
    { role: { name: "member", mspId: "org1" }},
    { role: { name: "member", mspId: "org2" }}
  ],
  policy: {
    "1-of": [{ "signed-by": 0 }, { "signed-by": 1 }]
  }
}
 
That works but makes a bit of pain to me. Does anyone have any solution to translate the endorsement policy like this "OR('org1.member', 'org2.member')", for example, to the above JSON object?

Thank you so much.
--
Best Regards,
Phuwanai Thummavet
Blockchain Architect and Full-Stack Developer
 
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


Re: Issues with docker in Fedora 30? #docker

Tong Li
 

traffic can go out out does not mean that traffic can come in, so ping google does not really mean your necessary ports are open.
as I have indicated earlier in this doc, https://github.com/litong01/minifabric/blob/master/docs/RunningOnFedora.md, you can do first 2 steps to open up ports to solve firewall related issues.

Tong Li
IBM Open Technology

mario.schwaiger---08/27/2020 09:25:13 AM---> > Looks like that the user can not access docker endpoint and also cannot

From: mario.schwaiger@...
To: fabric@...
Date: 08/27/2020 09:25 AM
Subject: [EXTERNAL] Re: [Hyperledger Fabric] Issues with docker in Fedora 30? #docker
Sent by: fabric@...




      Looks like that the user can not access docker endpoint and also cannot even create a file when the current directory is mounted to the container, you need to fix these permission errors first.
I already assumed something like this, so I started it as root. It's weirdly causing very similar issues. In my opinion it's more a Fedora/Docker issue and not so much related to permissions. I have encountered other strange behaviours when you try to mount something into a Docker under Fedora. See the appendix to this reply. I'm getting different errors when I remove all Hyperledger-Images and try to start the test-network.
      I suspect the problem might be the same cause your other attempt also had errors. I would manually mount a directory to a container and exec into it and see why there were permission errors. If you give me a bit more details about your system such as OS version, how your docker was installed and its version, and what user you are using, I probably can dig it bit further.
This is a Fedora VM (30). The Docker is installed according to the very basic tutorial: https://docs.docker.com/engine/install/fedora/
Firewall-related I'm not very skilled, so I tried to allow as much as possible. No change. Also, as alpine can ping Google I'm in the opinion it's not a firewall-issue

Appendix when running test-network up:
#########  Generating Orderer Genesis block ##############
+ configtxgen -profile TwoOrgsOrdererGenesis -channelID system-channel -outputBlock ./system-genesis-block/genesis.block
2020-08-27 12:59:35.059 UTC [common.tools.configtxgen] main -> INFO 001 Loading configuration
2020-08-27 12:59:35.085 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 002 orderer type: etcdraft
2020-08-27 12:59:35.085 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 Orderer.EtcdRaft.Options unset, setting to tick_interval:"500ms" election_tick:10 heartbeat_tick:1 max_inflight_blocks:5 snapshot_interval_size:16777216
2020-08-27 12:59:35.085 UTC [common.tools.configtxgen.localconfig] Load -> INFO 004 Loaded configuration: /home/user/fabric-samples/test-network/configtx/configtx.yaml
2020-08-27 12:59:35.087 UTC [common.tools.configtxgen] doOutputBlock -> INFO 005 Generating genesis block
2020-08-27 12:59:35.087 UTC [common.tools.configtxgen] doOutputBlock -> INFO 006 Writing genesis block
+ res=0
Recreating orderer.example.com    ... error
Recreating peer0.org1.example.com ...
Recreating peer0.org2.example.com ...

ERROR: for orderer.example.com  Cannot start service orderer.example.com: b'OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \\"rootfs_linux.go:58: mounting \\\\\\"/home/user/fabric-samples/test-network/system-genesis-block/genesis.block\\\\\\" to rootfs \\\\\\"/var/lib/docker/overlay2/ccd7adec94c0fc9eb1b444e89b0ca1b5181135ad7f1b958277f8371d33168052/merged\\\\\\" at \\\\\\"/var/lib/docker/overlay2/ccd7adec94c0fc9eb1b444e89b0ca1b5181135ad7f1b958277f8371Recreating peer0.org1.example.com ... done
Recreating peer0.org2.example.com ... done

ERROR: for orderer.example.com  Cannot start service orderer.example.com: b'OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \\"rootfs_linux.go:58: mounting \\\\\\"/home/user/fabric-samples/test-network/system-genesis-block/genesis.block\\\\\\" to rootfs \\\\\\"/var/lib/docker/overlay2/ccd7adec94c0fc9eb1b444e89b0ca1b5181135ad7f1b958277f8371d33168052/merged\\\\\\" at \\\\\\"/var/lib/docker/overlay2/ccd7adec94c0fc9eb1b444e89b0ca1b5181135ad7f1b958277f8371d33168052/merged/var/hyperledger/orderer/orderer.genesis.block\\\\\\" caused \\\\\\"not a directory\\\\\\"\\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type'
ERROR: Encountered errors while bringing up the project.





Re: Issues with docker in Fedora 30? #docker

mario.schwaiger@...
 

Looks like that the user can not access docker endpoint and also cannot even create a file when the current directory is mounted to the container, you need to fix these permission errors first.
I already assumed something like this, so I started it as root. It's weirdly causing very similar issues. In my opinion it's more a Fedora/Docker issue and not so much related to permissions. I have encountered other strange behaviours when you try to mount something into a Docker under Fedora. See the appendix to this reply. I'm getting different errors when I remove all Hyperledger-Images and try to start the test-network.
I suspect the problem might be the same cause your other attempt also had errors. I would manually mount a directory to a container and exec into it and see why there were permission errors. If you give me a bit more details about your system such as OS version, how your docker was installed and its version, and what user you are using, I probably can dig it bit further.
This is a Fedora VM (30). The Docker is installed according to the very basic tutorial: https://docs.docker.com/engine/install/fedora/
Firewall-related I'm not very skilled, so I tried to allow as much as possible. No change. Also, as alpine can ping Google I'm in the opinion it's not a firewall-issue

Appendix when running test-network up:
#########  Generating Orderer Genesis block ##############
+ configtxgen -profile TwoOrgsOrdererGenesis -channelID system-channel -outputBlock ./system-genesis-block/genesis.block
2020-08-27 12:59:35.059 UTC [common.tools.configtxgen] main -> INFO 001 Loading configuration
2020-08-27 12:59:35.085 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 002 orderer type: etcdraft
2020-08-27 12:59:35.085 UTC [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 Orderer.EtcdRaft.Options unset, setting to tick_interval:"500ms" election_tick:10 heartbeat_tick:1 max_inflight_blocks:5 snapshot_interval_size:16777216
2020-08-27 12:59:35.085 UTC [common.tools.configtxgen.localconfig] Load -> INFO 004 Loaded configuration: /home/user/fabric-samples/test-network/configtx/configtx.yaml
2020-08-27 12:59:35.087 UTC [common.tools.configtxgen] doOutputBlock -> INFO 005 Generating genesis block
2020-08-27 12:59:35.087 UTC [common.tools.configtxgen] doOutputBlock -> INFO 006 Writing genesis block
+ res=0
Recreating orderer.example.com ... error
Recreating peer0.org1.example.com ...
Recreating peer0.org2.example.com ...

ERROR: for orderer.example.com Cannot start service orderer.example.com: b'OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \\"rootfs_linux.go:58: mounting \\\\\\"/home/user/fabric-samples/test-network/system-genesis-block/genesis.block\\\\\\" to rootfs \\\\\\"/var/lib/docker/overlay2/ccd7adec94c0fc9eb1b444e89b0ca1b5181135ad7f1b958277f8371d33168052/merged\\\\\\" at \\\\\\"/var/lib/docker/overlay2/ccd7adec94c0fc9eb1b444e89b0ca1b5181135ad7f1b958277f8371Recreating peer0.org1.example.com ... done
Recreating peer0.org2.example.com ... done

ERROR: for orderer.example.com Cannot start service orderer.example.com: b'OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \\"rootfs_linux.go:58: mounting \\\\\\"/home/user/fabric-samples/test-network/system-genesis-block/genesis.block\\\\\\" to rootfs \\\\\\"/var/lib/docker/overlay2/ccd7adec94c0fc9eb1b444e89b0ca1b5181135ad7f1b958277f8371d33168052/merged\\\\\\" at \\\\\\"/var/lib/docker/overlay2/ccd7adec94c0fc9eb1b444e89b0ca1b5181135ad7f1b958277f8371d33168052/merged/var/hyperledger/orderer/orderer.genesis.block\\\\\\" caused \\\\\\"not a directory\\\\\\"\\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type'
ERROR: Encountered errors while bringing up the project.


Re: Issues with docker in Fedora 30? #docker

mario.schwaiger@...
 

But it's not that it won't work at all:

$ docker run --rm -it alpine:latest /bin/sh
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
df20fa9351a1: Already exists
Digest: sha256:185518070891758909c9f839cf4ca393ee977ac378609f700f60a771a2dfe321
Status: Downloaded newer image for alpine:latest
/ # ping www.google.com
PING www.google.com (172.217.23.228): 56 data bytes
64 bytes from 172.217.23.228: seq=0 ttl=116 time=12.889 ms
64 bytes from 172.217.23.228: seq=1 ttl=116 time=12.600 ms
^C
--- www.google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 12.600/12.744/12.889 ms
/ #


Re: Issues with docker in Fedora 30? #docker

Tong Li
 

Looks like that the user can not access docker endpoint and also cannot even create a file when the current directory is mounted to the container, you need to fix these permission errors first. I suspect the problem might be the same cause your other attempt also had errors. I would manually mount a directory to a container and exec into it and see why there were permission errors. If you give me a bit more details about your system such as OS version, how your docker was installed and its version, and what user you are using, I probably can dig it bit further.

Tong Li
IBM Open Technology

mario.schwaiger---08/27/2020 08:20:50 AM---Tried. Doesn't work: (base) [user@f30 mywork]$ ./minifab up

From: mario.schwaiger@...
To: fabric@...
Date: 08/27/2020 08:20 AM
Subject: [EXTERNAL] Re: [Hyperledger Fabric] Issues with docker in Fedora 30? #docker
Sent by: fabric@...





Tried. Doesn't work:
(base) [user@f30 mywork]$ ./minifab up
Unable to find image 'hfrd/minifab:latest' locally
latest: Pulling from hfrd/minifab
df20fa9351a1: Already exists
16d327ff9a88: Pull complete
4b00023a922a: Pull complete
5d2a491bd934: Pull complete
603d27addd1e: Pull complete
Digest: sha256:0167daac05b1a55d187a287d88a3b053609921e15a4c8bdd8e0e4efc0b8e165e
Status: Downloaded newer image for hfrd/minifab:latest
cp: can't create 'vars/envsettings': Permission denied
scripts/mainfuncs.sh: line 84: ./vars/envsettings: No such file or directory
scripts/mainfuncs.sh: line 91: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
Minifab Execution Context:
   FABRIC_RELEASE=
   CHANNEL_NAME=
   PEER_DATABASE_TYPE=
   CHAINCODE_LANGUAGE=
   CHAINCODE_NAME=
   CHAINCODE_VERSION=
   CHAINCODE_INIT_REQUIRED=
   CHAINCODE_PARAMETERS=
   CHAINCODE_PRIVATE=
   CHAINCODE_POLICY=
   TRANSIENT_DATA=
   BLOCK_NUMBER=
   EXPOSE_ENDPOINTS=
   CURRENT_ORG=
   HOST_ADDRESSES=192.168.121.76,172.20.8.243
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get
http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/minifab/json: dial unix /var/run/docker.sock: connect: permission denied
   WORKING_DIRECTORY:
cp: can't create directory '/home/vars/chaincode': Permission denied
[WARNING]: log file at /home/vars/ansible.log is not writeable and we cannot create it, aborting

..
# Remove approve and commit from the operation list if release is less than 2.0
 The conditional check 'IMAGETAG is version('2.0', '<')' failed. The error was: Version comparison: 'LooseVersion' object has no attribute 'version'
 
 The error appears to be in '/home/fabops.yaml': line 21, column 7, but may
 be elsewhere in the file depending on the exact syntax problem.
 
 The offending line appears to be:
 
 
     - name: Remove approve and commit from the operation list if release is less than 2.0
       ^ here
 

# STATS *******************************************************
minifab: ok=2 failed=1

real 0m1.435s
user 0m1.295s
sys 0m0.152s
(base) [user@f30 mywork]$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
(base) [user@f30 mywork]$ sudo ./minifab up
[sudo] password for user:
cp: can't create 'vars/envsettings': Permission denied
scripts/mainfuncs.sh: line 84: ./vars/envsettings: No such file or directory
scripts/mainfuncs.sh: line 91: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
Minifab Execution Context:
   FABRIC_RELEASE=
   CHANNEL_NAME=
   PEER_DATABASE_TYPE=
   CHAINCODE_LANGUAGE=
   CHAINCODE_NAME=
   CHAINCODE_VERSION=
   CHAINCODE_INIT_REQUIRED=
   CHAINCODE_PARAMETERS=
   CHAINCODE_PRIVATE=
   CHAINCODE_POLICY=
   TRANSIENT_DATA=
   BLOCK_NUMBER=
   EXPOSE_ENDPOINTS=
   CURRENT_ORG=
   HOST_ADDRESSES=192.168.121.76,172.20.8.243
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get
http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/minifab/json: dial unix /var/run/docker.sock: connect: permission denied
   WORKING_DIRECTORY:
cp: can't create directory '/home/vars/chaincode': Permission denied
[WARNING]: log file at /home/vars/ansible.log is not writeable and we cannot create it, aborting

..
# Remove approve and commit from the operation list if release is less than 2.0
 The conditional check 'IMAGETAG is version('2.0', '<')' failed. The error was: Version comparison: 'LooseVersion' object has no attribute 'version'
 
 The error appears to be in '/home/fabops.yaml': line 21, column 7, but may
 be elsewhere in the file depending on the exact syntax problem.
 
 The offending line appears to be:
 
 
     - name: Remove approve and commit from the operation list if release is less than 2.0
       ^ here
 

# STATS *******************************************************
minifab: ok=2 failed=1

real 0m1.391s
user 0m1.249s
sys 0m0.149s
(base) [user@f30 mywork]$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES





Re: #fabric-chaincode #hyperledger-fabric #fabric-sdk-node , peer lifecycle chaincode install issue #fabric-chaincode #hyperledger-fabric #fabric-sdk-node

Chris Gabriel <alaskadd@...>
 

Hi Bozhidar,
Can you share the commands/output from when you packaged the chaincode? You may also find it helpful if you have not already done so, to review the tutorial “Deploying a Smart Contract to a Channel” in the fabric docs to confirm you completed the necessary steps in order. 

Chris


On Aug 27, 2020, at 6:41 AM, Bozhidar Ignatov <ignatov@...> wrote:

Hello All,

The peer has joined the channel and chaincode is packed on.

I have a problem with instantiating chaincode in Hyperledger fabric Network version 2:
# peer lifecycle chaincode install chaincode.tar.gz

It gives me:
2020-08-27 11:21:53.851 UTC [bccsp] GetDefault -> DEBU 001 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP.
2020-08-27 11:21:53.862 UTC [bccsp] GetDefault -> DEBU 002 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP.
2020-08-27 11:21:53.865 UTC [bccsp_sw] openKeyStore -> DEBU 003 KeyStore opened at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/keystore]...done
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 004 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/signcerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 005 Inspecting file /etc/hyperledger/msp/users/Admin@d.as.com/msp/signcerts/Admin@d.as.com-cert.pem
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 006 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/cacerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 007 Inspecting file /etc/hyperledger/msp/users/Admin@d.as.com/msp/cacerts/ca.d.as.com-cert.pem
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 008 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/admincerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 009 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/intermediatecerts
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 00a Intermediate certs folder not found at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/intermediatecerts]. Skipping. [stat /etc/hyperledger/msp/users/Admin@d.as.com/msp/intermediatecerts: no such file or directory]
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00b Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlscacerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00c Inspecting file /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlscacerts/tlsca.d.as.com-cert.pem
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00d Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlsintermediatecerts
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 00e TLS intermediate certs folder not found at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/tlsintermediatecerts]. Skipping. [stat /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlsintermediatecerts: no such file or directory]
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00f Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/crls
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 010 crls folder not found at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/crls]. Skipping. [stat /etc/hyperledger/msp/users/Admin@d.as.com/msp/crls: no such file or directory]
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 011 Loading NodeOUs
2020-08-27 11:21:53.866 UTC [msp] newBccspMsp -> DEBU 012 Creating BCCSP-based MSP instance
2020-08-27 11:21:53.866 UTC [msp] New -> DEBU 013 Creating Cache-MSP instance
2020-08-27 11:21:53.866 UTC [msp] loadLocaMSP -> DEBU 014 Created new local MSP
2020-08-27 11:21:53.866 UTC [msp] Setup -> DEBU 015 Setting up MSP instance DMSP
2020-08-27 11:21:53.866 UTC [msp.identity] newIdentity -> DEBU 016 Creating identity instance for cert -----BEGIN CERTIFICATE-----
--cert--
-----END CERTIFICATE-----
2020-08-27 11:21:53.866 UTC [msp.identity] newIdentity -> DEBU 017 Creating identity instance for cert -----BEGIN CERTIFICATE-----
--cert--
-----END CERTIFICATE-----
2020-08-27 11:21:53.867 UTC [msp.identity] newIdentity -> DEBU 018 Creating identity instance for cert -----BEGIN CERTIFICATE-----
--cert--
-----END CERTIFICATE-----
2020-08-27 11:21:53.867 UTC [msp] setupSigningIdentity -> DEBU 019 Signing identity expires at 2030-08-19 07:54:00 +0000 UTC
2020-08-27 11:21:53.868 UTC [msp] GetDefaultSigningIdentity -> DEBU 01a Obtaining default signing identity
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01b parsed scheme: ""
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01c scheme "" not registered, fallback to default scheme
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01d ccResolverWrapper: sending update to cc: {[{127.0.0.1:7051  <nil> 0 <nil>}] <nil> <nil>}
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01e ClientConn switching balancer to "pick_first"
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01f Channel switches to new LB policy "pick_first"
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 020 Subchannel Connectivity change to CONNECTING
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 021 Subchannel picks a new address "127.0.0.1:7051" to connect
2020-08-27 11:21:53.870 UTC [grpc] UpdateSubConnState -> DEBU 022 pickfirstBalancer: HandleSubConnStateChange: 0xc000382c30, {CONNECTING <nil>}
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 023 Channel Connectivity change to CONNECTING
2020-08-27 11:21:53.874 UTC [grpc] Infof -> DEBU 024 Subchannel Connectivity change to READY
2020-08-27 11:21:53.874 UTC [grpc] UpdateSubConnState -> DEBU 025 pickfirstBalancer: HandleSubConnStateChange: 0xc000382c30, {READY <nil>}
2020-08-27 11:21:53.874 UTC [grpc] Infof -> DEBU 026 Channel Connectivity change to READY
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 027 parsed scheme: ""
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 028 scheme "" not registered, fallback to default scheme
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 029 ccResolverWrapper: sending update to cc: {[{127.0.0.1:7051  <nil> 0 <nil>}] <nil> <nil>}
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02a ClientConn switching balancer to "pick_first"
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02b Channel switches to new LB policy "pick_first"
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02c Subchannel Connectivity change to CONNECTING
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02d Subchannel picks a new address "127.0.0.1:7051" to connect
2020-08-27 11:21:53.875 UTC [grpc] UpdateSubConnState -> DEBU 02e pickfirstBalancer: HandleSubConnStateChange: 0xc0005267f0, {CONNECTING <nil>}
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02f Channel Connectivity change to CONNECTING
2020-08-27 11:21:53.877 UTC [grpc] Infof -> DEBU 030 Subchannel Connectivity change to READY
2020-08-27 11:21:53.877 UTC [grpc] UpdateSubConnState -> DEBU 031 pickfirstBalancer: HandleSubConnStateChange: 0xc0005267f0, {READY <nil>}
2020-08-27 11:21:53.877 UTC [grpc] Infof -> DEBU 032 Channel Connectivity change to READY
2020-08-27 11:21:53.878 UTC [msp.identity] Sign -> DEBU 033 Sign: plaintext: 0ACA070A6208031A0C08D1AE9EFA0510...FDFBFE160000FFFF0DCA33DD00120000 
2020-08-27 11:21:53.878 UTC [msp.identity] Sign -> DEBU 034 Sign: digest: 2715703A70596B688F7C36B592747957EB324AF0B142BD3F91B1A9CFA5F30903 

Error: chaincode install failed with status: 500 - error in simulation: failed to execute transaction 104b0c8f47f02adb3103a8c537f81ebd74275969a0d97aacad10f9e83bd7e33c: could not launch chaincode _lifecycle.syscc: error building chaincode: error building image: failed to get chaincode package for external build: could not get legacy chaincode package '_lifecycle.syscc': open /var/hyperledger/production/chaincodes/_lifecycle.syscc: no such file or directory


In the log of the peer - nothing interesting.


Hope someone face the same or will help solving with the issue!

Thanks in advance,
Bozhidar Ignatov


Re: Issues with docker in Fedora 30? #docker

mario.schwaiger@...
 

Tried. Doesn't work:
(base) [user@f30 mywork]$ ./minifab up
Unable to find image 'hfrd/minifab:latest' locally
latest: Pulling from hfrd/minifab
df20fa9351a1: Already exists
16d327ff9a88: Pull complete
4b00023a922a: Pull complete
5d2a491bd934: Pull complete
603d27addd1e: Pull complete
Digest: sha256:0167daac05b1a55d187a287d88a3b053609921e15a4c8bdd8e0e4efc0b8e165e
Status: Downloaded newer image for hfrd/minifab:latest
cp: can't create 'vars/envsettings': Permission denied
scripts/mainfuncs.sh: line 84: ./vars/envsettings: No such file or directory
scripts/mainfuncs.sh: line 91: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
Minifab Execution Context:
FABRIC_RELEASE=
CHANNEL_NAME=
PEER_DATABASE_TYPE=
CHAINCODE_LANGUAGE=
CHAINCODE_NAME=
CHAINCODE_VERSION=
CHAINCODE_INIT_REQUIRED=
CHAINCODE_PARAMETERS=
CHAINCODE_PRIVATE=
CHAINCODE_POLICY=
TRANSIENT_DATA=
BLOCK_NUMBER=
EXPOSE_ENDPOINTS=
CURRENT_ORG=
HOST_ADDRESSES=192.168.121.76,172.20.8.243
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/minifab/json: dial unix /var/run/docker.sock: connect: permission denied
WORKING_DIRECTORY:
cp: can't create directory '/home/vars/chaincode': Permission denied
[WARNING]: log file at /home/vars/ansible.log is not writeable and we cannot create it, aborting

..
# Remove approve and commit from the operation list if release is less than 2.0
The conditional check 'IMAGETAG is version('2.0', '<')' failed. The error was: Version comparison: 'LooseVersion' object has no attribute 'version'

The error appears to be in '/home/fabops.yaml': line 21, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Remove approve and commit from the operation list if release is less than 2.0
^ here


# STATS *******************************************************
minifab: ok=2 failed=1

real 0m1.435s
user 0m1.295s
sys 0m0.152s
(base) [user@f30 mywork]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
(base) [user@f30 mywork]$ sudo ./minifab up
[sudo] password for user:
cp: can't create 'vars/envsettings': Permission denied
scripts/mainfuncs.sh: line 84: ./vars/envsettings: No such file or directory
scripts/mainfuncs.sh: line 91: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
scripts/mainfuncs.sh: line 93: ./vars/envsettings: Permission denied
Minifab Execution Context:
FABRIC_RELEASE=
CHANNEL_NAME=
PEER_DATABASE_TYPE=
CHAINCODE_LANGUAGE=
CHAINCODE_NAME=
CHAINCODE_VERSION=
CHAINCODE_INIT_REQUIRED=
CHAINCODE_PARAMETERS=
CHAINCODE_PRIVATE=
CHAINCODE_POLICY=
TRANSIENT_DATA=
BLOCK_NUMBER=
EXPOSE_ENDPOINTS=
CURRENT_ORG=
HOST_ADDRESSES=192.168.121.76,172.20.8.243
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/minifab/json: dial unix /var/run/docker.sock: connect: permission denied
WORKING_DIRECTORY:
cp: can't create directory '/home/vars/chaincode': Permission denied
[WARNING]: log file at /home/vars/ansible.log is not writeable and we cannot create it, aborting

..
# Remove approve and commit from the operation list if release is less than 2.0
The conditional check 'IMAGETAG is version('2.0', '<')' failed. The error was: Version comparison: 'LooseVersion' object has no attribute 'version'

The error appears to be in '/home/fabops.yaml': line 21, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Remove approve and commit from the operation list if release is less than 2.0
^ here


# STATS *******************************************************
minifab: ok=2 failed=1

real 0m1.391s
user 0m1.249s
sys 0m0.149s
(base) [user@f30 mywork]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES


Unable to fetch private data from peers (Empty membership) and can't commit new transactions - Hyperledged Fabric 1.4.6

mvtavares@...
 

Hello everyone. I got a problem with an 1.4.6 Fabric network with a network (27 peers and 5 orderers) where there is one peer (anchor peer) in an Organization that stopped commiting transactions. I can't understand why it started showing this message without any updates on the network, but it was working normally before that.

The message is:

2020-08-26 19:56:35.147 UTC [gossip.privdata] fetchPrivateData -> WARN fc2 Do not know any peer in the channel( xxxx ) that matches the policies , aborting
2020-08-26 19:56:35.147 UTC [gossip.privdata] fetchFromPeers -> WARN fc3 Failed fetching private data for block 743444 from peers: Empty membership
2020-08-26 19:56:36.149 UTC [gossip.privdata] fetchPrivateData -> WARN fc4 Do not know any peer in the channel( xxxx ) that matches the policies , aborting

I know we should have other peers configured to disseminate the pvt data, but unfortunately we didn't did it and now i need to find a way to make this peer work again. All the others 26 are fine and they all have the same config (changing only the Organization). Can anyone help me to find a way to just make this peer accept and commit new transaction even if it causes some of the pvt data to be lost ?

We've already tried to update the chaincode of this specific channel and while all the 26 peers confirmed the upgrade and are OK, this specific one still returns with the older version when we issue "peer chaincode list --instantiated channel".

Any help would be greatly appreciated.


#fabric-chaincode #hyperledger-fabric #fabric-sdk-node , peer lifecycle chaincode install issue #fabric-chaincode #hyperledger-fabric #fabric-sdk-node

Bozhidar Ignatov
 

Hello All,

The peer has joined the channel and chaincode is packed on.

I have a problem with instantiating chaincode in Hyperledger fabric Network version 2:
# peer lifecycle chaincode install chaincode.tar.gz

It gives me:
2020-08-27 11:21:53.851 UTC [bccsp] GetDefault -> DEBU 001 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP.
2020-08-27 11:21:53.862 UTC [bccsp] GetDefault -> DEBU 002 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP.
2020-08-27 11:21:53.865 UTC [bccsp_sw] openKeyStore -> DEBU 003 KeyStore opened at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/keystore]...done
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 004 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/signcerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 005 Inspecting file /etc/hyperledger/msp/users/Admin@d.as.com/msp/signcerts/Admin@d.as.com-cert.pem
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 006 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/cacerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 007 Inspecting file /etc/hyperledger/msp/users/Admin@d.as.com/msp/cacerts/ca.d.as.com-cert.pem
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 008 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/admincerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 009 Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/intermediatecerts
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 00a Intermediate certs folder not found at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/intermediatecerts]. Skipping. [stat /etc/hyperledger/msp/users/Admin@d.as.com/msp/intermediatecerts: no such file or directory]
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00b Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlscacerts
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00c Inspecting file /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlscacerts/tlsca.d.as.com-cert.pem
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00d Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlsintermediatecerts
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 00e TLS intermediate certs folder not found at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/tlsintermediatecerts]. Skipping. [stat /etc/hyperledger/msp/users/Admin@d.as.com/msp/tlsintermediatecerts: no such file or directory]
2020-08-27 11:21:53.865 UTC [msp] getPemMaterialFromDir -> DEBU 00f Reading directory /etc/hyperledger/msp/users/Admin@d.as.com/msp/crls
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 010 crls folder not found at [/etc/hyperledger/msp/users/Admin@d.as.com/msp/crls]. Skipping. [stat /etc/hyperledger/msp/users/Admin@d.as.com/msp/crls: no such file or directory]
2020-08-27 11:21:53.865 UTC [msp] getMspConfig -> DEBU 011 Loading NodeOUs
2020-08-27 11:21:53.866 UTC [msp] newBccspMsp -> DEBU 012 Creating BCCSP-based MSP instance
2020-08-27 11:21:53.866 UTC [msp] New -> DEBU 013 Creating Cache-MSP instance
2020-08-27 11:21:53.866 UTC [msp] loadLocaMSP -> DEBU 014 Created new local MSP
2020-08-27 11:21:53.866 UTC [msp] Setup -> DEBU 015 Setting up MSP instance DMSP
2020-08-27 11:21:53.866 UTC [msp.identity] newIdentity -> DEBU 016 Creating identity instance for cert -----BEGIN CERTIFICATE-----
--cert--
-----END CERTIFICATE-----
2020-08-27 11:21:53.866 UTC [msp.identity] newIdentity -> DEBU 017 Creating identity instance for cert -----BEGIN CERTIFICATE-----
--cert--
-----END CERTIFICATE-----
2020-08-27 11:21:53.867 UTC [msp.identity] newIdentity -> DEBU 018 Creating identity instance for cert -----BEGIN CERTIFICATE-----
--cert--
-----END CERTIFICATE-----
2020-08-27 11:21:53.867 UTC [msp] setupSigningIdentity -> DEBU 019 Signing identity expires at 2030-08-19 07:54:00 +0000 UTC
2020-08-27 11:21:53.868 UTC [msp] GetDefaultSigningIdentity -> DEBU 01a Obtaining default signing identity
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01b parsed scheme: ""
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01c scheme "" not registered, fallback to default scheme
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01d ccResolverWrapper: sending update to cc: {[{127.0.0.1:7051  <nil> 0 <nil>}] <nil> <nil>}
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01e ClientConn switching balancer to "pick_first"
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 01f Channel switches to new LB policy "pick_first"
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 020 Subchannel Connectivity change to CONNECTING
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 021 Subchannel picks a new address "127.0.0.1:7051" to connect
2020-08-27 11:21:53.870 UTC [grpc] UpdateSubConnState -> DEBU 022 pickfirstBalancer: HandleSubConnStateChange: 0xc000382c30, {CONNECTING <nil>}
2020-08-27 11:21:53.870 UTC [grpc] Infof -> DEBU 023 Channel Connectivity change to CONNECTING
2020-08-27 11:21:53.874 UTC [grpc] Infof -> DEBU 024 Subchannel Connectivity change to READY
2020-08-27 11:21:53.874 UTC [grpc] UpdateSubConnState -> DEBU 025 pickfirstBalancer: HandleSubConnStateChange: 0xc000382c30, {READY <nil>}
2020-08-27 11:21:53.874 UTC [grpc] Infof -> DEBU 026 Channel Connectivity change to READY
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 027 parsed scheme: ""
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 028 scheme "" not registered, fallback to default scheme
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 029 ccResolverWrapper: sending update to cc: {[{127.0.0.1:7051  <nil> 0 <nil>}] <nil> <nil>}
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02a ClientConn switching balancer to "pick_first"
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02b Channel switches to new LB policy "pick_first"
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02c Subchannel Connectivity change to CONNECTING
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02d Subchannel picks a new address "127.0.0.1:7051" to connect
2020-08-27 11:21:53.875 UTC [grpc] UpdateSubConnState -> DEBU 02e pickfirstBalancer: HandleSubConnStateChange: 0xc0005267f0, {CONNECTING <nil>}
2020-08-27 11:21:53.875 UTC [grpc] Infof -> DEBU 02f Channel Connectivity change to CONNECTING
2020-08-27 11:21:53.877 UTC [grpc] Infof -> DEBU 030 Subchannel Connectivity change to READY
2020-08-27 11:21:53.877 UTC [grpc] UpdateSubConnState -> DEBU 031 pickfirstBalancer: HandleSubConnStateChange: 0xc0005267f0, {READY <nil>}
2020-08-27 11:21:53.877 UTC [grpc] Infof -> DEBU 032 Channel Connectivity change to READY
2020-08-27 11:21:53.878 UTC [msp.identity] Sign -> DEBU 033 Sign: plaintext: 0ACA070A6208031A0C08D1AE9EFA0510...FDFBFE160000FFFF0DCA33DD00120000 
2020-08-27 11:21:53.878 UTC [msp.identity] Sign -> DEBU 034 Sign: digest: 2715703A70596B688F7C36B592747957EB324AF0B142BD3F91B1A9CFA5F30903 

Error: chaincode install failed with status: 500 - error in simulation: failed to execute transaction 104b0c8f47f02adb3103a8c537f81ebd74275969a0d97aacad10f9e83bd7e33c: could not launch chaincode _lifecycle.syscc: error building chaincode: error building image: failed to get chaincode package for external build: could not get legacy chaincode package '_lifecycle.syscc': open /var/hyperledger/production/chaincodes/_lifecycle.syscc: no such file or directory


In the log of the peer - nothing interesting.


Hope someone face the same or will help solving with the issue!

Thanks in advance,
Bozhidar Ignatov


Re: Search for an endorsement policy translator for Node.js SDK v1.4

Matthew White
 

Hello - I do have a pegjs grammar for policies that could be useful.
 
 
 
Regards, Matthew.
Matthew B White  IBM Blockchain Solutions Architect
 
Email me at WHITEMAT@...
Find me on StackOverflow, and generally at  calanais.me.uk
 
Note: restricted availability for meetings 14:30 to 17:00 UK Tuesday 
IBM United Kingdom Limited, Hursley Park, Winchester, Hampshire, SO21 2JN

"The wrong answers are the ones you go looking for when the right answers stare you in the face"
 
 
 
----- Original message -----
From: "Mr.Phuwanai Thummavet" <mr.thummavet@...>
Sent by: fabric@...
To: fabric <fabric@...>
Cc:
Subject: [EXTERNAL] [Hyperledger Fabric] Search for an endorsement policy translator for Node.js SDK v1.4
Date: Thu, Aug 27, 2020 11:36 AM
 
Hi Everyone,

I'm using Node.js Fabric SDK v1.4 for managing chaincode operations such as installing, instantiating, and upgrading. When to instantiate or upgrade a chaincode, I have to provide an endorsement policy in terms of a JSON object like the following.
{
  identities: [
    { role: { name: "member", mspId: "org1" }},
    { role: { name: "member", mspId: "org2" }}
  ],
  policy: {
    "1-of": [{ "signed-by": 0 }, { "signed-by": 1 }]
  }
}
 
That works but makes a bit of pain to me. Does anyone have any solution to translate the endorsement policy like this "OR('org1.member', 'org2.member')", for example, to the above JSON object?

Thank you so much.
--
Best Regards,
Phuwanai Thummavet
Blockchain Architect and Full-Stack Developer
 
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


Search for an endorsement policy translator for Node.js SDK v1.4

Mr.Phuwanai Thummavet
 

Hi Everyone,

I'm using Node.js Fabric SDK v1.4 for managing chaincode operations such as installing, instantiating, and upgrading. When to instantiate or upgrade a chaincode, I have to provide an endorsement policy in terms of a JSON object like the following.
{
  identities: [
    { role: { name: "member", mspId: "org1" }},
    { role: { name: "member", mspId: "org2" }}
  ],
  policy: {
    "1-of": [{ "signed-by": 0 }, { "signed-by": 1 }]
  }
}

That works but makes a bit of pain to me. Does anyone have any solution to translate the endorsement policy like this "OR('org1.member', 'org2.member')", for example, to the above JSON object?

Thank you so much.
--
Best Regards,
Phuwanai Thummavet
Blockchain Architect and Full-Stack Developer


Re: Issues with docker in Fedora 30? #docker

email4tong@gmail.com
 

Try minifabric, only takes 5 minutes to know if it works for you or not.




On Thursday, August 27, 2020, 5:33 AM, mario.schwaiger@... wrote:

I thought so too at first as I'm aware Fedora has a more restrictive security guideline. I installed firewalld and did according to the provided manual. It's different now, but still nothing works:
(base) [user@f30 fabric-samples]$ cd test-network/
(base) [user@f30 test-network]$ ./network.sh up
Starting nodes with CLI timeout of '5' tries and CLI delay of '3' seconds and using database 'leveldb'

LOCAL_VERSION=2.2.0
DOCKER_IMAGE_VERSION=2.2.0
Creating network "net_test" with the default driver
Creating volume "net_orderer.example.com" with default driver
Creating volume "net_peer0.org1.example.com" with default driver
Creating volume "net_peer0.org2.example.com" with default driver
Creating peer0.org2.example.com ... done
Creating orderer.example.com ... done
Creating peer0.org1.example.com ... done
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
eff58b51de11 hyperledger/fabric-peer:latest "peer node start" 2 seconds ago Up Less than a second 0.0.0.0:7051->7051/tcp peer0.org1.example.com
f610d2bca29e hyperledger/fabric-peer:latest "peer node start" 2 seconds ago Up Less than a second 7051/tcp, 0.0.0.0:9051->9051/tcp peer0.org2.example.com
0eb3c219d317 hyperledger/fabric-orderer:latest "orderer" 2 seconds ago Up Less than a second 0.0.0.0:7050->7050/tcp orderer.example.com
0c4437009820 ubuntu "bash" 15 hours ago Exited (0) 15 hours ago elated_swirles
3d15519bcfab hello-world "/hello" 15 hours ago Exited (0) 15 hours ago naughty_borg
53a4e50a385d hello-world "/hello" 16 hours ago Exited (0) 16 hours ago blissful_shannon
15f638ad5f95 hyperledger/fabric-peer "peer node start" 16 hours ago Exited (0) 16 hours ago distracted_jones
(base) [user@f30 test-network]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
(base) [user@f30 test-network]$ cd ..
(base) [user@f30 fabric-samples]$ cd fabcar/
(base) [user@f30 fabcar]$ ./startFabric.sh javascript
/home/user/fabric-samples/test-network /home/user/fabric-samples/fabcar
Stopping network

Removing peer0.org1.example.com ... done
Removing peer0.org2.example.com ... done
Removing orderer.example.com ... done
Removing network net_test
Removing volume net_orderer.example.com
Removing volume net_peer0.org1.example.com
Removing volume net_peer0.org2.example.com
Removing network net_test
WARNING: Network net_test not found.
Removing volume net_peer0.org3.example.com
WARNING: Volume net_peer0.org3.example.com not found.
---- No containers available for deletion ----
---- No images available for deletion ----
(base) [user@f30 fabcar]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES


Re: Issues with docker in Fedora 30? #docker

mario.schwaiger@...
 

I thought so too at first as I'm aware Fedora has a more restrictive security guideline. I installed firewalld and did according to the provided manual. It's different now, but still nothing works:
(base) [user@f30 fabric-samples]$ cd test-network/
(base) [user@f30 test-network]$ ./network.sh up
Starting nodes with CLI timeout of '5' tries and CLI delay of '3' seconds and using database 'leveldb'

LOCAL_VERSION=2.2.0
DOCKER_IMAGE_VERSION=2.2.0
Creating network "net_test" with the default driver
Creating volume "net_orderer.example.com" with default driver
Creating volume "net_peer0.org1.example.com" with default driver
Creating volume "net_peer0.org2.example.com" with default driver
Creating peer0.org2.example.com ... done
Creating orderer.example.com ... done
Creating peer0.org1.example.com ... done
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
eff58b51de11 hyperledger/fabric-peer:latest "peer node start" 2 seconds ago Up Less than a second 0.0.0.0:7051->7051/tcp peer0.org1.example.com
f610d2bca29e hyperledger/fabric-peer:latest "peer node start" 2 seconds ago Up Less than a second 7051/tcp, 0.0.0.0:9051->9051/tcp peer0.org2.example.com
0eb3c219d317 hyperledger/fabric-orderer:latest "orderer" 2 seconds ago Up Less than a second 0.0.0.0:7050->7050/tcp orderer.example.com
0c4437009820 ubuntu "bash" 15 hours ago Exited (0) 15 hours ago elated_swirles
3d15519bcfab hello-world "/hello" 15 hours ago Exited (0) 15 hours ago naughty_borg
53a4e50a385d hello-world "/hello" 16 hours ago Exited (0) 16 hours ago blissful_shannon
15f638ad5f95 hyperledger/fabric-peer "peer node start" 16 hours ago Exited (0) 16 hours ago distracted_jones
(base) [user@f30 test-network]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
(base) [user@f30 test-network]$ cd ..
(base) [user@f30 fabric-samples]$ cd fabcar/
(base) [user@f30 fabcar]$ ./startFabric.sh javascript
/home/user/fabric-samples/test-network /home/user/fabric-samples/fabcar
Stopping network

Removing peer0.org1.example.com ... done
Removing peer0.org2.example.com ... done
Removing orderer.example.com ... done
Removing network net_test
Removing volume net_orderer.example.com
Removing volume net_peer0.org1.example.com
Removing volume net_peer0.org2.example.com
Removing network net_test
WARNING: Network net_test not found.
Removing volume net_peer0.org3.example.com
WARNING: Volume net_peer0.org3.example.com not found.
---- No containers available for deletion ----
---- No images available for deletion ----
(base) [user@f30 fabcar]$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES


Re: Hyperledger Fabric Multi Cloud Setup (Azure, AWS and GCP), Multi Version Setup and Integration -- Hyperledger Fabric 1.2 (AWS Managed), Hyperledger Fabric (HLF) on Azure Kubernetes Service (AKS)

Eugene Aseev
 

Hi Nathan,

 

This is definitely possible. Chainstack customers are running production-grade Hyperledger Fabric 2.x networks in exactly three clouds you mentioned.

 

Regards,

Eugene Aseev

 

From: fabric@... <fabric@...> On Behalf Of Nathan Aw via lists.hyperledger.org
Sent: Wednesday, 26 August 2020 3:48 PM
To: fabric@...
Subject: [Hyperledger Fabric] Hyperledger Fabric Multi Cloud Setup (Azure, AWS and GCP), Multi Version Setup and Integration -- Hyperledger Fabric 1.2 (AWS Managed), Hyperledger Fabric (HLF) on Azure Kubernetes Service (AKS)

 

Hi everyone,

 

I have an existing Hyperledger Fabric 1.2 (AWS Managed Blockchain) and Hyperledger Fabric (HLF) on Azure Kubernetes Service (AKS) 

 

As part of anti-fragile designand architect, there is a need to extend and/or create a fabric network that spans across multiple cloud providers (Azure, AWS, GCP).

 

Key idea here is to have multiple ordering services and all the peer nodes distributed across the 3 major cloud providers to achieve true resilience/decentralization. This is to ensure that the platform on which hyperledger fabric is deployed is sufficiently decentralized, too. 

 

Is this within the realm of possibility from the design of hyperledger fabric?

 

Thank you.

 

Regards,

 

Nathan Aw

 


Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere - Fri, 08/28/2020 6:00am-7:00am #cal-reminder

fabric@lists.hyperledger.org Calendar <fabric@...>
 

Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere

When: Friday, 28 August 2020, 6:00am to 7:00am, (GMT+01:00) Europe/London

Where:https://zoom.us/j/6223336701

View Event

Organizer: Anthony O'Dowd a_o-dowd@... +441962816761

Description: Documentation workgroup call.
Agenda, minutes and recordings: https://wiki.hyperledger.org/display/fabric/Documentation+Working+Group


Re: Hyperledger Fabric Multi Cloud Setup (Azure, AWS and GCP), Multi Version Setup and Integration -- Hyperledger Fabric 1.2 (AWS Managed), Hyperledger Fabric (HLF) on Azure Kubernetes Service (AKS)

Tsvetan Georgiev
 

Hi Nathan,

As Jacov suggests you have to upgrade your network (ordering service, peers, etc) to 1.4.x (and then optionally to 2.x) in order to get the RAFT based HLF Ordering Service that can be managed by multiple service providers (OSPs) and orderers can be added on the fly.

To understand more about 1.4.x you can read through https://hyperledger-fabric.readthedocs.io/en/release-1.4/whatsnew.html. You can find there a migration guide and all the information you need to distribute your peers/orderers and Service Providers.

It will take some reading and time to implement it. That is very essential topic though as cross cloud deployments are quite important considering the nature and meaning of DLT paradigm.  My team had to go through and automate all these steps while building the channel management feature of consortia.io (essentially HLF channel update transaction managed by chaincode deployed on HLF network). Honestly this is not a simple process and requires time to understand and implement. Don't hesitate to ask ... I can help in pointing to the right information.

Regards,
Tsvetan
consortia.io

2341 - 2360 of 11213