Blockchain Hyperledger实例化链码

Blockchain Hyperledger实例化链码,blockchain,hyperledger,Blockchain,Hyperledger,尝试使用以下命令在hyperledger中实例化链码时: CORE_PEER_ADDRESS=peer0.org1.gnaledger.org:7051 peer chaincode instantiate -C gna-channel -n gnacc -v v0 -c '{"Args":[]}' -o orderer.gnaledger.org:7050 我发现以下错误: 2018-03-27 23:32:13.195 UTC [msp] GetLocalMSP -> DEBU 0

尝试使用以下命令在hyperledger中实例化链码时:

CORE_PEER_ADDRESS=peer0.org1.gnaledger.org:7051 peer chaincode instantiate -C gna-channel -n gnacc  -v v0 -c '{"Args":[]}' -o orderer.gnaledger.org:7050
我发现以下错误:

2018-03-27 23:32:13.195 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2018-03-27 23:32:13.195 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-03-27 23:32:13.203 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
2018-03-27 23:32:13.203 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
2018-03-27 23:32:13.203 UTC [grpc] Printf -> DEBU 005 transport: http2Client.notifyError got notified that the client transport was broken read tcp 172.18.0.7:33712->172.18.0.4:7050: read: connection reset by peer.
2018-03-27 23:32:13.209 UTC [msp/identity] Sign -> DEBU 006 Sign: plaintext: 0A9A070A6808031A0B08FDA8EBD50510...1A000A000A04657363630A0476736363
2018-03-27 23:32:13.209 UTC [msp/identity] Sign -> DEBU 007 Sign: digest: 7EF3FD93154CC3D3809AA89E945DC21ADCD9EBB9E80BF1D516162F137078FF81
Error: Error endorsing chaincode: rpc error: code = Unknown desc = Failed to deserialize creator identity, err MSP Org1MSP is unknown
2018-03-27 23:32:13.213 UTC [grpc] Printf -> DEBU 008 transport: http2Client.notifyError got notified that the client transport was broken unexpected EOF.
2018-03-27 23:32:13.213 UTC [grpc] Printf -> DEBU 009 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: failed to write window update: write tcp 172.18.0.7:33714->172.18.0.4:7050: write: broken pipe"; Reconnecting to {orderer.dcmledger.org:7050 <nil>}
2018-03-27 23:32:13.213 UTC [grpc] Printf -> DEBU 00a grpc: addrConn.transportMonitor exits due to: grpc: the connection is closing
Usage:
  peer chaincode instantiate [flags]
2018-03-27 23:32:13.195UTC[msp]GetLocalMSP->DEBU 001返回现有本地msp
2018-03-27 23:32:13.195 UTC[msp]GetDefaultSigningIdentity->DEBU 002获取默认签名身份
2018-03-27 23:32:13.203 UTC[chaincodeCmd]使用默认escc检查ChainCodecMDParams->INFO 003
2018-03-27 23:32:13.203 UTC[chaincodeCmd]使用默认vscc检查ChainCodecMDParams->INFO 004
2018-03-27 23:32:13.203 UTC[grpc]Printf->DEBU 005传输:http2Client.notifyError收到客户端传输中断的通知读取tcp 172.18.0.7:33712->172.18.0.4:7050:读取:对等方重置连接。
2018-03-27 23:32:13.209 UTC[msp/identity]标志->德布006标志:明文:0A9A0070A68031A0B08FDA8EBD50510…1A000A000A046573630A04767363
2018-03-27 23:32:13.209 UTC[msp/identity]标志->德布007标志:摘要:7EF3FD93154CC3D3809AA89E945DC21ADCD9EBB9E80BF1D516162F137078FF81
错误:签署链码时出错:rpc错误:代码=未知描述=无法反序列化创建者标识,错误MSP Org1MSP未知
2018-03-27 23:32:13.213 UTC[grpc]Printf->DEBU 008传输:http2Client.notifyError收到通知,客户端传输因意外EOF而中断。
2018-03-27 23:32:13.213 UTC[grpc]Printf->DEBU 009 grpc:addrConn.resetTransport无法创建客户端传输:连接错误:desc=“传输:无法写入窗口更新:写入tcp 172.18.0.7:33714->172.18.0.4:7050:写入:断开的管道”;正在重新连接到{order.dcmledger.org:7050}
2018-03-27 23:32:13.213 UTC[grpc]Printf->DEBU 00a grpc:addrConn.transportMonitor由于以下原因退出:grpc:连接正在关闭
用法:
对等链码实例化[标志]

首先是管道破裂,然后找不到MSP?

如果tls为真,则必须添加: --tls true--cafile./orderOrganizations/order.com/orders/order0.org1.com/msp/tlscacerts/tlsca.crfchina.com-cert.pem

关键错误为

Error: Error endorsing chaincode: rpc error: code = Unknown desc = Failed to deserialize creator identity, err MSP Org1MSP is unknown
我面临着类似的问题。我建议您在整个供应过程中仔细检查您使用的MSP的资本化情况,即
Org1MSP
vs
Org1MSP

更具体地说,我要看的一个细节是
configtx.yaml
-Org1
元素,
ID
键。通常是
org1MSP
org1MSP
。尝试一下,看看这是否有什么不同