分析Fabric示例网络./byfn.sh up 的输出

最新推荐文章于 2023-03-19 14:46:13 发布
最新推荐文章于 2023-03-19 14:46:13 发布
阅读量1.8k 收藏 3
点赞数 1
分类专栏： Fabric 文章标签： docker 区块链 linux
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_18807043/article/details/105448013
版权

Starting for channel ‘mychannel’ with CLI timeout of ‘10’ seconds and CLI delay of ‘3’ seconds
Continue? [Y/n] y
// byfn.sh line:119 /
// 检查版本 //
proceeding …
LOCAL_VERSION=2.0.0
DOCKER_IMAGE_VERSION=2.0.0
// byfn.sh line:297 generateCerts ///
// 如果存在目录crypto-config，则删除之
/root/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/first-network/…/bin/cryptogen

##########################################################

Generate certificates using cryptogen tool

##########################################################

// 调用cryptogen ///
// 在当前目录下创建子目录crypto-configls，分层生成各成员的公私钥 /
// crypto-config.yaml描述各成员构成 //

  • cryptogen generate --config=./crypto-config.yaml
    org1.example.com
    org2.example.com
  • res=0
  • set +x

Generate CCP files for Org1 and Org2
// byfn.sh line:321 调用ccp-generate.sh ///
/ ccp-generate.sh用ccp-template.json,ccp-template.yaml为模板，生成4个文件 /
// connection-org1.json,connection-org1.yaml
// connection-org2.json, connection-org2.yaml
/ 用于设置组织的各节点端口， 公钥证书 /
/ 如果有3个或更多组织，需修改ccp-generate.sh
/ 在byfn.sh里并没有用到上述产生的4个文件
/root/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/first-network/…/bin/configtxgen
##########################################################
######### Generating Orderer Genesis block ##############
##########################################################
// byfn.sh line:375 ///
// configtxgen产生创世纪块genesis.block，用到配置文件configtx.yaml ///
SampleMultiNodeEtcdRaft:为Raft排序服务创建创世纪块,在configtx.yaml中定义///
configtx.yaml定义网络参数，例如背书策略，打包区块的时间，区块大小等 ///
channelID指定系统通道的ID /
configtx.yaml定义了不少参数，需要单独描述

  • configtxgen -profile SampleMultiNodeEtcdRaft -channelID byfn-sys-channel -outputBlock ./channel-artifacts/genesis.block
    2020-04-10 08:39:41.348 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration
    2020-04-10 08:39:41.375 CST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 002 orderer type: etcdraft
    2020-04-10 08:39:41.375 CST [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-04-10 08:39:41.375 CST [common.tools.configtxgen.localconfig] Load -> INFO 004 Loaded configuration: /root/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/first-network/configtx.yaml
    2020-04-10 08:39:41.377 CST [common.tools.configtxgen] doOutputBlock -> INFO 005 Generating genesis block
    2020-04-10 08:39:41.377 CST [common.tools.configtxgen] doOutputBlock -> INFO 006 Writing genesis block
  • res=0
  • set +x

#################################################################

Generating channel configuration transaction ‘channel.tx’

#################################################################
// configtxgen产生通道channel.tx，用到配置文件configtx.yaml ///
// TwoOrgsChannel:在configtx.yaml定义，定义通道的共识、容量等
channelID指定通道的ID，不是系统通道 /

  • configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID mychannel
    2020-04-10 08:39:41.406 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration
    2020-04-10 08:39:41.434 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/first-network/configtx.yaml
    2020-04-10 08:39:41.434 CST [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 003 Generating new channel configtx
    2020-04-10 08:39:41.436 CST [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 004 Writing new channel tx
  • res=0
  • set +x

#################################################################
####### Generating anchor peer update for Org1MSP ##########
#################################################################
// configtxgen设置组织1的锚节点，用到配置文件configtx.yaml ///
// 产生文件Org1MSPanchors.tx

  • configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID mychannel -asOrg Org1MSP
    2020-04-10 08:39:41.473 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration
    2020-04-10 08:39:41.500 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/first-network/configtx.yaml
    2020-04-10 08:39:41.500 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 003 Generating anchor peer update
    2020-04-10 08:39:41.502 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 004 Writing anchor peer update
  • res=0
  • set +x

#################################################################
####### Generating anchor peer update for Org2MSP ##########
#################################################################
// configtxgen设置组织2的锚节点，用到配置文件configtx.yaml ///
// 产生文件Org2MSPanchors.tx

  • configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID mychannel -asOrg Org2MSP
    2020-04-10 08:39:41.534 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration
    2020-04-10 08:39:41.565 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/first-network/configtx.yaml
    2020-04-10 08:39:41.565 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 003 Generating anchor peer update
    2020-04-10 08:39:41.567 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 004 Writing anchor peer update
  • res=0
  • set +x
    // configtxgen主要用于创建创世纪区块、通道配置、锚节点配置 ///
    / 完成上述步骤后，在channel-artivacts目录下生成4个文件 //
    / channel.tx genesis.block Org1MSPanchors.tx Org2MSPanchors.tx ///

// byfn.sh line:167 ，执行如下命令，启动各节点的docker ///
/ IMAGE_TAG=latest /
/ docker-compose -f docker-compose-cli.yaml -f docker-compose-etcdraft2.yaml up -d //
/ docker-compose-etcdraft2.yaml启动4个order(order2~order5)节点的docker /
/ docker-compose-cli.yaml启动6个节点 (order，4个peer，cli)节点的docker /
Creating network “net_byfn” 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_peer1.org1.example.com” with default driver
Creating volume “net_peer0.org2.example.com” with default driver
Creating volume “net_peer1.org2.example.com” with default driver
Creating volume “net_orderer2.example.com” with default driver
Creating volume “net_orderer3.example.com” with default driver
Creating volume “net_orderer4.example.com” with default driver
Creating volume “net_orderer5.example.com” with default driver
Creating orderer.example.com … done
Creating peer1.org2.example.com … done
Creating orderer4.example.com … done
Creating orderer5.example.com … done
Creating peer0.org1.example.com … done
Creating peer1.org1.example.com … done
Creating peer0.org2.example.com … done
Creating orderer3.example.com … done
Creating orderer2.example.com … done
Creating cli … done
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
83c79cc4449b hyperledger/fabric-tools:latest “/bin/bash” 3 seconds ago Up Less than a second cli
b252e866db77 hyperledger/fabric-orderer:latest “orderer” 8 seconds ago Up 2 seconds 7050/tcp, 0.0.0.0:8050->8050/tcp orderer2.example.com
a4593529e3c4 hyperledger/fabric-peer:latest “peer node start” 8 seconds ago Up 3 seconds 7051/tcp, 0.0.0.0:9051->9051/tcp peer0.org2.example.com
da8fc277ffc4 hyperledger/fabric-peer:latest “peer node start” 8 seconds ago Up 3 seconds 0.0.0.0:7051->7051/tcp peer0.org1.example.com
1f2df772275e hyperledger/fabric-orderer:latest “orderer” 8 seconds ago Up 2 seconds 7050/tcp, 0.0.0.0:9050->9050/tcp orderer3.example.com
523cd6e05c01 hyperledger/fabric-orderer:latest “orderer” 8 seconds ago Up 3 seconds 7050/tcp, 0.0.0.0:11050->11050/tcp orderer5.example.com
1dbae684457c hyperledger/fabric-peer:latest “peer node start” 8 seconds ago Up 2 seconds 7051/tcp, 0.0.0.0:8051->8051/tcp peer1.org1.example.com
387057e05649 hyperledger/fabric-orderer:latest “orderer” 8 seconds ago Up 3 seconds 7050/tcp, 0.0.0.0:10050->10050/tcp orderer4.example.com
bb17140ee7d6 hyperledger/fabric-peer:latest “peer node start” 8 seconds ago Up 2 seconds 7051/tcp, 0.0.0.0:10051->10051/tcp peer1.org2.example.com
f422e2d45ee5 hyperledger/fabric-orderer:latest “orderer” 8 seconds ago Up 3 seconds 0.0.0.0:7050->7050/tcp orderer.example.com
c9bea8330020 hyperledger/fabric-tools:amd64-1.4.2 “//bin/bash -c 'FABR…” 16 minutes ago Exited (0) 16 minutes ago heuristic_euler
b1fa5fd87acc hyperledger/fabric-tools:amd64-1.4.2 “//bin/bash -c 'FABR…” 16 minutes ago Exited (0) 16 minutes ago strange_mahavira
f09fe7b6e68c bf68857e10c3 “/bin/sh -c 'bash /t…” 17 minutes ago Exited (1) 16 minutes ago cocky_lalande
7d23774ee827 515ff2fd27cc “/bin/sh -c 'bash /t…” 25 minutes ago Exited (1) 23 minutes ago hopeful_raman
9cd87922b2ed hyperledger/fabric-tools:amd64-1.4.2 “//bin/bash -c 'FABR…” 25 minutes ago Exited (0) 25 minutes ago dreamy_shannon
b707ff006624 hyperledger/fabric-tools:amd64-1.4.2 “//bin/bash -c 'FABR…” 25 minutes ago Exited (0) 25 minutes ago quirky_shannon
953e091b9583 98ff39fde1c7 “/bin/sh -c 'bash /t…” 33 minutes ago Exited (1) 25 minutes ago cocky_moore
a2789aa5ac5b hyperledger/fabric-tools:amd64-1.4.2 “//bin/bash -c 'FABR…” 3 days ago Exited (0) 3 days ago quizzical_thompson
667f70baabe0 hyperledger/fabric-tools:amd64-1.4.2 “//bin/bash -c 'FABR…” 3 days ago Exited (0) 3 days ago charming_lichterman
805216a77308 1d016c34e9f6 “/bin/sh -c 'bash /t…” 3 days ago Exited (1) 3 days ago nifty_wiles
b97772fe2542 fa953080b404 “/bin/sh -c 'bash /t…” 3 days ago Exited (1) 3 days ago optimistic_jepsen
Sleeping 15s to allow Raft cluster to complete booting
Vendoring Go dependencies …
~/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/chaincode/abstore/go ~/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/first-network
~/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/first-network
Finished vendoring Go dependencies

// byfn.sh line:186 ///
// 到这里时，共启动了10个docker(4 peers, 5 orderers,1 cli ) //
// 下面将在cli docker里执行脚本 /
// docker exec cli scripts/script.sh mychannel 3 go 10 false ///
/ script.sh在一个单独的docker里设置网络(例如将节点添加到通道中) /
script.sh还将在peer节点上安装、测试链码
script.sh完成后，将新启动3个docker，与链码有关 /

/ | | | / \ | _ \ | |
_ \ | | / _ \ | |) | | |
) | | | / ___ \ | _ < | |
|/ || // _\ || _\ |_|

Build your first network (BYFN) end-to-end test

Channel name : mychannel
Creating channel…

  • peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
  • res=0
  • set +x
    2020-04-10 00:40:05.924 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
    2020-04-10 00:40:05.945 UTC [cli.common] readBlock -> INFO 002 Expect block, but got status: &{NOT_FOUND}
    2020-04-10 00:40:05.948 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
    2020-04-10 00:40:06.150 UTC [cli.common] readBlock -> INFO 004 Expect block, but got status: &{SERVICE_UNAVAILABLE}
    2020-04-10 00:40:06.153 UTC [channelCmd] InitCmdFactory -> INFO 005 Endorser and orderer connections initialized
    2020-04-10 00:40:06.358 UTC [cli.common] readBlock -> INFO 006 Expect block, but got status: &{SERVICE_UNAVAILABLE}
    2020-04-10 00:40:06.367 UTC [channelCmd] InitCmdFactory -> INFO 007 Endorser and orderer connections initialized
    2020-04-10 00:40:06.571 UTC [cli.common] readBlock -> INFO 008 Expect block, but got status: &{SERVICE_UNAVAILABLE}
    2020-04-10 00:40:06.581 UTC [channelCmd] InitCmdFactory -> INFO 009 Endorser and orderer connections initialized
    2020-04-10 00:40:06.784 UTC [cli.common] readBlock -> INFO 00a Expect block, but got status: &{SERVICE_UNAVAILABLE}
    2020-04-10 00:40:06.794 UTC [channelCmd] InitCmdFactory -> INFO 00b Endorser and orderer connections initialized
    2020-04-10 00:40:06.999 UTC [cli.common] readBlock -> INFO 00c Expect block, but got status: &{SERVICE_UNAVAILABLE}
    2020-04-10 00:40:07.010 UTC [channelCmd] InitCmdFactory -> INFO 00d Endorser and orderer connections initialized
    2020-04-10 00:40:07.216 UTC [cli.common] readBlock -> INFO 00e Received block: 0
    ===================== Channel ‘mychannel’ created =====================

Having all peers join the channel…

  • peer channel join -b mychannel.block

  • res=0

  • set +x
    2020-04-10 00:40:07.298 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
    2020-04-10 00:40:07.343 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
    ===================== peer0.org1 joined channel ‘mychannel’ =====================

  • peer channel join -b mychannel.block

  • res=0

  • set +x
    2020-04-10 00:40:10.453 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
    2020-04-10 00:40:10.481 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
    ===================== peer1.org1 joined channel ‘mychannel’ =====================

  • peer channel join -b mychannel.block

  • res=0

  • set +x
    2020-04-10 00:40:13.580 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
    2020-04-10 00:40:13.607 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
    ===================== peer0.org2 joined channel ‘mychannel’ =====================

  • peer channel join -b mychannel.block

  • res=0

  • set +x
    2020-04-10 00:40:16.713 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
    2020-04-10 00:40:16.740 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
    ===================== peer1.org2 joined channel ‘mychannel’ =====================

Updating anchor peers for org1…

  • peer channel update -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org1MSPanchors.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
  • res=0
  • set +x
    2020-04-10 00:40:19.846 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
    2020-04-10 00:40:19.862 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update
    ===================== Anchor peers updated for org ‘Org1MSP’ on channel ‘mychannel’ =====================

Updating anchor peers for org2…

  • peer channel update -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/Org2MSPanchors.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

  • res=0

  • set +x
    2020-04-10 00:40:22.952 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
    2020-04-10 00:40:22.967 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update
    ===================== Anchor peers updated for org ‘Org2MSP’ on channel ‘mychannel’ =====================

  • peer lifecycle chaincode package mycc.tar.gz --path github.com/hyperledger/fabric-samples/chaincode/abstore/go/ --lang golang --label mycc_1

  • res=0

  • set +x
    ===================== Chaincode is packaged on peer0.org1 =====================

Installing chaincode on peer0.org1…

  • peer lifecycle chaincode install mycc.tar.gz
  • res=0
  • set +x
    2020-04-10 00:40:45.888 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 001 Installed remotely: response:<status:200 payload:"\nGmycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3\022\006mycc_1" >
    2020-04-10 00:40:45.888 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 002 Chaincode code package identifier: mycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3
    ===================== Chaincode is installed on peer0.org1 =====================

Install chaincode on peer0.org2…

  • peer lifecycle chaincode install mycc.tar.gz

  • res=0

  • set +x
    2020-04-10 00:40:57.744 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 001 Installed remotely: response:<status:200 payload:"\nGmycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3\022\006mycc_1" >
    2020-04-10 00:40:57.744 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 002 Chaincode code package identifier: mycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3
    ===================== Chaincode is installed on peer0.org2 =====================

  • peer lifecycle chaincode queryinstalled

  • res=0

  • set +x
    Installed chaincodes on peer:
    Package ID: mycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3, Label: mycc_1
    PackageID is mycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3
    ===================== Query installed successful on peer0.org1 on channel =====================

  • peer lifecycle chaincode approveformyorg --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --channelID mychannel --name mycc --version 1 --init-required --package-id mycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3 --sequence 1 --waitForEvent

  • set +x
    2020-04-10 00:40:57.905 UTC [cli.lifecycle.chaincode] setOrdererClient -> INFO 001 Retrieved channel (mychannel) orderer endpoint: orderer.example.com:7050
    2020-04-10 00:40:59.978 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [a503f15489e81e78918bc91c6e333f8f9a88f2671341ba6fe6f489514a3a5996] committed with status (VALID) at
    ===================== Chaincode definition approved on peer0.org1 on channel ‘mychannel’ =====================

===================== Checking the commit readiness of the chaincode definition on peer0.org1 on channel ‘mychannel’… =====================
Attempting to check the commit readiness of the chaincode definition on peer0.org1 …3 secs

  • peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name mycc --version 1 --sequence 1 --output json --init-required
  • res=0
  • set +x

{
“approvals”: {
“Org1MSP”: true,
“Org2MSP”: false
}
}
===================== Checking the commit readiness of the chaincode definition successful on peer0.org1 on channel ‘mychannel’ =====================
===================== Checking the commit readiness of the chaincode definition on peer0.org2 on channel ‘mychannel’… =====================

  • peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name mycc --version 1 --sequence 1 --output json --init-required
    Attempting to check the commit readiness of the chaincode definition on peer0.org2 …3 secs
  • res=0
  • set +x

{
“approvals”: {
“Org1MSP”: true,
“Org2MSP”: false
}
}
===================== Checking the commit readiness of the chaincode definition successful on peer0.org2 on channel ‘mychannel’ =====================

  • peer lifecycle chaincode approveformyorg --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --channelID mychannel --name mycc --version 1 --init-required --package-id mycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3 --sequence 1 --waitForEvent
  • set +x
    2020-04-10 00:41:06.289 UTC [cli.lifecycle.chaincode] setOrdererClient -> INFO 001 Retrieved channel (mychannel) orderer endpoint: orderer.example.com:7050
    2020-04-10 00:41:08.361 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [a1881a3f10ad237d78c27871fba0701ebcb14cfa2312566515012dc7030d084b] committed with status (VALID) at
    ===================== Chaincode definition approved on peer0.org2 on channel ‘mychannel’ =====================

===================== Checking the commit readiness of the chaincode definition on peer0.org1 on channel ‘mychannel’… =====================

  • peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name mycc --version 1 --sequence 1 --output json --init-required
    Attempting to check the commit readiness of the chaincode definition on peer0.org1 …3 secs
  • res=0
  • set +x

{
“approvals”: {
“Org1MSP”: true,
“Org2MSP”: true
}
}
===================== Checking the commit readiness of the chaincode definition successful on peer0.org1 on channel ‘mychannel’ =====================
===================== Checking the commit readiness of the chaincode definition on peer0.org2 on channel ‘mychannel’… =====================
Attempting to check the commit readiness of the chaincode definition on peer0.org2 …3 secs

  • peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name mycc --version 1 --sequence 1 --output json --init-required
  • res=0
  • set +x

{
“approvals”: {
“Org1MSP”: true,
“Org2MSP”: true
}
}
===================== Checking the commit readiness of the chaincode definition successful on peer0.org2 on channel ‘mychannel’ =====================

  • peer lifecycle chaincode commit -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --channelID mychannel --name mycc --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:9051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt --version 1 --sequence 1 --init-required
  • res=0
  • set +x
    2020-04-10 00:41:16.996 UTC [chaincodeCmd] ClientWait -> INFO 001 txid [31e1703493701adbda39d31f8ce3b4aea18f07f120c9b056fd3034530c8047d4] committed with status (VALID) at peer0.org2.example.com:9051
    2020-04-10 00:41:16.997 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [31e1703493701adbda39d31f8ce3b4aea18f07f120c9b056fd3034530c8047d4] committed with status (VALID) at peer0.org1.example.com:7051
    ===================== Chaincode definition committed on channel ‘mychannel’ =====================

===================== Querying chaincode definition on peer0.org1 on channel ‘mychannel’… =====================
Attempting to Query committed status on peer0.org1 …3 secs

  • peer lifecycle chaincode querycommitted --channelID mychannel --name mycc
  • res=0
  • set +x

Committed chaincode definition for chaincode ‘mycc’ on channel ‘mychannel’:
Version: 1, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc, Approvals: [Org1MSP: true, Org2MSP: true]
===================== Query chaincode definition successful on peer0.org1 on channel ‘mychannel’ =====================
===================== Querying chaincode definition on peer0.org2 on channel ‘mychannel’… =====================
Attempting to Query committed status on peer0.org2 …3 secs

  • peer lifecycle chaincode querycommitted --channelID mychannel --name mycc
  • res=0
  • set +x

Committed chaincode definition for chaincode ‘mycc’ on channel ‘mychannel’:
Version: 1, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc, Approvals: [Org1MSP: true, Org2MSP: true]
===================== Query chaincode definition successful on peer0.org2 on channel ‘mychannel’ =====================

  • peer chaincode invoke -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n mycc --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:9051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt --isInit -c ‘{“Args”:[“Init”,“a”,“100”,“b”,“100”]}’
  • res=0
  • set +x
    2020-04-10 00:41:23.395 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Chaincode invoke successful. result: status:200
    ===================== Invoke transaction successful on peer0.org1 peer0.org2 on channel ‘mychannel’ =====================

Querying chaincode on peer0.org1…
===================== Querying on peer0.org1 on channel ‘mychannel’… =====================
Attempting to Query peer0.org1 …3 secs

  • peer chaincode query -C mychannel -n mycc -c ‘{“Args”:[“query”,“a”]}’
  • res=0
  • set +x

100
===================== Query successful on peer0.org1 on channel ‘mychannel’ =====================
Sending invoke transaction on peer0.org1 peer0.org2…

  • peer chaincode invoke -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n mycc --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:9051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt -c ‘{“Args”:[“invoke”,“a”,“b”,“10”]}’
  • res=0
  • set +x
    2020-04-10 00:41:26.606 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Chaincode invoke successful. result: status:200
    ===================== Invoke transaction successful on peer0.org1 peer0.org2 on channel ‘mychannel’ =====================

Querying chaincode on peer0.org1…
===================== Querying on peer0.org1 on channel ‘mychannel’… =====================

  • peer chaincode query -C mychannel -n mycc -c ‘{“Args”:[“query”,“a”]}’
    Attempting to Query peer0.org1 …3 secs
  • res=0
  • set +x

90
===================== Query successful on peer0.org1 on channel ‘mychannel’ =====================
Installing chaincode on peer1.org2…

  • peer lifecycle chaincode install mycc.tar.gz
  • res=0
  • set +x
    2020-04-10 00:41:40.837 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 001 Installed remotely: response:<status:200 payload:"\nGmycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3\022\006mycc_1" >
    2020-04-10 00:41:40.837 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 002 Chaincode code package identifier: mycc_1:4622fb602aa60c6368716a70474dc9d9ba2776200f70eccca07a4df4360eaff3
    ===================== Chaincode is installed on peer1.org2 =====================

Querying chaincode on peer1.org2…
===================== Querying on peer1.org2 on channel ‘mychannel’… =====================

  • peer chaincode query -C mychannel -n mycc -c ‘{“Args”:[“query”,“a”]}’
    Attempting to Query peer1.org2 …3 secs
  • res=0
  • set +x

90
===================== Query successful on peer1.org2 on channel ‘mychannel’ =====================

========= All GOOD, BYFN execution completed ===========

| | | \ | | | _ \
| | | | | | | | |
| | | |\ | | || |
|_____| || _| |____/

完成上述步骤后，将产生一些区块 ///
docker exec cli peer channel getinfo -c mychannel 获取指定通道上的区块信息
2020-04-11 01:59:17.429 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Blockchain info: {“height”:8,“currentBlockHash”:“1A+7SUu4crYK6eprW9ZBmmkSvHISCMiSBA2O5RnfRtE=”,“previousBlockHash”:“5rxU3ntHIEtbKIfUT58lkSQ5NvLGD1DuXAQ39lbF8NQ=”}

docker exec cli peer channel fetch 7 -c mychannel
获取指定高度(区块号)的区块，存储在docker里
2020-04-11 02:01:10.668 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2020-04-11 02:01:10.670 UTC [cli.common] readBlock -> INFO 002 Received block: 7

docker cp cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/mychannel_7.block .
从docker里复制区块7的文件到本地
configtxgen -inspectBlock mychannel_7.block 将区块文件转换成json格式

看聊效
关注
  • 1
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
阿里云上运行./byfn.sh -m up失败解决办法
h363659487的博客
09-12 1464
在fabric-samples/first-network#目录下，修改如下几个文件： docker-compose-cli.yaml: 在cli -&gt; environment下面添加： - GODEBUG=netdns=go base/docker-compose-base.yaml 在 orderer.example.com的environment下面添加： - GODEB...
byfn.sh 创建fabric网络官方实例
10-27
build you first net 文件
fabric-sample配置常见错误解析
tianlongtc的博客
06-29 9151
1、运行docker-compose -f docker-compose-simple.yaml up 出现下面错误 ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information. 解决：https://github.com/docker/compose...
Fabric2.0.0环境搭建及链码操作详解
yuch_hong的博客
07-24 1954
安装软件 更新源 sudo apt-get update 安装Go cd /usr/local 上传go的压缩包 sudo rz 解压压缩包 sudo tar -zxf go1.14.4.linux-amd64.tar.gz 配置环境 vim ~/.bashrc export GOROOT=/usr/local/go export GOPATH=/opt/gopath export PATH=$PATH:$GOROOT/bin/:$GOPATH/bin s..
手动搭建hyperledger fabric v2.x 生产网络（四）创建通道，链码的生命周期
每一个不曾起舞的日子，都是对生命的辜负
04-21 2991
官方文档地址：https://hyperledger-fabric.readthedocs.io/zh_CN/release-2.2/command_ref.html 命令参考： peer channel [command]相关命令：允许管理员在 Peer节点上执行通道的相关操作 相关子命令： peer channel create 创建通道 peer channel fetch peer channel getinfo peer channel join 加入通道 peer c
Fabric v2.3测试网络 - 在通道中启动链码返回结果分析
ling1998的博客
10-31 1151
Fabric v2.3 测试网络，在通道中启动链码命令如下： ./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go -ccl go 以上命令操作分为以下步骤： 1.打包智能合约 2. 安装链码包 3. 通道中组织批准链码定义 4. 提交链码定义到通道中 要安装的智能合约asset-transfer-basic路径： 若上面命令执行失败，可手动安装go依赖（第一次执行没有vendo...
fabric联盟链笔记（9）
01-07
在first-network目录下运行byfn.sh 提示/bin/bash^M: 坏的解释器: 没有那个文件或目录 解决方案 执行 sed -i 's/\r$//' byfn.sh 将windows下的转义符替换成linux可以识别的转义符 再次运行即可 第二个问题 这是...
手动搭建fabric单机多节点网络.pdf
07-20
现在，你可以使用`docker-compose`或`byfn.sh`脚本来启动网络，加入通道，并进行链码部署和调用。 总结来说，手动搭建Hyperledger Fabric单机多节点网络涉及到的关键步骤包括：设置环境变量，使用cryptogen生成加密...
fabric-samples.zip
05-15
在“binary”文件夹中，bin目录通常存放的是执行脚本和可执行文件，这些文件是用于启动和管理Fabric网络的关键工具，比如“byfn.sh”（基本功能网络）脚本，可以快速搭建一个简单的两节点网络，用于演示Fabric的基本...
fabric-sdk-java+ springBoot 简单invoke和query引用示例
03-11
2，注释掉docker-compose-e2e-template.yaml，以及base目录下包含_TLS_ENABLED字段的配置，并启动网络，./byfn.sh up 3，将生成的crypto-config文件夹拷贝到：项目所在盘:/data/crypto-config 4,修改Config.java中...
HyperLedger Fabric 1.0.5安装、测试和常见问题汇总
06-16
Hyperledger是被业界非常看到的联盟链的实现，包括IBM、Intel、R3、各个大型商业银行等都参与其中，带给我们关于区块链技术与软件工业、金融、保险、物流等领域碰撞结合的想象空间；在这个联盟中，有超过1/4的成员都来自中国，这更是我们对于它的一举一动都非常关注。很大程度上，Hyperledger和它背后的联盟体系就代表着区块链在产业环境中的未来。 写下此教程，让后面学习的同学少走弯路。
成功解决Chaincode definition approved on peer0.org1 on channel ‘mychannel‘ failed Deploying chaincode
GniLAY1022的博客
10-14 3373
执行以下指令时报错 ./network.sh deployCC Error: proposal failed with status: 500 - channel 'mychannel' not found Chaincode definition approved on peer0.org1 on channel 'mychannel' failed Deploying chaincode failed 原因是没有在创建通道的情况下部署链码 执行以下指令创建通道 ./network.sh createC
使用addOrg3: Expect block, but got status: &{NOT_FOUND}
qq_42482245的博客
04-14 649
2022-04-14 08:09:07.950 UTC 0002 INFO [cli.common] readBlock -> Expect block, but got status: &{NOT_FOUND} Error: can't read the block: &{NOT_FOUND} Fetching config block from orderer has failed ERROR !!!! Unable to join Org3 peers to network
./byfn.sh -m up 启动fabric时 出现No such container: cli
qq_53714459的博客
05-04 747
问题: ./byfn.sh up 启动fabric时失败，出现No such container: cli（没有这样的容器:cli） 原因:系统缺少工具库 解决:执行如下命令 执行完后输入 docker-compase -version 出现如下结果即成功 此时输入进入如下位置输入 ./byfn.sh up 稍等片刻即可测试成功 参考:https://bbs.huaweicloud.com/blogs/detail/286823 ...
安装fabric链码
qq_15799869的博客
07-05 3122
[root@iZ8vbjcbks7pzj9po96hleZ test-network]# go env -w GOPROXY=https://goproxy.cn,direct [root@iZ8vbjcbks7pzj9po96hleZ test-network]# ./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go -ccl go Using docker and docker-compose deployi
Hyperledegr Fabric BYFN 3: byfn.sh up 操作分析 docker-compose部署
小鸟达子的博客
02-21 378
byfn.sh up 操作分析 docker-compose部署 # Generate the needed certificates, the genesis block and start the network. function networkUp() { checkPrereqs # generate artifacts if they don't exist if [ ! ...
Fabric 2.2 测试网络 ccp-template.yaml 详解
weixin_43811576的博客
03-19 102
这是一个YAML文件，用于定义Hyperledger Fabric网络中的组织、对等体和证书颁发机构等信息。
docker 部署 hyperleger fabric v2.2.0 网络环境
boymy
11-02 394
[toc] 环境 GoSDK安装 下载 GO SDK wget https://golang.google.cn/dl/go1.17.3.linux-amd64.tar.gz tar xfv go1.14.4.linux-amd64.tar.gz -C /usr/local 配置环境变量 在文件最后添加以下内容 vim /etc/profile export PATH=$PATH:/usr/l...
source /etc/profile mkdir -p /home/ubuntu/gopath/src/github.com/hyperledger cd /home/ubuntu/gopath/src/github.com/hyperledger cp /resource/docker-compose /usr/local/bin chmod +x /usr/local/bin/docker-compose cp /resource/fabric-samples.tar.gz /home/ubuntu/gopath/src/github.com/hyperledger cd /home/ubuntu/gopath/src/github.com/hyperledger tar -xf ./fabric-samples.tar.gz source /etc/profile cd /home/ubuntu/gopath/src/github.com/hyperledger/fabric-samples/scripts ./bootstrap.sh 1.4.0 1.4.0 0.4.14 cd /home/ubuntu/gopath/src/github.com/hyperledger/fabric-samples/first-network ./byfn.sh up -s couchdb docker-compose -f docker-compose-cli.yaml -f docker-compose-couch.yaml -f docker-compose-kafka.yaml start ../bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx channel-artifacts/test.tx -channelID test
最新发布
06-07
这段命令的作用是： 1. 执行 `source /etc/profile` 命令，使得之前添加的 Go 语言环境变量生效； 2. 执行 `mkdir -p /home/ubuntu/gopath/src/github.com/hyperledger` 命令，创建一个目录用于存放 Hyperledger Fabric 的源代码； 3. 执行 `cd /home/ubuntu/gopath/src/github.com/hyperledger` 命令，切换到 Hyperledger Fabric 代码存放的目录； 4. 执行 `cp /resource/docker-compose /usr/local/bin` 命令，将预设好的 `docker-compose` 文件拷贝到 `/usr/local/bin` 目录下； 5. 执行 `chmod +x /usr/local/bin/docker-compose` 命令，添加可执行权限； 6. 执行 `cp /resource/fabric-samples.tar.gz /home/ubuntu/gopath/src/github.com/hyperledger` 命令，将预设好的 Hyperledger Fabric 样例程序压缩包拷贝到 `github.com/hyperledger` 目录下； 7. 执行 `cd /home/ubuntu/gopath/src/github.com/hyperledger` 命令，切换到 Hyperledger Fabric 样例程序所在的目录； 8. 执行 `tar -xf ./fabric-samples.tar.gz` 命令，解压 Hyperledger Fabric 样例程序压缩包； 9. 执行 `source /etc/profile` 命令，重新加载 Go 语言环境变量； 10. 执行 `cd /home/ubuntu/gopath/src/github.com/hyperledger/fabric-samples/scripts` 命令，切换到 Hyperledger Fabric 样例程序的脚本目录； 11. 执行 `./bootstrap.sh 1.4.0 1.4.0 0.4.14` 命令，安装 Hyperledger Fabric 所需的依赖组件； 12. 执行 `cd /home/ubuntu/gopath/src/github.com/hyperledger/fabric-samples/first-network` 命令，切换到 Hyperledger Fabric 样例程序的第一个网络目录； 13. 执行 `./byfn.sh up -s couchdb` 命令，启动第一个网络，并使用 CouchDB 作为状态数据库； 14. 执行 `docker-compose -f docker-compose-cli.yaml -f docker-compose-couch.yaml -f docker-compose-kafka.yaml start` 命令，启动 Fabric 网络中的 Docker 容器； 15. 执行 `../bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx channel-artifacts/test.tx -channelID test` 命令，使用 configtxgen 工具生成通道交易配置文件和创世块配置文件。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值