Skip to content

GB-268: a peering host's clock is not synchronized, is too far from UTC, or could not be read

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-268 is printed by goatbuilder. The same text offline: goat explain GB-268 or goatbuilder explain GB-268.

What it means

federate phase 1 (preflight) read each edge and core host's clock from its own time service (chronyc -c tracking, else timedatectl). A Zenoh router refuses a timestamp more than 500 ms ahead of its own clock, and the partner's fabric is synchronized separately, so each side must hold its clock within half that, 250 ms by default (FED_CLOCK_BUDGET_MS), of UTC. A host that is not synchronized to an outside reference, or is over the budget, is a FAIL; a host whose clock could not be read is SKIP, never PASS.

Why it happens

  • the host's time service follows no reachable time source, or only the host's own local clock
  • the clock is synchronized but still slewing a large step, or the time source itself is wrong
  • neither chronyd nor systemd answered the probe, so the clock was not read

What to do

One line per step or alternative:

on the named host: chronyc tracking (or: timedatectl show); repair its time synchronization, then run phase 1 again
goatbuilder federate <partner> --from 1 --to 1

Read more

Exit code

goatbuilder exits with 1.