GB-132: the republisher metrics port is already held on the core¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-132 is printed by goatbuilder. The same text offline: goat explain GB-132 or goatbuilder explain GB-132.
What it means¶
the outbound republisher's loopback metrics port is held on the core host by something other than this peering's republisher. One port per peering on a shared core host.
Why it happens¶
- another peering's republisher uses the same metrics port on the core host
- another service listens on that loopback port
What to do¶
One line per step or alternative:
pin republisher_metrics_port in the peering declaration (goatbuilder.yaml peerings: values:)
or set goat_fed_republisher_metrics_port in group_vars/<peering>_core/
Read more¶
Exit code¶
goatbuilder exits with 1.