Ledger Increase Check

[l-monninger]

Summary

• RFCs: $\emptyset$.
• Categories:util

Adds an overlay that will crash the docker-compose application if the ledger has not increased in a given amount of time. This is useful for detecting node asynchrony and similar conditions without a more advanced monitoring setup.

Most of the changes here are permissions changes on compose files.

Testing

To validate

# to ensure that it will run normally
LEDGER_INCREASE_PERIOD_SECONDS=300 just suzuka-full-node docker-compose local.ledger-should-progresst will run normally

# to ensure the crash occurs
LEDGER_INCREASE_PERIOD_SECONDS=1 just suzuka-full-node docker-compose local.ledger-should-progress

Added

No automated tests have yet been added.

Outstanding issues

1. We may want to build a monitoring util container. This is a quick solution. More advanced solutions would fall under.
2. Main still has issues with containers--owing to a bad setup script. Please use an older container when testing.

[0xmovses]

Inside the nix shell I run
LEDGER_INCREASE_PERIOD_SECONDS=1 just suzuka-full-node docker-compose local.ledger-should-progress

Running docker-compose for suzuka-full-node with override files: -f docker/compose/suzuka-full-node/docker-compose.local.yml -f docker/compose/suzuka-full-node/docker-compose.ledger-should-progress.yml...
Couldn't find env file: /Users/movses/movement-dev/.env
error: Recipe `suzuka-full-node` failed on line 6 with exit code 1

Assume this is because of the aforementioned bad script. For using an old container, should I just go back one commit on main and run docker compose? And then go back to this branch and re run the command? I need some clearer instructions to test.

[l-monninger]

Inside the nix shell I run
LEDGER_INCREASE_PERIOD_SECONDS=1 just suzuka-full-node docker-compose local.ledger-should-progress

Running docker-compose for suzuka-full-node with override files: -f docker/compose/suzuka-full-node/docker-compose.local.yml -f docker/compose/suzuka-full-node/docker-compose.ledger-should-progress.yml...
Couldn't find env file: /Users/movses/movement-dev/.env
error: Recipe suzuka-full-node failed on line 6 with exit code 1
Assume this is because of the aforementioned bad script. For using an old container, should I just go back one commit on main and run docker compose? And then go back to this branch and re run the command? I need some clearer instructions to test.

To this point we have assumed a .env file. If we want to remove this, it's a line here, but this will change some assumptions in other places the docker-compose target is used. I would recommend you put in an empty .env or populate accordingly.

[l-monninger]

@0xmovses

[mzabaluev]

Is there a purpose for this standalone script file, when the ledger-should-progress inlines a copy of it?

[mzabaluev]

The execution flag change by chmod looks spurious, let's revert that.