Question

按照http://hyperledger-fabric.readthedocs.io/en/latest/getting_started.html处的文档尝试设置基本testnet 使用docker compose和示例docker-compose-no-tls.yaml文件。使用orderer获取以下错误：

orderer.example.com       | 2017-05-09 22:37:26.733 UTC [orderer/multichain] NewManagerImpl -> DEBU 102 Starting chain: 74657374636861696e6964
orderer.example.com       | 2017-05-09 22:37:26.733 UTC [orderer/ramledger] Iterator -> DEBU 103 Attempting to return block 0
orderer.example.com       | 2017-05-09 22:37:26.733 UTC [orderer/multichain] newChainSupport -> DEBU 104 Retrieved metadata for tip of chain (block #0): 
orderer.example.com       | 2017-05-09 22:37:26.733 UTC [orderer/multichain] NewManagerImpl -> CRIT 105 No system chain found
orderer.example.com       | panic: No system chain found
orderer.example.com       | 
orderer.example.com       | goroutine 1 [running]:
orderer.example.com       | panic(0xadb720, 0xc4203a8f30)
orderer.example.com       |   /opt/go/src/runtime/panic.go:500 +0x1a1
orderer.example.com       | github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panicf(0xc420185fb0, 0xbf561f, 0x15, 0x0, 0x0, 0x0)
orderer.example.com       |   /opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:194 +0x127
orderer.example.com       | github.com/hyperledger/fabric/orderer/multichain.NewManagerImpl(0x116bb60, 0xc42032c060, 0xc42028a660, 0x1169260, 0x11af8c0, 0x0, 0x0)
orderer.example.com       |   /opt/gopath/src/github.com/hyperledger/fabric/orderer/multichain/manager.go:125 +0x5c6
orderer.example.com       | main.main()
orderer.example.com       |   /opt/gopath/src/github.com/hyperledger/fabric/orderer/main.go:174 +0x1787

无法弄清楚导致它的原因。有人提示吗？

Answer 1

也许你使用了错误的configtxgen。

我遇到了同样的问题，它已经通过使用来自release.tar.gz的configtxgen重新生成orderer.block来解决。

configtxgen仍在开发中，不同版本的configtxgen生成的文件完全不同，并且不保证兼容。

Hyperledger fabric v1：启动orderer peer

1 个答案: