Re: #fabric-ca #fabric-orderer #hyperledger-fabric Unable to start the Orderer, keep getting "initializing channelconfig failed: could not create channel Consortiums sub-group config:" #fabric-ca #fabric-orderer #hyperledger-fabric


Marek Malik <info@...>
 

Thanks Yacov, but I don’t intend to create the admincerts folder.

“define the admin OU in the config.yaml of the MSP folder”
This is exactly what I’m doing -> This is the config.yaml from the mail:

NodeOUs:
   Enable: true
   ClientOUIdentifier:
     Certificate: cacerts/hlf-ca--amvoxdlt-7054.pem
     OrganizationalUnitIdentifier: client
   PeerOUIdentifier:
     Certificate: cacerts/hlf-ca--amvoxdlt-7054.pem
     OrganizationalUnitIdentifier: peer
   AdminOUIdentifier:
     Certificate: cacerts/hlf-ca--amvoxdlt-7054.pem
     OrganizationalUnitIdentifier: admin
   OrdererOUIdentifier:
     Certificate: cacerts/hlf-ca--amvoxdlt-7054.pem
     OrganizationalUnitIdentifier: orderer



The cert is stored in the cacerts folder in the MSP dir.
Anything else that I’m missing ?

 

 

Best Regards,

Marek Malik

 

Od: Yacov Manevich <YACOVM@...>
Data: piątek, 8 stycznia 2021 22:58
Do: Marek Malik <info@...>
DW: "fabric@..." <fabric@...>
Temat: Re: [Hyperledger Fabric] #fabric-ca #fabric-orderer #hyperledger-fabric Unable to start the Orderer, keep getting "initializing channelconfig failed: could not create channel Consortiums sub-group config:"

 

Put admin certificates in the admin folder, or define the admin OU in the config.yaml of the MSP folder



From:        "Marek Malik" <info@...>
To:        fabric@...
Date:        01/08/2021 11:49 PM
Subject:        [EXTERNAL] [Hyperledger Fabric] #fabric-ca #fabric-orderer #hyperledger-fabric Unable to start the Orderer, keep getting "initializing channelconfig failed: could not create channel Consortiums sub-group config:"
Sent by:        fabric@...





Hello Guys, 

I'm trying to setup my network to work in Kubernetes cluster, but my Orderer keeps failing. I'm getting the following error: 
Main -> PANI 005 Failed validating bootstrap block: initializing channelconfig failed: could not create channel Consortiums sub-group config: setting up the MSP manager failed: administrators must be declared when no admin ou classification is set
panic: Failed validating bootstrap block: initializing channelconfig failed: could not create channel Consortiums sub-group config: setting up the MSP manager failed: administrators must be declared when no admin ou classification is set

Could anyone help?


I'm following a similar setup as the test-network from the samples: I have the Fabric-CA generating the certificates & using the NodeOUs (it is enabled in crypto-config.yaml): 

This is the configtx.yaml that I'm using to generate the genesis.block. It is also located in the msp folder when running the Orderer.

NodeOUs:
   Enable: true
   ClientOUIdentifier:
     Certificate: cacerts/hlf-ca--amvoxdlt-7054.pem
     OrganizationalUnitIdentifier: client
   PeerOUIdentifier:
     Certificate: cacerts/hlf-ca--amvoxdlt-7054.pem
     OrganizationalUnitIdentifier: peer
   AdminOUIdentifier:
     Certificate: cacerts/hlf-ca--amvoxdlt-7054.pem
     OrganizationalUnitIdentifier: admin
   OrdererOUIdentifier:
     Certificate: cacerts/hlf-ca--amvoxdlt-7054.pem
     OrganizationalUnitIdentifier: orderer

