GB-182: the run journal cannot be read¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-182 is printed by goatbuilder. The same text offline: goat explain GB-182 or goatbuilder explain GB-182.
What it means¶
<work>/state.json is the only account of what ran for this peering, so a journal that does not parse, has a later schema than this goatbuilder reads, or names another peering is refused rather than overwritten. A journal of the same schema that a later goatbuilder wrote is read: a word or field this one does not know is shown as written and kept.
Why it happens¶
- the file was edited by hand or cut short
- a later goatbuilder wrote it with a later schema (the message names the schema and the goatbuilder that wrote it)
- two peerings share one working folder
What to do¶
One line per step or alternative:
use the goatbuilder that wrote it, or move the file aside and run again (the run then starts with no journal, and --resume skips nothing)
give each peering its own working folder: --work /var/lib/goat-federation/<partner>
Read more¶
Exit code¶
goatbuilder exits with 1.