Fabric的官方DEMO Building Your First Network的启动日志分析

最新推荐文章于 2022-12-06 20:41:22 发布
最新推荐文章于 2022-12-06 20:41:22 发布
阅读量873 收藏 1
点赞数
分类专栏： 区块链
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u010833547/article/details/79448755
版权

当你按照官方的指示部署好preinstall的环境，下载了fabric-samples的代码和bin目录下的二进制程序后，你就会执行


./byfn.sh -m generate   # 生成Fabric区块链网络的部署配置文件
./byfn.sh -m up        # 运行区块链网络
然后就会产生如下一堆日志，注意了下面这堆日志很有学习价值，是很好的入门材料，所以我决定用红色字体对他们进行注释。

以下红色部分为我的注释


------------------------------------------华丽的分割线---------------------------------------------------
proceeding ...


/root/fabric-samples/bin/cryptogen




##########################################################
##### Generate certificates using cryptogen tool #########
##########################################################
+ cryptogen generate --config=./crypto-config.yaml




根据 crypto-config.yaml 里面的组织声明，给每个组织的用户 生成 用户证书其中包括MSP证书和TSL证书（peer节点涉及到gRPC通讯所以用到了TSL证书，而普通的客户端用户不需要TSL证书）。

 


org1.example.com


org2.example.com
+ set +x












/root/fabric-samples/bin/configtxgen
##########################################################
#########  Generating Orderer Genesis block ##############
##########################################################
+ configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block
根据 configtx.yaml 中配置的区块链核心配置 生成创世块安装包。






2018-03-05 09:33:35.300 UTC [common/tools/configtxgen] main -> INFO 001 Loading configuration


2018-03-05 09:33:35.307 UTC [msp] getMspConfig -> INFO 002 Loading NodeOUs
2018-03-05 09:33:35.308 UTC [msp] getMspConfig -> INFO 003 Loading NodeOUs
2018-03-05 09:33:35.308 UTC [common/tools/configtxgen] doOutputBlock -> INFO 004 Generating genesis block
2018-03-05 09:33:35.308 UTC [common/tools/configtxgen] doOutputBlock -> INFO 005 Writing genesis block
+ set +x




#################################################################
### Generating channel configuration transaction 'channel.tx' ###
#################################################################
+ configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID mychannel


根据 configtx.yaml 中配置的区块链核心配置 生成通道安装包。

2018-03-05 09:33:35.316 UTC [common/tools/configtxgen] main -> INFO 001 Loading configuration
2018-03-05 09:33:35.323 UTC [common/tools/configtxgen] doOutputChannelCreateTx -> INFO 002 Generating new channel configtx
2018-03-05 09:33:35.323 UTC [msp] getMspConfig -> INFO 003 Loading NodeOUs
2018-03-05 09:33:35.323 UTC [msp] getMspConfig -> INFO 004 Loading NodeOUs
2018-03-05 09:33:35.341 UTC [common/tools/configtxgen] doOutputChannelCreateTx -> INFO 005 Writing new channel tx
+ set +x




#################################################################
#######    Generating anchor peer update for Org1MSP   ##########
#################################################################
+ configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID mychannel -asOrg Org1MSP


根据 configtx.yaml 中配置的区块链核心配置 生成组织1的锚节点peer0的update安装包。


2018-03-05 09:33:35.350 UTC [common/tools/configtxgen] main -> INFO 001 Loading configuration
2018-03-05 09:33:35.356 UTC [common/tools/configtxgen] doOutputAnchorPeersUpdate -> INFO 002 Generating anchor peer update
2018-03-05 09:33:35.357 UTC [common/tools/configtxgen] doOutputAnchorPeersUpdate -> INFO 003 Writing anchor peer update
+ set +x




#################################################################
#######    Generating anchor peer update for Org2MSP   ##########
#################################################################
+ configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID mychannel -asOrg Org2MSP


根据 configtx.yaml 中配置的区块链核心配置 生成组织2的锚节点peer0的update安装包。


2018-03-05 09:33:35.365 UTC [common/tools/configtxgen] main -> INFO 001 Loading configuration
2018-03-05 09:33:35.371 UTC [common/tools/configtxgen] doOutputAnchorPeersUpdate -> INFO 002 Generating anchor peer update
2018-03-05 09:33:35.371 UTC [common/tools/configtxgen] doOutputAnchorPeersUpdate -> INFO 003 Writing anchor peer update
+ set +x




[root@vultr first-network]# ./byfn.sh -m up
Starting with channel 'mychannel' and CLI timeout of '10' seconds and CLI delay of '3' seconds
Continue? [Y/n] y
proceeding ...
2018-03-05 09:33:59.073 UTC [main] main -> INFO 001 Exiting.....
LOCAL_VERSION=1.1.0-rc1
DOCKER_IMAGE_VERSION=1.1.0-rc1
Creating network "net_byfn" with the 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_peer1.org1.example.com" with default driver
Creating volume "net_peer0.org1.example.com" with default driver
Creating peer1.org1.example.com ... done
Creating cli ... done
Creating orderer.example.com ...
Creating peer0.org2.example.com ...
Creating peer1.org1.example.com ...
Creating peer1.org2.example.com ...
Creating cli ...


docker-compose 运行整个区块链网络中各个节点的容器


 ____    _____      _      ____    _____
/ ___|  |_   _|    / \    |  _ \  |_   _|
\___ \    | |     / _ \   | |_) |   | |
 ___) |   | |    / ___ \  |  _ <    | |
|____/    |_|   /_/   \_\ |_| \_\   |_|




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




Channel name : mychannel
Creating channel...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
组织1 的锚节点 Peer0的TLS ca根证书


CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
组织1 的锚节点 Peer0的TLS 密钥证书


CORE_PEER_LOCALMSPID=Org1MSP
MSP的ID
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
组织1 的锚节点 Peer0的TLS 数字证书


CORE_PEER_TLS_ENABLED=true
开启TLS通讯

CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
管理员MSP身份证书


CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
指明CLI访问组织org1的peer0节点




2018-03-05 09:34:02.843 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-03-05 09:34:02.888 UTC [channelCmd] InitCmdFactory -> INFO 002 Endorser and orderer connections initialized
2018-03-05 09:34:03.093 UTC [main] main -> INFO 003 Exiting.....
通道创建完成
===================== Channel "mychannel" is created successfully =====================




Having all peers join the channel...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
+ peer channel join -b mychannel.block
命令组织1的peer0节点加入通道


+ set +x
2018-03-05 09:34:03.144 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-03-05 09:34:03.180 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
2018-03-05 09:34:03.180 UTC [main] main -> INFO 003 Exiting.....
===================== peer0.org1 joined on the channel "mychannel" =====================




CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer1.org1.example.com:7051
+ peer channel join -b mychannel.block
命令组织1的peer1节点加入通道


+ set +x
2018-03-05 09:34:06.219 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-03-05 09:34:06.244 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
2018-03-05 09:34:06.244 UTC [main] main -> INFO 003 Exiting.....
===================== peer1.org1 joined on the channel "mychannel" =====================




CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org2MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org2.example.com:7051
+ peer channel join -b mychannel.block
命令组织2的peer0节点加入通道


+ set +x
2018-03-05 09:34:09.283 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-03-05 09:34:09.308 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
2018-03-05 09:34:09.308 UTC [main] main -> INFO 003 Exiting.....
===================== peer0.org2 joined on the channel "mychannel" =====================




CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org2MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer1.org2.example.com:7051
+ peer channel join -b mychannel.block
命令组织2的peer1节点加入通道


+ set +x
2018-03-05 09:34:12.346 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-03-05 09:34:12.372 UTC [channelCmd] executeJoin -> INFO 002 Successfully submitted proposal to join channel
2018-03-05 09:34:12.372 UTC [main] main -> INFO 003 Exiting.....
===================== peer1.org2 joined on the channel "mychannel" =====================




Updating anchor peers for org1...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
+ 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
命令组织1的peer0节点更新锚节点配置


+ set +x
2018-03-05 09:34:15.412 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-03-05 09:34:15.423 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update
2018-03-05 09:34:15.423 UTC [main] main -> INFO 003 Exiting.....
===================== Anchor peers for org "Org1MSP" on "mychannel" is updated successfully =====================




