4. Hyperledger Fabric 네트워크 구축하기-멀티호스트 환경
페이지 정보
작성자 관리자 댓글 0건 조회 2,312회 작성일 19-08-23 22:25본문
4. Hyperledger Fabric 네트워크 구축하기-멀티호스트 환경
root@client:~# mkdir testnet
root@client:~# cp $FABRIC_HOME/sampleconfig/core.yaml /root/testnet/
root@client:~# cp $FABRIC_HOME/sampleconfig/orderer.yaml /root/testnet/
oot@client:~# vi /etc/hosts
192.168.0.105 peer0
192.168.0.108 peer1
192.168.0.103 orderer0
192.168.0.104 kafka-zookeeper
192.168.0.100 client
root@client:~# cd testnet/
root@client:~/testnet# ls
core.yaml orderer.yaml
root@client:~/testnet# vi crypto-config.yaml
OrdererOrgs:
- Name: OrdererOrg0
Domain: ordererorg0
Specs:
- Hostname: orderer0
PeerOrgs:
- Name: Org0
Domain: org0
Template:
Count: 1
Users:
Count: 1
root@client:~/testnet# cryptogen generate --config=./crypto-config.yaml
org0
root@client:~/testnet# tree crypto-config
crypto-config
├── ordererOrganizations
│ └── ordererorg0
│ ├── ca
│ │ ├── b19c22c6776017d7643bed281911a15da958a07dd23144fd0a74905df9c05a0b_sk
│ │ └── ca.ordererorg0-cert.pem
│ ├── msp
│ │ ├── admincerts
│ │ │ └── Admin@ordererorg0-cert.pem
│ │ ├── cacerts
│ │ │ └── ca.ordererorg0-cert.pem
│ │ └── tlscacerts
│ │ └── tlsca.ordererorg0-cert.pem
│ ├── orderers
│ │ └── orderer0.ordererorg0
│ │ ├── msp
│ │ │ ├── admincerts
│ │ │ │ └── Admin@ordererorg0-cert.pem
│ │ │ ├── cacerts
│ │ │ │ └── ca.ordererorg0-cert.pem
│ │ │ ├── keystore
│ │ │ │ └── d08cad30fbb53a815f14ed26ffe553d0f9ef511476b73758109df17943c4e1b4_sk
│ │ │ ├── signcerts
│ │ │ │ └── orderer0.ordererorg0-cert.pem
│ │ │ └── tlscacerts
│ │ │ └── tlsca.ordererorg0-cert.pem
│ │ └── tls
│ │ ├── ca.crt
│ │ ├── server.crt
│ │ └── server.key
│ ├── tlsca
│ │ ├── 3ee067e7c02e1bbccd324531262be17a2b39a07a9f86fadfd1612b27a91a8a0a_sk
│ │ └── tlsca.ordererorg0-cert.pem
│ └── users
│ └── Admin@ordererorg0
│ ├── msp
│ │ ├── admincerts
│ │ │ └── Admin@ordererorg0-cert.pem
│ │ ├── cacerts
│ │ │ └── ca.ordererorg0-cert.pem
│ │ ├── keystore
│ │ │ └── 216673e76d55fa01311f6d7ebcc808ec26211c534b000945afb9775c5b6a1959_sk
│ │ ├── signcerts
│ │ │ └── Admin@ordererorg0-cert.pem
│ │ └── tlscacerts
│ │ └── tlsca.ordererorg0-cert.pem
│ └── tls
│ ├── ca.crt
│ ├── client.crt
│ └── client.key
└── peerOrganizations
└── org0
├── ca
│ ├── 7a9da8af6e5ff112b7121b542b8b82443bf9694d4dca917975826382898eabcf_sk
│ └── ca.org0-cert.pem
├── msp
│ ├── admincerts
│ │ └── Admin@org0-cert.pem
│ ├── cacerts
│ │ └── ca.org0-cert.pem
│ └── tlscacerts
│ └── tlsca.org0-cert.pem
├── peers
│ └── peer0.org0
│ ├── msp
│ │ ├── admincerts
│ │ │ └── Admin@org0-cert.pem
│ │ ├── cacerts
│ │ │ └── ca.org0-cert.pem
│ │ ├── keystore
│ │ │ └── 624d3f74cc149271e883e6957c76cde799112252f4949242376e6deaa6e9308e_sk
│ │ ├── signcerts
│ │ │ └── peer0.org0-cert.pem
│ │ └── tlscacerts
│ │ └── tlsca.org0-cert.pem
│ └── tls
│ ├── ca.crt
│ ├── server.crt
│ └── server.key
├── tlsca
│ ├── d8fde820418823cbf071198e5ad8d9298bfc94be0afac70cc36b91ee3936778f_sk
│ └── tlsca.org0-cert.pem
└── users
├── Admin@org0
│ ├── msp
│ │ ├── admincerts
│ │ │ └── Admin@org0-cert.pem
│ │ ├── cacerts
│ │ │ └── ca.org0-cert.pem
│ │ ├── keystore
│ │ │ └── f80e5739ebdc435e1f39ba7e067a25b74fa75578bab8147f38279cbb53f27a5a_sk
│ │ ├── signcerts
│ │ │ └── Admin@org0-cert.pem
│ │ └── tlscacerts
│ │ └── tlsca.org0-cert.pem
│ └── tls
│ ├── ca.crt
│ ├── client.crt
│ └── client.key
└── User1@org0
├── msp
│ ├── admincerts
│ │ └── User1@org0-cert.pem
│ ├── cacerts
│ │ └── ca.org0-cert.pem
│ ├── keystore
│ │ └── cd8c95ed78ab244df803b506563082601f2ba9531897f30e4e047f42f3910556_sk
│ ├── signcerts
│ │ └── User1@org0-cert.pem
│ └── tlscacerts
│ └── tlsca.org0-cert.pem
└── tls
├── ca.crt
├── client.crt
└── client.key
60 directories, 54 files
root@client:~/testnet#
root@client:~/testnet# vi configtx.yaml
Organizations:
- &OrdererOrg0
Name: OrdererOrg0
ID: OrdererOrg0MSP
MSPDir: crypto-config/ordererOrganizations/ordererorg0/msp/
- &Org0
Name: Org0MSP
ID: Org0MSP
MSPDir: crypto-config/peerOrganizations/org0/msp/
AnchorPeers:
- Host: peer0
Port: 7051
Orderer: &OrdererDefaults
OrdererType: kafka
Addresses:
- orderer0:7050
BatchTimeout: 1s
BatchSize:
MaxMessageCount: 30
AbsoluteMaxBytes: 99 MB
PreferredMaxBytes: 512 KB
Kafka:
Brokers:
- kafka-zookeeper:9092
Organizations:
Application: &ApplicationDefaults
Organizations:
Profiles:
TwoOrgsOrdererGenesis:
Orderer:
<<: *OrdererDefaults
Organizations:
- *OrdererOrg0
Consortiums:
SampleConsortium:
Organizations:
- *Org0
TwoOrgsChannel:
Consortium: SampleConsortium
Application:
<<: *ApplicationDefaults
Organizations:
- *Org0
root@client:~/testnet# configtxgen -profile TwoOrgsOrdererGenesis -outputBlock genesis.block
2019-08-27 21:56:35.993 KST [common.tools.configtxgen] main -> WARN 001 Omitting the channel ID for configtxgen for output operations is deprecated. Explicitly passing the channel ID will be required in the future, defaulting to 'testchainid'.
2019-08-27 21:56:36.003 KST [common.tools.configtxgen] main -> INFO 002 Loading configuration
2019-08-27 21:56:36.059 KST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 orderer type: kafka
2019-08-27 21:56:36.060 KST [common.tools.configtxgen.localconfig] Load -> INFO 004 Loaded configuration: /root/testnet/configtx.yaml
2019-08-27 21:56:36.081 KST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 005 orderer type: kafka
2019-08-27 21:56:36.082 KST [common.tools.configtxgen.localconfig] LoadTopLevel -> INFO 006 Loaded configuration: /root/testnet/configtx.yaml
2019-08-27 21:56:36.083 KST [common.tools.configtxgen.encoder] NewChannelGroup -> WARN 007 Default policy emission is deprecated, please include policy specifications for the channel group in configtx.yaml
2019-08-27 21:56:36.084 KST [common.tools.configtxgen.encoder] NewOrdererGroup -> WARN 008 Default policy emission is deprecated, please include policy specifications for the orderer group in configtx.yaml
2019-08-27 21:56:36.086 KST [common.tools.configtxgen.encoder] NewOrdererOrgGroup -> WARN 009 Default policy emission is deprecated, please include policy specifications for the orderer org group OrdererOrg0 in configtx.yaml
2019-08-27 21:56:36.088 KST [common.tools.configtxgen.encoder] NewConsortiumOrgGroup -> WARN 00a Default policy emission is deprecated, please include policy specifications for the orderer org group Org0MSP in configtx.yaml
2019-08-27 21:56:36.088 KST [common.tools.configtxgen] doOutputBlock -> INFO 00b Generating genesis block
2019-08-27 21:56:36.096 KST [common.tools.configtxgen] doOutputBlock -> INFO 00c Writing genesis block
root@client:~/testnet# ls
configtx.yaml crypto-config genesis.block
core.yaml crypto-config.yaml orderer.yaml
root@client:~/testnet# mv genesis.block /root/testnet/crypto-config/ordererOrganizations/ordererorg0/orderers/orderer0.ordererorg0/
root@client:~/testnet# tree crypto-config
crypto-config
├── ordererOrganizations
│ └── ordererorg0
│ ├── ca
│ │ ├── 583be9d11a0155126bd3c982fd407a053b418f0dc550c143529bc68dee49c061_sk
│ │ └── ca.ordererorg0-cert.pem
│ ├── msp
│ │ ├── admincerts
│ │ │ └── Admin@ordererorg0-cert.pem
│ │ ├── cacerts
│ │ │ └── ca.ordererorg0-cert.pem
│ │ └── tlscacerts
│ │ └── tlsca.ordererorg0-cert.pem
│ ├── orderers
│ │ └── orderer0.ordererorg0
│ │ ├── genesis.block
│ │ ├── msp
│ │ │ ├── admincerts
│ │ │ │ └── Admin@ordererorg0-cert.pem
│ │ │ ├── cacerts
│ │ │ │ └── ca.ordererorg0-cert.pem
│ │ │ ├── keystore
│ │ │ │ └── ab83701f4e47e828bbad88a5349d16ff72822bc12d24efd0c72d4110e787d151_sk
│ │ │ ├── signcerts
│ │ │ │ └── orderer0.ordererorg0-cert.pem
│ │ │ └── tlscacerts
│ │ │ └── tlsca.ordererorg0-cert.pem
│ │ └── tls
│ │ ├── ca.crt
│ │ ├── server.crt
│ │ └── server.key
│ ├── tlsca
│ │ ├── a5a7f04257b97456f42301d01268cc8ee0aea44d9231da29ddd55d9bda0b12ba_sk
│ │ └── tlsca.ordererorg0-cert.pem
│ └── users
│ └── Admin@ordererorg0
│ ├── msp
│ │ ├── admincerts
│ │ │ └── Admin@ordererorg0-cert.pem
│ │ ├── cacerts
│ │ │ └── ca.ordererorg0-cert.pem
│ │ ├── keystore
│ │ │ └── 3cb3b722658ff5c0a09e5d5c63886f6de231e82fbc310d3695af6885209e95e9_sk
│ │ ├── signcerts
│ │ │ └── Admin@ordererorg0-cert.pem
│ │ └── tlscacerts
│ │ └── tlsca.ordererorg0-cert.pem
│ └── tls
│ ├── ca.crt
│ ├── client.crt
│ └── client.key
└── peerOrganizations
└── org0
├── ca
│ ├── ae589d4cbb27151c5c166c1e11532a7a42d71c6906769dcd851850751c3b43c7_sk
│ └── ca.org0-cert.pem
├── msp
│ ├── admincerts
│ │ └── Admin@org0-cert.pem
│ ├── cacerts
│ │ └── ca.org0-cert.pem
│ └── tlscacerts
│ └── tlsca.org0-cert.pem
├── peers
│ ├── peer0.org0
│ │ ├── msp
│ │ │ ├── admincerts
│ │ │ │ └── Admin@org0-cert.pem
│ │ │ ├── cacerts
│ │ │ │ └── ca.org0-cert.pem
│ │ │ ├── keystore
│ │ │ │ └── be73e9b08ecfc3cb8297c681378f8c92731b5dd9f876ed941c294b79f90be657_sk
│ │ │ ├── signcerts
│ │ │ │ └── peer0.org0-cert.pem
│ │ │ └── tlscacerts
│ │ │ └── tlsca.org0-cert.pem
│ │ └── tls
│ │ ├── ca.crt
│ │ ├── server.crt
│ │ └── server.key
│ └── peer1.org0
│ ├── msp
│ │ ├── admincerts
│ │ │ └── Admin@org0-cert.pem
│ │ ├── cacerts
│ │ │ └── ca.org0-cert.pem
│ │ ├── keystore
│ │ │ └── 2cb436b638cd14bd023d53ae0c160509fdec9ad70a14940563ff56ba0aedddc9_sk
│ │ ├── signcerts
│ │ │ └── peer1.org0-cert.pem
│ │ └── tlscacerts
│ │ └── tlsca.org0-cert.pem
│ └── tls
│ ├── ca.crt
│ ├── server.crt
│ └── server.key
├── tlsca
│ ├── d947df64c1e645f2b28f97b5cc36a8033e7172be26298d9bf2e0c65b36f20ba2_sk
│ └── tlsca.org0-cert.pem
└── users
├── Admin@org0
│ ├── msp
│ │ ├── admincerts
│ │ │ └── Admin@org0-cert.pem
│ │ ├── cacerts
│ │ │ └── ca.org0-cert.pem
│ │ ├── keystore
│ │ │ └── 17bd3a8895122878b1328942d2074ca51ebe6f011a5be659747c8759da49e89c_sk
│ │ ├── signcerts
│ │ │ └── Admin@org0-cert.pem
│ │ └── tlscacerts
│ │ └── tlsca.org0-cert.pem
│ └── tls
│ ├── ca.crt
│ ├── client.crt
│ └── client.key
└── User1@org0
├── msp
│ ├── admincerts
│ │ └── User1@org0-cert.pem
│ ├── cacerts
│ │ └── ca.org0-cert.pem
│ ├── keystore
│ │ └── 9e1acda339a9e4e6b22d884632348644b5b6bc0f9916df85f174165b7f74c1d6_sk
│ ├── signcerts
│ │ └── User1@org0-cert.pem
│ └── tlscacerts
│ └── tlsca.org0-cert.pem
└── tls
├── ca.crt
├── client.crt
└── client.key
68 directories, 63 files
root@client:~/testnet#
root@client:~/testnet# configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ch1.tx -channelID ch1
2019-08-27 22:13:52.145 KST [common.tools.configtxgen] main -> INFO 001 Loading configuration
2019-08-27 22:13:52.154 KST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/testnet/configtx.yaml
2019-08-27 22:13:52.161 KST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 orderer type: kafka
2019-08-27 22:13:52.162 KST [common.tools.configtxgen.localconfig] LoadTopLevel -> INFO 004 Loaded configuration: /root/testnet/configtx.yaml
2019-08-27 22:13:52.162 KST [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 005 Generating new channel configtx
2019-08-27 22:13:52.163 KST [common.tools.configtxgen.encoder] NewChannelGroup -> WARN 006 Default policy emission is deprecated, please include policy specifications for the channel group in configtx.yaml
2019-08-27 22:13:52.163 KST [common.tools.configtxgen.encoder] NewApplicationGroup -> WARN 007 Default policy emission is deprecated, please include policy specifications for the application group in configtx.yaml
2019-08-27 22:13:52.164 KST [common.tools.configtxgen.encoder] NewApplicationOrgGroup -> WARN 008 Default policy emission is deprecated, please include policy specifications for the application org group Org0MSP in configtx.yaml
2019-08-27 22:13:52.165 KST [common.tools.configtxgen.encoder] NewChannelGroup -> WARN 009 Default policy emission is deprecated, please include policy specifications for the channel group in configtx.yaml
2019-08-27 22:13:52.165 KST [common.tools.configtxgen.encoder] NewApplicationGroup -> WARN 00a Default policy emission is deprecated, please include policy specifications for the application group in configtx.yaml
2019-08-27 22:13:52.166 KST [common.tools.configtxgen.encoder] NewApplicationOrgGroup -> WARN 00b Default policy emission is deprecated, please include policy specifications for the application org group Org0MSP in configtx.yaml
2019-08-27 22:13:52.166 KST [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 00c Writing new channel tx
root@client:~/testnet# ls
ch1.tx core.yaml crypto-config.yaml
configtx.yaml crypto-config orderer.yaml
root@client:~/testnet#
root@client:~/testnet# configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate Org0MSPanchors.tx -channelID ch1 -asOrg Org0MSP
2019-08-27 22:15:30.181 KST [common.tools.configtxgen] main -> INFO 001 Loading configuration
2019-08-27 22:15:30.187 KST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /root/testnet/configtx.yaml
2019-08-27 22:15:30.194 KST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 orderer type: kafka
2019-08-27 22:15:30.194 KST [common.tools.configtxgen.localconfig] LoadTopLevel -> INFO 004 Loaded configuration: /root/testnet/configtx.yaml
2019-08-27 22:15:30.195 KST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 005 Generating anchor peer update
2019-08-27 22:15:30.195 KST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 006 Writing anchor peer update
root@client:~/testnet# ls
Org0MSPanchors.tx configtx.yaml crypto-config orderer.yaml
ch1.tx core.yaml crypto-config.yaml
root@client:~/testnet#
root@client:~/testnet# cd ..
root@client:~# tar cvfz testnet.tar.gz testnet/
testnet/
testnet/crypto-config/
testnet/crypto-config/peerOrganizations/
root@client:~# scp -rq testnet.tar.gz leejinkwan@peer0:/home/leejinkwan
leejinkwan@peer0's password:
root@client:~#
root@client:~# scp -rq testnet.tar.gz leejinkwan@peer1:/home/leejinkwan
The authenticity of host 'peer1 (192.168.0.108)' can't be established.
ECDSA key fingerprint is SHA256:34qmUqZfUJpl9rRi4SCUcEIrRNldImnA446BQ7toQ4k.
Are you sure you want to continue connecting (yes/no)? yes
leejinkwan@peer1's password:
root@client:~# scp -rq testnet.tar.gz leejinkwan@orderer0:/home/leejinkwan
The authenticity of host 'orderer0 (192.168.0.104)' can't be established.
ECDSA key fingerprint is SHA256:34qmUqZfUJpl9rRi4SCUcEIrRNldImnA446BQ7toQ4k.
Are you sure you want to continue connecting (yes/no)? yes
leejinkwan@orderer0's password:
root@client:~#
root@peer0:~# mv /home/leejinkwan/testnet.tar.gz ./
root@peer0:~# tar xvfz testnet.tar.gz
root@peer0:~# cd testnet/
root@peer0:~/testnet# vi runPeer0.sh
CORE_PEER_ENDORSER_ENABLED=true \
CORE_PEER_PROFILE_ENABLED=true \
CORE_PEER_ADDRESS=peer0:7051 \
CORE_PEER_CHAINCODELISTENADDRESS=peer0:7052 \
CORE_PEER_ID=org0-peer0 \
CORE_PEER_LOCALMSPID=Org0MSP \
CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0:7051 \
CORE_PEER_GOSSIP_USELEADERELECTION=true \
CORE_PEER_GOSSIP_ORGLEADER=false \
CORE_PEER_TLS_ENABLED=false \
CORE_PEER_TLS_KEY_FILE=/root/testnet/crypto-config/peerOrganizations/org0/peers/peer0.org0/tls/server.key \
CORE_PEER_TLS_CERT_FILE=/root/testnet/crypto-config/peerOrganizations/org0/peers/peer0.org0/tls/server.crt \
CORE_PEER_TLS_ROOTCERT_FILE=/root/testnet/crypto-config/peerOrganizations/org0/peers/peer0.org0/tls/ca.crt \
CORE_PEER_TLS_SERVERHOSTOVERRIDE=peer0 \
CORE_VM_DOCKER_ATTACHSTDOUT=true \
CORE_PEER_MSPCONFIGPATH=/root/testnet/crypto-config/peerOrganizations/org0/peers/peer0.org0/msp \
peer node start
root@peer0:~/testnet# chmod 777 runPeer0.sh
root@peer0:~/testnet# ./runPeer0.sh
2019-08-27 22:24:41.481 KST [nodeCmd] serve -> INFO 001 Starting peer:
Version: 1.4.3
Commit SHA: 1e54df2ea
Go version: go1.10.4
OS/Arch: linux/amd64
Chaincode:
Base Image Version: 0.4.15
Base Docker Namespace: hyperledger
Base Docker Label: org.hyperledger.fabric
Docker Namespace: hyperledger
2019-08-27 22:24:41.494 KST [ledgermgmt] initialize -> INFO 002 Initializing ledger mgmt
2019-08-27 22:24:41.494 KST [kvledger] NewProvider -> INFO 003 Initializing ledger provider
2019-08-27 22:24:41.617 KST [kvledger] NewProvider -> INFO 004 ledger provider Initialized
2019-08-27 22:24:41.745 KST [ledgermgmt] initialize -> INFO 005 ledger mgmt initialized
2019-08-27 22:24:41.746 KST [peer] func1 -> INFO 006 Auto-detected peer address: 192.168.0.103:7051
2019-08-27 22:24:41.746 KST [peer] func1 -> INFO 007 Returning peer0:7051
2019-08-27 22:24:41.747 KST [peer] func1 -> INFO 008 Auto-detected peer address: 192.168.0.103:7051
2019-08-27 22:24:41.747 KST [peer] func1 -> INFO 009 Returning peer0:7051
2019-08-27 22:24:41.766 KST [nodeCmd] computeChaincodeEndpoint -> INFO 00a Entering computeChaincodeEndpoint with peerHostname: peer0
2019-08-27 22:24:41.767 KST [nodeCmd] computeChaincodeEndpoint -> INFO 00b Exit with ccEndpoint: peer0:7052
2019-08-27 22:24:41.771 KST [sccapi] registerSysCC -> INFO 00c system chaincode lscc(github.com/hyperledger/fabric/core/scc/lscc) registered
2019-08-27 22:24:41.773 KST [sccapi] registerSysCC -> INFO 00d system chaincode cscc(github.com/hyperledger/fabric/core/scc/cscc) registered
2019-08-27 22:24:41.774 KST [sccapi] registerSysCC -> INFO 00e system chaincode qscc(github.com/hyperledger/fabric/core/scc/qscc) registered
2019-08-27 22:24:41.775 KST [sccapi] registerSysCC -> INFO 00f system chaincode (+lifecycle,github.com/hyperledger/fabric/core/chaincode/lifecycle,true) disabled
2019-08-27 22:24:41.782 KST [gossip.service] func1 -> INFO 010 Initialize gossip with endpoint peer0:7051 and bootstrap set [127.0.0.1:7051]
2019-08-27 22:24:41.800 KST [gossip.gossip] NewGossipService -> INFO 011 Creating gossip service with self membership of Endpoint: peer0:7051, InternalEndpoint: peer0:7051, PKI-ID: 82779492ff005534628c5a3af1b13ce8fbf501bc04f77329ceb40317b4aafc4e, Metadata:
2019-08-27 22:24:41.804 KST [gossip.gossip] start -> INFO 012 Gossip instance peer0:7051 started
2019-08-27 22:24:41.819 KST [sccapi] deploySysCC -> INFO 013 system chaincode lscc/(github.com/hyperledger/fabric/core/scc/lscc) deployed
2019-08-27 22:24:41.819 KST [cscc] Init -> INFO 014 Init CSCC
2019-08-27 22:24:41.830 KST [sccapi] deploySysCC -> INFO 015 system chaincode cscc/(github.com/hyperledger/fabric/core/scc/cscc) deployed
2019-08-27 22:24:41.831 KST [qscc] Init -> INFO 016 Init QSCC
2019-08-27 22:24:41.831 KST [sccapi] deploySysCC -> INFO 017 system chaincode qscc/(github.com/hyperledger/fabric/core/scc/qscc) deployed
2019-08-27 22:24:41.832 KST [sccapi] deploySysCC -> INFO 018 system chaincode (+lifecycle,github.com/hyperledger/fabric/core/chaincode/lifecycle) disabled
2019-08-27 22:24:41.832 KST [nodeCmd] serve -> INFO 019 Deployed system chaincodes
2019-08-27 22:24:41.839 KST [discovery] NewService -> INFO 01a Created with config TLS: false, authCacheMaxSize: 1000, authCachePurgeRatio: 0.750000
2019-08-27 22:24:41.840 KST [nodeCmd] registerDiscoveryService -> INFO 01b Discovery service activated
2019-08-27 22:24:41.841 KST [nodeCmd] serve -> INFO 01c Starting peer with ID=[name:"org0-peer0" ], network ID=[dev], address=[peer0:7051]
2019-08-27 22:24:41.841 KST [nodeCmd] serve -> INFO 01d Started peer with ID=[name:"org0-peer0" ], network ID=[dev], address=[peer0:7051]
2019-08-27 22:24:41.842 KST [kvledger] LoadPreResetHeight -> INFO 01e Loading prereset height from path [/var/hyperledger/production/ledgersData/chains]
2019-08-27 22:24:41.842 KST [fsblkstorage] LoadPreResetHeight -> INFO 01f Loading Pre-reset heights
2019-08-27 22:24:41.843 KST [fsblkstorage] preRestHtFiles -> INFO 020 Dir [/var/hyperledger/production/ledgersData/chains/chains] missing... exiting
2019-08-27 22:24:41.843 KST [fsblkstorage] LoadPreResetHeight -> INFO 021 Pre-reset heights loaded
2019-08-27 22:24:41.843 KST [nodeCmd] func7 -> INFO 022 Starting profiling server with listenAddress = 0.0.0.0:6060
다른 터미널 창을 실행하고 hyperledger farbic 에서 생성되는 디렉토리 구조를 확인한다.
root@peer0:~# tree /var/hyperledger/
/var/hyperledger/
첨부파일
- script.zip (8.1K) 45회 다운로드 | DATE : 2019-10-31 15:10:43
댓글목록
등록된 댓글이 없습니다.