我正在使用Hyperledger Fabric创建我的第一个网络。我正在尝试在Mac OSX 10.13.4和Fabric v1.1.0上建立一个包含3 Orgs的网络。
成功创建加密材料后，我继续使用Orderer Genesis块生成。但是我收到以下错误消息：
[common / tools / configtxgen / localconfig]加载 - ＆gt; CRIT 002读取配置时出错：解析配置时：yaml：第31行：找不到预期的密钥 2018-04-29 23：16：14.056 CEST [common / tools / configtxgen] func1 - ＆gt; CRIT 003读取配置时出错：解析配置时：yaml：第31行：找不到预期的密钥 恐慌：读取配置时出错：解析配置时：yaml：第31行：找不到预期的密钥[已恢复]恐慌：读取配置时出错：解析配置时：yaml：第31行：找不到预期的密钥
我的configtx.yaml文件是：
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
---
################################################################################
#
# Profile
#
# - Different configuration profiles may be encoded here to be specified
# as parameters to the configtxgen tool
#
################################################################################
Profiles:
MhmdOrdererGenesis:
Capabilities:
<<: *ChannelCapabilities
Orderer:
<<: *OrdererDefaults
Organizations:
- *OrdererOrg
Capabilities:
<<: *OrdererCapabilities
Consortiums:
MhmdConsortium:
Organizations:
- *Hos
- *Pha
- *Res
MhmdChannel:
Consortium: MhmdConsortium
Application:
<<: *ApplicationDefaults
Organizations:
- *Hos
- *Pha
- *Res
Capabilities:
<<: *ApplicationCapabilities
################################################################################
#
# Section: Organizations
#
# - This section defines the different organizational identities which will
# be referenced later in the configuration.
#
################################################################################
Organizations:
# SampleOrg defines an MSP using the sampleconfig. It should never be used
# in production but may be used as a template for other definitions
- &OrdererOrg
# DefaultOrg defines the organization which is used in the sampleconfig
# of the fabric.git development environment
Name: OrdererOrg
# ID to load the MSP definition as
ID: OrdererMSP
# MSPDir is the filesystem path which contains the MSP configuration
MSPDir: crypto-config/ordererOrganizations/mhmd.com/msp
- &Hos
# DefaultOrg defines the organization which is used in the sampleconfig
# of the fabric.git development environment
Name: HosMSP
# ID to load the MSP definition as
ID: HosMSP
MSPDir: crypto-config/peerOrganizations/hos.mhmd.com/msp
AnchorPeers:
# AnchorPeers defines the location of peers which can be used
# for cross org gossip communication. Note, this value is only
# encoded in the genesis block in the Application section context
- Host: peer0.hos.example.com
Port: 7051
- &Pha
# DefaultOrg defines the organization which is used in the sampleconfig
# of the fabric.git development environment
Name: PhaMSP
# ID to load the MSP definition as
ID: PhaMSP
MSPDir: crypto-config/peerOrganizations/pha.mhmd.com/msp
AnchorPeers:
# AnchorPeers defines the location of peers which can be used
# for cross org gossip communication. Note, this value is only
#encoded in the genesis block in the Application section context
- Host: peer0.pha.example.com
Port: 7051
- &Res
# DefaultOrg defines the organization which is used in the sampleconfig
# of the fabric.git development environment
Name: ResMSP
# ID to load the MSP definition as
ID: ResMSP
MSPDir: crypto-config/peerOrganizations/res.mhmd.com/msp
AnchorPeers:
# AnchorPeers defines the location of peers which can be used
# for cross org gossip communication. Note, this value is only
# encoded in the genesis block in the Application section context
- Host: peer0.res.example.com
Port: 7051
################################################################################
#
# SECTION: Orderer
#
# - This section defines the values to encode into a config transaction or
# genesis block for orderer related parameters
#
################################################################################
Orderer: &OrdererDefaults
# Orderer Type: The orderer implementation to start
# Available types are "solo" and "kafka"
OrdererType: solo
Addresses:
- orderer.mhmd.com:7050
# Batch Timeout: The amount of time to wait before creating a batch
BatchTimeout: 2s
# Batch Size: Controls the number of messages batched into a block
BatchSize:
# Max Message Count: The maximum number of messages to permit in a batch
MaxMessageCount: 10
# Absolute Max Bytes: The absolute maximum number of bytes allowed for
# the serialized messages in a batch.
AbsoluteMaxBytes: 99 MB
# Preferred Max Bytes: The preferred maximum number of bytes allowed for
# the serialized messages in a batch. A message larger than the preferred
# max bytes will result in a batch larger than preferred max bytes.
PreferredMaxBytes: 512 KB
Kafka:
# Brokers: A list of Kafka brokers to which the orderer connects
# NOTE: Use IP:port notation
Brokers:
- 127.0.0.1:9092
# Organizations is the list of orgs which are defined as participants on
# the orderer side of the network
Organizations:
################################################################################
#
# SECTION: Application
#
# - This section defines the values to encode into a config transaction or
# genesis block for application related parameters
#
################################################################################
Application: &ApplicationDefaults
# Organizations is the list of orgs which are defined as participants on
# the application side of the network
Organizations:
################################################################################
#
# SECTION: Capabilities
#
# - This section defines the capabilities of fabric network. This is a new
# concept as of v1.1.0 and should not be utilized in mixed networks with
# v1.0.x peers and orderers. Capabilities define features which must be
# present in a fabric binary for that binary to safely participate in the
# fabric network. For instance, if a new MSP type is added, newer binaries
# might recognize and validate the signatures from this type, while older
# binaries without this support would be unable to validate those
# transactions. This could lead to different versions of the fabric binaries
# having different world states. Instead, defining a capability for a channel
# informs those binaries without this capability that they must cease
# processing transactions until they have been upgraded. For v1.0.x if any
# capabilities are defined (including a map with all capabilities turned off)
# then the v1.0.x peer will deliberately crash.
#
################################################################################
Capabilities:
# Channel capabilities apply to both the orderers and the peers and must be
# supported by both. Set the value of the capability to true to require it.
Global: &ChannelCapabilities
# V1.1 for Global is a catchall flag for behavior which has been
# determined to be desired for all orderers and peers running v1.0.x,
# but the modification of which would cause incompatibilities. Users
# should leave this flag set to true.
V1_1: true
# Orderer capabilities apply only to the orderers, and may be safely
# manipulated without concern for upgrading peers. Set the value of the
# capability to true to require it.
Orderer: &OrdererCapabilities
# V1.1 for Order is a catchall flag for behavior which has been
# determined to be desired for all orderers running v1.0.x, but the
# modification of which would cause incompatibilities. Users should
# leave this flag set to true.
V1_1: true
# Application capabilities apply only to the peer network, and may be safely
# manipulated without concern for upgrading orderers. Set the value of the
# capability to true to require it.
Application: &ApplicationCapabilities
# V1.1 for Application is a catchall flag for behavior which has been
# determined to be desired for all peers running v1.0.x, but the
# modification of which would cause incompatibilities. Users should
# leave this flag set to true.
V1_1: true
我该如何解决？。
提前致谢。
答案 0 :(得分：1)
尝试删除第31行（MhmdChannel :)上的一个空格，使其保持与MhmdOrdererGenesis相同的级别，看看它是否有效。缩进在这里很重要。
答案 1 :(得分：0)
第17行，（MhmdOrdererGenesis），看起来它没有缩进得足够远。我会添加另一个空格，应该是4，看看是否有效。 YAML文件在查找键/对值时是缩进敏感的。