This repository has been archived by the owner on Jan 2, 2025. It is now read-only.
Add check on latest_block_time #51
Open
Conversation
This file contains 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
dylanschultzie
approved these changes
Feb 7, 2023
|
This might pertain to this issue as well: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
A node can be
catching_up:falseyet when/status?is inspected thelatest_block_timecan be behind the current time.Symptoms
This causes issues when trying to monitor missed blocks, since the node doesn't get updated, neither does the missed block counts, but yet the
cosmos/slashing/v1beta1/signing_infosquery will return a response as if the node was caught up.Solution
Check that the
latest_block_timeis within thestalled_minutesamount and if not don't use it as an RPC node and report it as down/not synched.