hyperledger-labs/hl-starterkit

Hyperledger CLI Starter Kit

Hyperledger Labs

Hyperledger Labs provides a space (i.e., GitHub repos) where work can easily be started without the creation of a project. Please refer to the Hyperledger Labs wiki page for additional information.

Process to propose a new lab

1. Fork the hyperledger-labs.github.io repository.

2. Fill out the Proposal Template and save it into the labs subdirectory under the name of your lab, such as labs/mynewlab.md. It is expected that your lab repository will have the same name so keep that in mind.

3. In the Proposal Template, there is an entry for sponsor(s). Although not required, proposers are encouraged to seek a sponsor who can help them create ties with the rest of the Hyperledger community and ensure that the proposal is cogent and novel (in conception, proposed execution, or interested community).
   
   To find sponsors:

   1. use your connections to existing projects and ask maintainers,
   2. find working groups or projects with affinities to the proposed lab and pitch the project (good to have the template already filled out) in associated channels and/or mailing lists. The WG chairs emails, the maintainers contacts etc can be found on the wiki or github. Make personal appeals if you can. Every repository contains a MAINTAINERS file that lists the current maintainers with their contact information and you can reach them all by posting to the Maintainers list.

4. Commit your changes with proper sign-off. This means that your commit log message must contain a line that looks like the following one, with your actual name and email address:

    Signed-off-by: John Doe <[email protected]>
   

   Adding the -s flag to your git commit command will add that line automatically. You can also add it manually as part of your commit log message or add it afterwards with git commit --amend -s.

5. Submit a Pull Request.

The labs stewards will then review your proposal. Like sponsors, stewards do not have a responsibility beyond this; ongoing work like contributing code or reviews is not tied to their role as stewards. In reviewing the proposal, the stewards make sure that the proposal is cogent and novel (in conception, proposed execution, or interested community).

IMPORTANT: It is up to the proposer to ensure that any comments or requested changes by the lab stewards are addressed. Failure to do so may delay the approval of your proposal.

Bringing in an existing repository

By default the Lab stewards will create a new repository for you to start from but if you have an existing github repo you would like to bring to your proposed lab you have the option to request for that repo to be reused instead. This is however only possible if every commit in your existing repo is signed-off so there is no DCO related issues. If that is not the case, you have two options:

1. bring your code by squashing all of your commits into a single first commit made against your new lab repo with your sign-off.

2. amend the commit history to include DCO sign-off for each of the commits. The Hyperledger Indy community has documented steps to fix DCO on previous commits. Also, the Fix DCO Guide from src-d contains some different steps you can take.

IMPORTANT: Regardless of which option you use, please be sure that the past committers to your project agree to the DCO.

Archiving

Stewards are responsible for curating the set of labs, archiving (see below) those that become dormant or unresponsive for an extended period (3+ months), or are explicitly deemed by the committers to be deprecated/obsoleted.

Deprecated, obsoleted, or dormant labs (as defined above) will be marked as "archived" in GitHub; that signifies that the lab is no longer maintained. Archived labs are read-only, and they can be moved back out of the archives, if there is interest in reviving them.

License requirement

All Hyperledger software must be made available under an Apache 2.0 license. This applies to Labs. Please, make sure to license all incoming code and new code accordingly, and ensure that all commits are made with proper sign-off so that no DCO related issue is introduced.

Code of Conduct

All Hyperledger community members must adhere to the Code of Conduct.

hl-starterkit's Issues

Unable to create channel after fabric network up. error at orderer logs.

2021-04-23 11:29:52.027 UTC [orderer.common.server] Start -> INFO 00b Beginning to serve requests
2021-04-23 11:30:17.741 UTC [cauthdsl] deduplicate -> ERRO 00c Principal deserialization failure (the supplied identity is not valid: x509: certificate signed by unknown authority) for identity 0
2021-04-23 11:30:17.742 UTC [cauthdsl] deduplicate -> ERRO 00d Principal deserialization failure (the supplied identity is not valid: x509: certificate signed by unknown authority) for identity 0
2021-04-23 11:30:17.742 UTC [orderer.common.broadcast] ProcessMessage -> WARN 00e [channel: mychannel] Rejecting broadcast of config message from 172.24.0.12:49964 because of error: error validating channel creation transaction for new channel 'mychannel', could not succesfully apply update to template configuration: error authorizing update: error validating DeltaSet: policy for [Group] /Channel/Application not satisfied: implicit policy evaluation failed - 0 sub-policies were satisfied, but this policy requires 1 of the 'Admins' sub-policies to be satisfied
2021-04-23 11:30:17.742 UTC [comm.grpc.server] 1 -> INFO 00f streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Broadcast grpc.peer_address=172.24.0.12:49964 grpc.code=OK grpc.call_duration=4.320992ms
2021-04-23 11:30:17.744 UTC [common.deliver] Handle -> WARN 010 Error reading from 172.24.0.12:49962: rpc error: code = Canceled desc = context canceled

Error on generating default config files - /tmp/example.com.tar.gz file already exists.

Error on console, stating file already exists on /tmp/example.com.tar.gz, But able to receive emails with attachment.

Peer node getting exit on Fabric version 1.4.3 randomly.