Updating anchor peers for org2...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org2MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org2.example.com:7051
+ 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
命令组织2的peer0节点更新锚节点配置
+ set +x
2018-03-05 09:34:18.465 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2018-03-05 09:34:18.476 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update
2018-03-05 09:34:18.476 UTC [main] main -> INFO 003 Exiting.....
===================== Anchor peers for org "Org2MSP" on "mychannel" is updated successfully =====================




Installing chaincode on peer0.org1...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
+ peer chaincode install -n mycc -v 1.0 -l golang -p github.com/chaincode/chaincode_example02/go/
安装链码mycc到组织1的锚节点peer0


+ set +x
2018-03-05 09:34:21.518 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-03-05 09:34:21.518 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2018-03-05 09:34:21.907 UTC [main] main -> INFO 003 Exiting.....
===================== Chaincode is installed on peer0.org1 =====================




Install chaincode on peer0.org2...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org2MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org2.example.com:7051
+ peer chaincode install -n mycc -v 1.0 -l golang -p github.com/chaincode/chaincode_example02/go/
安装链码mycc到组织2的锚节点peer0
+ set +x
2018-03-05 09:34:21.944 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-03-05 09:34:21.944 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2018-03-05 09:34:22.061 UTC [main] main -> INFO 003 Exiting.....
===================== Chaincode is installed on peer0.org2 =====================




Instantiating chaincode on peer0.org2...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org2MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org2.example.com:7051
+ peer chaincode instantiate -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 -l golang -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P 'OR   ('\''Org1MSP.peer'\'','\''Org2MSP.peer'\'')'
实例化并初始化链码mycc到组织2的锚节点peer0


+ set +x
2018-03-05 09:34:22.099 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-03-05 09:34:22.099 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2018-03-05 09:34:43.739 UTC [main] main -> INFO 003 Exiting.....
===================== Chaincode Instantiation on peer0.org2 on channel 'mychannel' is successful =====================




Querying chaincode on peer0.org1...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
===================== 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"]}'
在组织1的锚节点peer0调用链码mycc查询区块链中a的值
+ set +x




2018-03-05 09:34:46.792 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-03-05 09:34:46.792 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Query Result: 100
2018-03-05 09:35:05.562 UTC [main] main -> INFO 003 Exiting.....
===================== Query on peer0.org1 on channel 'mychannel' is successful =====================
Sending invoke transaction on peer0.org1...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org1MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer0.org1.example.com:7051
+ 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 -c '{"Args":["invoke","a","b","10"]}'
在组织1的锚节点peer0调用链码mycc修改区块链中a的值,把a的值转移10到b
+ set +x
2018-03-05 09:35:05.685 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-03-05 09:35:05.685 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2018-03-05 09:35:06.221 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 003 Chaincode invoke successful. result: status:200
2018-03-05 09:35:06.221 UTC [main] main -> INFO 004 Exiting.....
===================== Invoke transaction on peer0.org1 on channel 'mychannel' is successful =====================




Installing chaincode on peer1.org2...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org2MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer1.org2.example.com:7051
+ peer chaincode install -n mycc -v 1.0 -l golang -p github.com/chaincode/chaincode_example02/go/
在组织2的普通节点peer1安装链码mycc
+ set +x
2018-03-05 09:35:06.302 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-03-05 09:35:06.302 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2018-03-05 09:35:06.601 UTC [main] main -> INFO 003 Exiting.....
===================== Chaincode is installed on peer1.org2 =====================




Querying chaincode on peer1.org2...
CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
CORE_PEER_LOCALMSPID=Org2MSP
CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
CORE_PEER_TLS_ENABLED=true
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
CORE_PEER_ID=cli
CORE_LOGGING_LEVEL=INFO
CORE_PEER_ADDRESS=peer1.org2.example.com:7051
===================== Querying on peer1.org2 on channel 'mychannel'... =====================
Attempting to Query peer1.org2 ...3 secs
+ peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'
在组织2的普通节点peer1实例化链码mycc并调用链码查询a的值
+ set +x




2018-03-05 09:35:09.643 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-03-05 09:35:09.643 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Query Result: 90
2018-03-05 09:35:28.560 UTC [main] main -> INFO 003 Exiting.....
===================== Query on peer1.org2 on channel 'mychannel' is successful =====================




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








 _____   _   _   ____