Orderer: &OrdererDefaults

 # Orderer Type: The orderer implementation to start
 OrdererType: etcdraft

 Addresses:
   - orderer0.amvox-dlt.io:7050

 # Batch Timeout: The amount of time to wait before creating a batch
 BatchTimeout: 3s

 # 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: 500

   # 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

 EtcdRaft:
   Consenters:
     - Host: orderer0.amvox-dlt.io
       Port: 7050
       ClientTLSCert: /hlf_config/crypto-config/ordererOrganizations/amvox-dlt.io/orderers/orderer0.amvox-dlt.io/tls/server.crt
       ServerTLSCert: /hlf_config/crypto-config/ordererOrganizations/amvox-dlt.io/orderers/orderer0.amvox-dlt.io/tls/server.crt


 # Organizations is the list of orgs which are defined as participants on
 # the orderer side of the network
 Organizations:

 # Policies defines the set of policies at this level of the config tree
 # For Orderer policies, their canonical path is
 #   /Channel/Orderer/<PolicyName>
 Policies:
   Readers:
     Type: ImplicitMeta
     Rule: "ANY Readers"
   Writers:
     Type: ImplicitMeta
     Rule: "ANY Writers"
   Admins:
     Type: ImplicitMeta
     Rule: "MAJORITY Admins"
   # BlockValidation specifies what signatures must be included in the block
   # from the orderer for the peer to validate it.
   BlockValidation:
     Type: ImplicitMeta
     Rule: "ANY Writers"

 # Capabilities describes the orderer level capabilities, see the
 # dedicated Capabilities section elsewhere in this file for a full
 # description
 Capabilities:
   <<: *OrdererCapabilities

################################################################################
#
#   CHANNEL
#
#   This section defines the values to encode into a config transaction or
#   genesis block for channel related parameters.
#
################################################################################
Channel: &ChannelDefaults
 # Policies defines the set of policies at this level of the config tree
 # For Channel policies, their canonical path is
 #   /Channel/<PolicyName>
 Policies:
   # Who may invoke the 'Deliver' API
   Readers:
     Type: ImplicitMeta
     Rule: "ANY Readers"
   # Who may invoke the 'Broadcast' API
   Writers:
     Type: ImplicitMeta
     Rule: "ANY Writers"
   # By default, who may modify elements at this config level
   Admins:
     Type: ImplicitMeta
     Rule: "MAJORITY Admins"

 # Capabilities describes the channel level capabilities, see the
 # dedicated Capabilities section elsewhere in this file for a full
 # description
 Capabilities:
   <<: *ChannelCapabilities

################################################################################
#
#   Profile
#
#   - Different configuration profiles may be encoded here to be specified
#   as parameters to the configtxgen tool
#
################################################################################
Profiles:

 amvox-channel:
   Consortium: AmvoxConsortium
   <<: *ChannelDefaults
   Application:
     <<: *ApplicationDefaults
     Organizations:
       - *Amvox
       - *Org2
       - *Org3
     Capabilities:
       <<: *ApplicationCapabilities

 OrdererGenesis:
   <<: *ChannelDefaults
   Orderer:
     <<: *OrdererDefaults
     OrdererType: etcdraft
     EtcdRaft:
       Consenters:
         - Host: orderer0.amvox-dlt.io
           Port: 7050
           ClientTLSCert: /hlf_config/crypto-config/ordererOrganizations/amvox-dlt.io/orderers/orderer0.amvox-dlt.io/tls/server.crt
           ServerTLSCert: /hlf_config/crypto-config/ordererOrganizations/amvox-dlt.io/orderers/orderer0.amvox-dlt.io/tls/server.crt
     Addresses:
       - orderer0.amvox-dlt.io:7050

     Organizations:
       - *AmvoxDLT
     Capabilities:
       <<: *OrdererCapabilities

   Application:
     <<: *ApplicationDefaults
     Organizations:
       - <<: *AmvoxDLT

   Consortiums:
     AmvoxConsortium:
       Organizations:
         - *Amvox
         - *Org2
         - *Org3

Anyone has any ideas why ordered can not get started?

 



Join fabric@lists.hyperledger.org to automatically receive all group messages.