How to use MANUAL_CLOSE in core config?

External question — Stellar Stack Exchange Author: cesarm Original post: https://stellar.stackexchange.com/questions/890 License: CC BY-SA 3.0 — https://creativecommons.org/licenses/by-sa/3.0/ Adaptation: HTML converted to plain text; contact email addresses removed. The example config states that "Ledger will only close when stellar-core gets the manualclose command". On a new private testing network (ledger#=1), after setting MANUAL_CLOSE=true , I did stellar-core --newdb & stellar-core --newhist XX (also stellar-core --forcescp ), but the stellar core network cannot start at all (constantly "Joining SCP"). Also failed with RUN_STANDALONE=true , so this doesn't look like a protocol issue. Any help/successful experience? p.s. No previous hands-on with manualclose . Edit: The other config variables to change ledger close time ARTIFICIALLY_SET_CLOSE_TIME_FOR_TESTING and ARTIFICIALLY_ACCELERATE_TIME_FOR_TESTING work just fine.

External answer — Stellar Stack Exchange Author: MonsieurNicolas Original post: https://stellar.stackexchange.com/a/943 License: CC BY-SA 3.0 — https://creativecommons.org/licenses/by-sa/3.0/ Adaptation: HTML converted to plain text; contact email addresses removed. Did you actually try to run the manualclose command after starting up the node with RUN_STANDALONE=true and MANUAL_CLOSE=true ? The "Joining SCP" status is irrelevant if MANUAL_CLOSE is set, and it will happily claim "Synced!" as soon as it closes a ledger.