| ____| | \ | | |  _ \
|  _|   |  \| | | | | |
| |___  | |\  | | |_| |
|_____| |_| \_| |____/
liangdu_Zuker
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
5. Fabric2.2 安装、提交合约（使用官方Demo）
菜鸟的博客
02-23 1597
带领大家，一步一步操作，完成Fabric2.2 智能合约的安装、提交等流程
Fabric2.0.0环境搭建及链码操作详解
yuch_hong的博客
07-24 1940
安装软件 更新源 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..
Fabric开发模式链码部署测试
攻城老湿的博客
12-06 547
完成 Fabric 的安装与初步尝试后，需要我们进一步的对 Fabric 的部署做了解。由于在生产环境下，无法对链码错误进行有效定位。故而本节首先完成 Fabric 开发环境的部署，可以由程序员手动执行链码，而非提交给 Fabric 去执行，从log日志中可以有效定位问题。另外，本节完成链码的整体操作流程。enjoy！ 1 基础 chaincode 编写 在 chaincode 文件夹中创建...
log fabrc -2019-06-03
boss2967的博客
06-03 347
root1@root1-virtual-machine:~/Fabric_file/images/fabric-samples/first-network$ ./byfn.sh up Starting for channel 'mychannel' with CLI timeout of '10' seconds and CLI delay of '3' seconds Continue? [Y...
(二)Fabric2.0 first-network 生成配置说明
01-07
(二)Fabric2.0 first-network 生成配置说明 (三)Fabric2.0启动网络脚本配置剖析 (四)Fabric2.0通道实践 (五)Fabric2.0 智能合约实践- 安装以及定义智能合约 (六)Fabric2.0 智能合约实践- 升级智能合约 (七)Fabric...
fabric first-network学习笔记
01-08
参考文档：https://hyperledger-fabric.readthedocs.io/en/release-1.4/build_network.html 网络拓扑 四个 Peer 节点分属于同一个管理域（example.com）下的两个组织Org1 和Org2，这两个组织都加入同一个应用通道...
五、区块链学习-Hyperledger Fabric (基于release-1.0) 官方示例FirstNetwork搭建
01-07
五、区块链学习-Hyperledger Fabric 基于release-1.0官方示例FirstNetwork搭建1、docker 镜像准备2、源码获取2.1 获取Hyperledger Fabric源码2.2 获取fabric-samples源码2.3 切换代码版本到release-1.03 、编译需要...
Hyperledger-Fabric-Demo:超级账本面料
05-10
超级账本面料 环境 Ubuntu16.10 准备 安装Docker（版本1.13.1） sudo apt install docker.io 安装docker-compose（版本1.19.0） ...修改权限 sudo chmod +x /usr/local/bin/docker-compose 安装golang（版本go1.8.3）...
(三)Fabric2.0启动网络脚本配置剖析
01-07
(二)Fabric2.0 first-network 生成配置说明 (三)Fabric2.0启动网络脚本配置剖析 (四)Fabric2.0通道实践 (五)Fabric2.0 智能合约实践- 安装以及定义智能合约 (六)Fabric2.0 智能合约实践- 升级智能合约 (七)Fabric...
fabricjs API 中译本
10-01
fabricjs是一款非常强大的Canvas绘图框架，很可惜的是我在网上找了一圈没找到中文翻译，SO为了自己能静下心通读一遍API，同时能造福英文不好的同学，我决定把这个框架的API文档译成中文。 这个文档是我完整翻译的第二个文档，虽然在阅读英文的API时能看得懂，但有些时候翻译成中文时会找不到合适的词，所以文档中有些地方我尽量做到表达清楚，但语句并是很流畅，请有缘人别太计较：） 最后附上fabricJS的官网，上面有些很不错DEMO：http://fabricjs.com/。还有一点需要说明，压缩包内同时附上四篇快速入门教程。这四篇教程是“无翻译英文原文”噢
network服务及其启动流程介绍
qq_36382062的博客
09-26 6233
概述 先说一下NetworkManager服务：从RHEL/CentOS 7开始，网络功能默认由NetworkManager以服务的形式提供。NetworkManager是一个能够动态控制和配置网络的守护进程，管理网络服务和网络连接，对应NetworkManager.service服务。 旧的 /etc/init.d/network 以及 ifup，ifdown 等静态控制脚本依然存在，但是处于备用状态，即：NetworkManager运行时，多数情况下这些脚本会调用NetworkManager去完成网络配
Hyperledger byfn.sh -m generate/up/down流程分析
baidu_25845567的博客
07-10 1576
BYFN——构建你的第一个网络，该方案提供了一个示例Hyperledger Fabric网络，该网络由两个组织组成，每个组织都维护两个对等节点，以及一个solo排序服务。该案例是fabric官方文档的第一个案例，也是市面上几乎所有Fabric教材和课程必讲的内容，其启动过程的重要性也就不言而喻了，可官方文档太长了，信息笔者初次看的时候就没看完，后来根据启动脚本分析了一遍后，再去看的时候就轻轻松松看...
Hyperledger Fabric构建第一个网络（官方教程）
chaishen10000的专栏
01-07 2749
前言 官方英文：Building Your First Network 中文：构建第一个fabric网络 感谢中文翻译！不然这么长的英文以及各种名词解释实在头疼。有一些和官方英文不一样的地方我已经按官方英文进行了补充和修正，并且尽量简化了语言，因为有些翻译过来有点拗口。如果希望看完整及原汁原味的文档，推荐看官方英文文档。 本文基于Mac OS以及Hyperledger Fabric 1.1...
零基础搭建区块链Hyperledger Fabric v1.0环境
强吉义的个人技术博客
02-08 470
　　2018新年伊始，一个被大家炒的比较热门的技术映入大众眼帘，没错就是“区块链”，这个去中心化技术的爆红得益于以比特币为代表的数字货币最近这几年的疯涨，也因此伴随着衍生出各种诸如“挖矿”、“矿工”、“矿机”...等新鲜词汇。作为一名搞技术的理工男，区块链适合研发什么样的项目，如何着手研发，它的技术特性及优势...才是我们最关心的。下面就来介绍下Hyperledger Fabric v1.0的...
3. 部署Fabric2.2 集群（使用官方Demo）
菜鸟的博客
02-22 3225
上节作者新购买阿里云，与大家一起操作，不遗漏每个操作步骤，保证大家都可以成功部署区块链集群。环境准备完毕，本节下载Fabric官方demo，并部署区块链集群。 1）安装git命令 yum install -y git 2）下载Fabric 2.2.1 版本代码 有点慢 或者出现中断情况，请反复操作，这是github网址 国内的支持不是很好。 git clone -b v2.2.1 https://github.com/hyperledger/fabric.git 3）下载依赖二进制、镜像 这个步骤也.
hyperLedger fabric 从0到1 + End2EndIT源码解析
weixin_34122548的博客
06-11 406
背景：本文主要是从0开始在阿里云ECS/mac上搭建fabric网络，然后在本地的MAC电脑intellij下载fabric-sdk-java，使用End2EndIT单元测试ECS/mac 部署的区块链；最后再完整实现一个业务CASE进行实战讲解；(鉴于本文过长，章节7单独开一个文章) fabric环境依赖安装 fabric安装 fabric官方例子...
Hyperledger Fabric命令详解之 up
weixin_34198762的博客
08-06 189
sudo ./byfn.sh up a@ubuntu:~/hyfa/fabric-samples/first-network$ sudo ./byfn.sh up > 创建网络，peer，orderer，cli Starting with channel 'mychannel' and CLI timeout of '10' ...
Linux 中日志以及网络的管理
热门推荐
x19979797的博客
10-19 1万+
1.系统日志 （1）系统日志默认分类 /var/log/messages   系统服务及日志，包括服务的信息，报错等等 /var/log/secure         系统认证信息日志 /var/log/maillog        系统邮件服务信息 /var/log/cron             系统定时任务信息 /var/log/boot.log      系统启动信息
fabric 中网络启动脚本 network.sh
最新发布
04-21
对于这个问题，我可以回答。network.sh 是一个Fabric网络启动脚本，它包含了一些用于启动Fabric网络的命令和配置文件。它可以让用户更方便地启动一个Fabric网络，同时也可以进行对网络的配置和测试。

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值