mirror of
https://github.com/XRPLF/rippled.git
synced 2026-09-27 07:26:51 +00:00
Test 1 pointed standalone at docker/telemetry/xrpld-telemetry.cfg, whose [node_db], [database_path] and [debug_logfile] all resolve under docker/telemetry/data. Standalone builds its own private chain, so that left one NuDB holding two unrelated chains. This file already states the rule for the key generation node in Test 2, and the sibling mainnet config keeps its store under data/mainnet/ for the same reason. Derive a standalone config with the three paths redirected under data/standalone/, and run from that. Note why the flag is not the problem: --start selects StartUpType::Fresh, but the default Normal reaches startGenesisLedger() through the same branch chain in ApplicationImp::setup, so any standalone run writes a genesis ledger into whichever store the config names.