Blockchain Hyperledger结构通道创建,无法获取通道ID.block

Blockchain Hyperledger结构通道创建,无法获取通道ID.block,blockchain,hyperledger-fabric,Blockchain,Hyperledger Fabric,我一直在尝试创建我的第一个网络,并遵循官方文件。但我一直在尝试使用以下命令创建通道: peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizat

我一直在尝试创建我的第一个网络,并遵循官方文件。但我一直在尝试使用以下命令创建通道:

peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
虽然它没有给我任何错误,但我得到了以下响应:

2018-02-26 12:59:03.263 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2018-02-26 12:59:03.263 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-02-26 12:59:03.271 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
2018-02-26 12:59:03.273 UTC [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP
2018-02-26 12:59:03.274 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
2018-02-26 12:59:03.274 UTC [msp] GetLocalMSP -> DEBU 006 Returning existing local MSP
2018-02-26 12:59:03.274 UTC [msp] GetDefaultSigningIdentity -> DEBU 007 Obtaining default signing identity
2018-02-26 12:59:03.274 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A8C060A074F7267314D53501280062D...53616D706C65436F6E736F727469756D 
2018-02-26 12:59:03.274 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: 17C4AA38A89CFCCCEC5FF13E7F51BC4FF9C23F72E900454F30AE8ABB0A338DF8 
2018-02-26 12:59:03.274 UTC [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP
2018-02-26 12:59:03.274 UTC [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity
2018-02-26 12:59:03.275 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP
2018-02-26 12:59:03.275 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity
2018-02-26 12:59:03.275 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0AC3060A1508021A06089789D0D40522...B4DCD533B8C5DA311196A1277CDC1204 
2018-02-26 12:59:03.275 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: A1BC4CF64450BD26E28303C321E1E43658EF4C377E055121537863F4624BBB5E 
2018-02-26 12:59:03.385 UTC [msp] GetLocalMSP -> DEBU 010 Returning existing local MSP
2018-02-26 12:59:03.386 UTC [msp] GetDefaultSigningIdentity -> DEBU 011 Obtaining default signing identity
2018-02-26 12:59:03.386 UTC [msp] GetLocalMSP -> DEBU 012 Returning existing local MSP
2018-02-26 12:59:03.386 UTC [msp] GetDefaultSigningIdentity -> DEBU 013 Obtaining default signing identity
2018-02-26 12:59:03.386 UTC [msp/identity] Sign -> DEBU 014 Sign: plaintext: 0AC3060A1508021A06089789D0D40522...03C6A8CB79E812080A021A0012021A00 
2018-02-26 12:59:03.386 UTC [msp/identity] Sign -> DEBU 015 Sign: digest: 1803C7715AEA9E1C5DD8D1BEECF639C03233911A3AC437AF83114C91F52EB0D5 
2018-02-26 12:59:03.390 UTC [channelCmd] readBlock -> DEBU 016 Got status: &{NOT_FOUND}
2018-02-26 12:59:03.391 UTC [msp] GetLocalMSP -> DEBU 017 Returning existing local MSP
2018-02-26 12:59:03.391 UTC [msp] GetDefaultSigningIdentity -> DEBU 018 Obtaining default signing identity
2018-02-26 12:59:03.402 UTC [channelCmd] InitCmdFactory -> INFO 019 Endorser and orderer connections initialized
2018-02-26 12:59:03.604 UTC [msp] GetLocalMSP -> DEBU 01a Returning existing local MSP
2018-02-26 12:59:03.604 UTC [msp] GetDefaultSigningIdentity -> DEBU 01b Obtaining default signing identity
2018-02-26 12:59:03.604 UTC [msp] GetLocalMSP -> DEBU 01c Returning existing local MSP
2018-02-26 12:59:03.604 UTC [msp] GetDefaultSigningIdentity -> DEBU 01d Obtaining default signing identity
2018-02-26 12:59:03.604 UTC [msp/identity] Sign -> DEBU 01e Sign: plaintext: 0AC3060A1508021A06089789D0D40522...10B3951C861712080A021A0012021A00 
2018-02-26 12:59:03.604 UTC [msp/identity] Sign -> DEBU 01f Sign: digest: 1E71D72F8D5B50472EA46BC372866789252A02AEDC4D5299CD18FD6A0A08DF2F 
2018-02-26 12:59:03.608 UTC [channelCmd] readBlock -> DEBU 020 Received block: 0
2018-02-26 12:59:03.612 UTC [main] main -> INFO 021 Exiting.....
所以我的问题是我没有看到任何反应。任何帮助都将不胜感激。 谢谢

返回中提供的genesis块(本例中为文件mychannel.block)

peer channel join -b mychannel.block
这将加入peer-to-mychannel

返回中提供的genesis块(本例中为文件mychannel.block)

peer channel join -b mychannel.block

这将加入peer-to-mychannel。

您是否尝试加入peer-to-channel?您是否尝试加入peer-to-channel?感谢您的回复。我在运行-ls命令后找到了id。我假设块id将在命令响应中返回。但它实际上是在docker容器内。现在一切都按预期进行。无论如何,谢谢你的有益评论。谢谢你的回复。我在运行-ls命令后找到了id。我假设块id将在命令响应中返回。但它实际上是在docker容器内。现在一切都按预期进行。无论如何,谢谢你的有益评论。