docker logs peer0.org1.example.com
2021-04-23 10:07:22.173 UTC [nodeCmd] serve -> INFO 001 Starting peer:
Version: 1.4.3
Commit SHA: b8c4a6a
Go version: go1.11.5
OS/Arch: linux/amd64
Chaincode:
Base Image Version: 0.4.15
Base Docker Namespace: hyperledger
Base Docker Label: org.hyperledger.fabric
Docker Namespace: hyperledger
2021-04-23 10:07:22.175 UTC [ledgermgmt] initialize -> INFO 002 Initializing ledger mgmt
2021-04-23 10:07:22.175 UTC [kvledger] NewProvider -> INFO 003 Initializing ledger provider
2021-04-23 10:07:22.500 UTC [kvledger] NewProvider -> INFO 004 ledger provider Initialized
2021-04-23 10:07:22.723 UTC [couchdb] handleRequest -> WARN 005 Retrying couchdb request in 125ms. Attempt:1 Error:Get http://couchdb0:5984/: dial tcp 172.20.0.4:5984: connect: connection refused
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x63 pc=0x7f4fec38c259]

runtime stack:
runtime.throw(0x128d76a, 0x2a)
/opt/go/src/runtime/panic.go:608 +0x72
runtime.sigpanic()
/opt/go/src/runtime/signal_unix.go:374 +0x2f2

goroutine 31 [syscall]:
runtime.cgocall(0xe5acb0, 0xc000351600, 0x29)
/opt/go/src/runtime/cgocall.go:128 +0x5e fp=0xc0003515c8 sp=0xc000351590 pc=0x4039ee
net._C2func_getaddrinfo(0xc0000b4094, 0x0, 0xc0002120c0, 0xc0000b6250, 0x0, 0x0, 0x0)
_cgo_gotypes.go:91 +0x55 fp=0xc000351600 sp=0xc0003515c8 pc=0x6174f5
net.cgoLookupIPCNAME.func1(0xc0000b4094, 0x0, 0xc0002120c0, 0xc0000b6250, 0x9, 0x9, 0x0)
/opt/go/src/net/cgo_unix.go:149 +0x131 fp=0xc000351648 sp=0xc000351600 pc=0x61cc21
net.cgoLookupIPCNAME(0xc0000b40c0, 0x8, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
/opt/go/src/net/cgo_unix.go:149 +0x153 fp=0xc000351738 sp=0xc000351648 pc=0x618ab3
net.cgoIPLookup(0xc000167800, 0xc0000b40c0, 0x8)
/opt/go/src/net/cgo_unix.go:201 +0x4d fp=0xc0003517c8 sp=0xc000351738 pc=0x61916d
runtime.goexit()
/opt/go/src/runtime/asm_amd64.s:1333 +0x1 fp=0xc0003517d0 sp=0xc0003517c8 pc=0x45de51
created by net.cgoLookupIP
/opt/go/src/net/cgo_unix.go:211 +0xad

Second channel name was not adding a count

Have issue in Docker Swarm templates. Throwing errors on config generation

Error for references 👍 ls: crypto-config/peerOrganizations/org1.example.com/ca/: No such file or directory
ls: crypto-config/peerOrganizations/org1.example.com/tlsca/: No such file or directory
ls: crypto-config/peerOrganizations/org2.example.com/ca/: No such file or directory
ls: crypto-config/peerOrganizations/org2.example.com/tlsca/: No such file or directory

Collecting the Host information for Swarm Setup

By default Orderer & Org1 will use same host, hence host & login details for swarm setup and file copy
Give your ORG_1 Hostname :testhost1
testhost1
ping: bad address 'testhost1'

testhost1 Not Pingable
Give your ORG_1 IPAddress :1.1.1.1
ping: permission denied (are you root?)
1.1.1.1 Not Pingable, Contact SYSADMIN or Check your DNS or Network Configuration

Give your ORG_2 Hostname :1.1.1.1
1.1.1.1
ping: permission denied (are you root?)

1.1.1.1 Not Pingable
Give your ORG_2 IPAddress :testhost2
ping: bad address 'testhost2'
testhost2 Not Pingable, Contact SYSADMIN or Check your DNS or Network Configuration

Updating Hostinformation for Swarm Setup

Transfering the Crypro artifacts to lab for Sync swarm Network

Considering the below

1, The Pre requestie installed i.e Docker, Fabric binary, Images, go, etc.

2, Following the same folder structure in remote host. i.e. ~/fabric-samples/

Initialising the Docker Swarm

Cleaning if any previous installs of docker swarm network from current node...
Provide a Network Interface name for swarm initialize :abc1
Docker Swarm Network Initialised
/usr/src/app/HLF/hlstartup/02_swarmstart.sh: line 243: docker: command not found
/usr/src/app/HLF/hlstartup/02_swarmstart.sh: line 247: docker: command not found
/usr/src/app/HLF/hlstartup/02_swarmstart.sh: line 250: docker: command not found
Swarm master IP:

Joining the Host: lab to Docker swarm Network

provide the username for remote host, ensure the user has admin rights: lab
Provide a Username for host : lab to login:

error in send Config file on email

At the end when tool ask for to generate config file and send it on my email this secetion is not working and giving error i cant send email and canot get the config file