hyperledger/fabric · error

failed obtaining gossip config

Error message

failed obtaining gossip config

What it means

Building the gossip layer's global config (gossipgossip.GlobalConfig) from core.yaml peer.gossip settings failed, e.g., an invalid bootstrap address or badly formed endpoint value; the wrapped cause identifies the offending setting.

Source

Thrown at internal/peer/node/start.go:1253

	localMSP := mgmt.GetLocalMSP(factory.GetDefault())
	deserManager := peergossip.NewDeserializersManager(localMSP)
	messageCryptoService := peergossip.NewMCS(
		policyMgr,
		signer,
		deserManager,
		factory.GetDefault(),
		peerInstance.GetChannelConfig,
	)
	secAdv := peergossip.NewSecurityAdvisor(deserManager)
	bootstrap := viper.GetStringSlice("peer.gossip.bootstrap")

	serviceConfig := gossipservice.GlobalConfig()
	if serviceConfig.Endpoint != "" {
		peerAddress = serviceConfig.Endpoint
	}
	gossipConfig, err := gossipgossip.GlobalConfig(peerAddress, certs, bootstrap...)
	if err != nil {
		return nil, errors.Wrap(err, "failed obtaining gossip config")
	}

	return gossipservice.New(
		signer,
		gossipmetrics.NewGossipMetrics(metricsProvider),
		peerAddress,
		peerServer.Server(),
		messageCryptoService,
		secAdv,
		secureDialOpts(credSupport),
		credSupport,
		gossipConfig,
		serviceConfig,
		privdataConfig,
		deliverServiceConfig,
	)
}

View on GitHub (pinned to 2736b63f8f)

Solutions

1. Review peer.gossip.* settings in core.yaml, especially bootstrap and endpoint
2. Correct malformed host:port values
3. Restart the peer after fixing configuration

When it happens

Trigger: Thrown at internal/peer/node/start.go:1253 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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