Repository navigation
fix(rpc): cap Caddy's container log size - #13
Merged
Merged
Conversation
…), document the sentry role of RPC nodes and never --reserved-only without a sentry
… outage filled the disk
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
rpc-1 was down for ~36 h. The disk filled to 100%, the node left
db_versionempty, and on every start it failed with:What was on the disk (75 GB):
The Caddy log is the only item caused by this repo's config: the
caddyservice had nologging:block, so Docker never rotated it. During the outage, every request was logged as a 502 with its full headers.Change
Add
json-filelog rotation to thecaddyservice intestnet/rpc/docker-compose.ymlandmainnet/rpc/docker-compose.yml: 50 MiB per file, 3 files. This matches the node service.Deploy
On each RPC host: