GB-180: another run of this peering is in progress¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-180 is printed by goatbuilder. The same text offline: goat explain GB-180 or goatbuilder explain GB-180.
What it means¶
A real run of goatbuilder federate holds <work>/.lock from start to end, so two runs of one peering never interleave phases or overwrite each other's run journal. This run found the lock held and changed nothing.
Why it happens¶
- another terminal or a scheduled job is running
goatbuilder federatefor the same peering - two peerings were given the same working folder (--work or FED_WORK)
What to do¶
One line per step or alternative:
wait for the other run to finish; the lock file names its process id
give each peering its own working folder: --work /var/lib/goat-federation/<partner>
Read more¶
Exit code¶
goatbuilder exits with 1.