mirror of
https://github.com/XRPLF/rippled.git
synced 2026-08-21 06:10:58 +00:00
91588cadca
Standing up and updating one of these hosts involves a handful of steps that fail quietly when missed, and the knowledge was living in people's heads and in an untracked file on the host itself. That file died with the last rebuild. Covers updating the checkout, re-applying the host overlays a checkout can disturb, building, and starting the collector and both nodes, then verifying all three signals actually arrive rather than trusting the configuration. The failure modes it calls out are ones already hit here: bringing the collector up without the cloud overlay, which exports nothing and logs no error; omitting --force-recreate, so a config change appears applied but is not; a log directory whose name does not match the instance id, which leaves logs unlabelled while metrics stay labelled; and reading the container command line to check which config is active, which cannot distinguish the two cases because the overlay mounts over the same path. It also records two signals that read backwards: a higher acquisition timeout count can mean a node is retrying forward more cheaply rather than stalling, and outbound byte counters are recorded at the decision to send rather than at the wire, so under a flood they overstate egress by orders of magnitude. Deliberately names no credential or environment files and carries no host identity, so it is safe in a public tree. Which file holds what is documented where it is needed, next to the installer that reads it.