hyperledger/fabric · error

failed parsing MSPConfig

Error message

failed parsing MSPConfig

What it means

This error means the service discovery support could not proto-unmarshal the MSPConfig protobuf stored under the 'MSP' key of an orderer organization's config group while building the MSP-ID-to-endpoints map. It is thrown because a corrupt, empty, or non-protobuf value in the orderer group's MSP config makes it impossible to extract organization info needed for orderer endpoint discovery. The underlying protobuf error is wrapped with 'failed parsing MSPConfig'.

Source

Thrown at discovery/support/config/support.go:148

				continue
			}
			res[mspID].Endpoint = append(res[mspID].Endpoint, &discovery.Endpoint{
				Host: host,
				Port: uint32(port),
			})
		}
	}

	return res
}

func perOrgEndpointsByMSPID(ordererGrp map[string]*common.ConfigGroup) (map[string][]string, error) {
	res := make(map[string][]string)

	for name, group := range ordererGrp {
		mspConfig := &msp.MSPConfig{}
		if err := proto.Unmarshal(group.Values[channelconfig.MSPKey].Value, mspConfig); err != nil {
			return nil, errors.Wrap(err, "failed parsing MSPConfig")
		}
		// Skip non fabric MSPs, as they don't carry useful information for service discovery.
		// An idemix MSP shouldn't appear inside an orderer group, but this isn't a fatal error
		// for the discovery service and we can just ignore it.
		if mspConfig.Type != int32(mspconstants.FABRIC) {
			logger.Error("Orderer group", name, "is not a FABRIC MSP, but is of type", mspConfig.Type)
			continue
		}

		fabricConfig := &msp.FabricMSPConfig{}
		if err := proto.Unmarshal(mspConfig.Config, fabricConfig); err != nil {
			return nil, errors.Wrap(err, "failed marshaling FabricMSPConfig")
		}

		// Initialize an empty MSP to address mapping.
		res[fabricConfig.Name] = nil

		// If the key has a corresponding value, it should unmarshal successfully.

View on GitHub (pinned to 2736b63f8f)

Solutions

1. Validate the channel configuration block/protobuf bytes are intact (regenerate the genesis block or re-fetch the latest config block from orderers).
2. Ensure each orderer org group has a valid MSP value under channelconfig.MSPKey generated with configtxgen/configtxlator, not hand-written bytes.
3. Decode the config with configtxlator to confirm the MSPConfig is parseable before feeding it to discovery.
4. Check proto/schema version consistency between the component building the config and the discovery service.

Example fix

// before (test/config fixture missing MSP value)
grp := &common.ConfigGroup{Values: map[string]*common.ConfigValue{}}
// after
mspCfg, _ := proto.Marshal(&msp.MSPConfig{Type: int32(mspconstants.FABRIC), Config: fabricCfgBytes})
grp := &common.ConfigGroup{Values: map[string]*common.ConfigValue{
  channelconfig.MSPKey: {Value: mspCfg},
}}

mspCfg := &msp.MSPConfig{}
if group == nil || group.Values[channelconfig.MSPKey] == nil || len(group.Values[channelconfig.MSPKey].Value) == 0 {
    return fmt.Errorf("org group %q has no MSP value", name)
}
if err := proto.Unmarshal(group.Values[channelconfig.MSPKey].Value, mspCfg); err != nil {
    return fmt.Errorf("org group %q has invalid MSPConfig: %w", name, err)
}

func hasValidMSPValue(g *common.ConfigGroup) bool {
    v := g.Values[channelconfig.MSPKey]
    if v == nil || len(v.Value) == 0 {
        return false
    }
    return proto.Unmarshal(v.Value, &msp.MSPConfig{}) == nil
}

if err != nil {
    var umErr *proto.UnmarshalError
    if errors.As(err, &umErr) {
        // skip or quarantine this org group instead of failing discovery
    }
    return nil, err
}

When it happens

Trigger: perOrgEndpointsByMSPID iterates the channel config's orderer groups (via computeOrdererEndpoints) and calls proto.Unmarshal(group.Values[channelconfig.MSPKey].Value, &msp.MSPConfig{}); the error occurs when that value is empty/nil bytes, truncated, or not a valid serialized msp.MSPConfig protobuf.

Common situations: Hand-edited or tool-mangled genesis/channel config tx; config group fetched from a channel where the MSP value was corrupted in transit or storage; using a config block produced by a different/older proto schema version; passing a fabricated common.ConfigGroup in tests without populating Values[channelconfig.MSPKey].

Understand the failure class

Background: "cannot parse invalid wire-format data", "cannot unmarshal", "failed unmarshalling": protobuf unmarshal errors explained — this error's family across 10 libraries.

Related errors

• failed unmarshalling orderer addresses
• failed marshaling FabricMSPConfig
• key Config.ChannelGroup.Groups[%s].Groups is nil
• field Config.ChannelGroup.Values is nil
• failed unmarshalling fabric msp config

AI-assisted analysis of hyperledger/fabric@2736b63f8f (2026-09-04). Data as JSON: /api/errors/24602597f6165a02. Report an issue: GitHub.