Skip to content
This repository has been archived by the owner on Jan 2, 2025. It is now read-only.

feature: add check for frozen node #56

Open
dylanschultzie opened this issue Feb 26, 2023 · 2 comments
Open

feature: add check for frozen node #56

dylanschultzie opened this issue Feb 26, 2023 · 2 comments

Comments

@dylanschultzie
Copy link
Collaborator

This could potentially be done by:

  1. scan /status and check if latest block height is too far away
  2. check if there are current peers?
@dylanschultzie
Copy link
Collaborator Author

Upon further inspection, it appears 1 is already being done.

I'm guessing, then, that the issue is that because events are no longer being consumed by the websocket, it can't know that the machine has stalled. Perhaps that means a secondary loop that checks cc.lastBlockTime against cc.lastBlockTime.Before(time.Now().Add(time.Duration(-cc.Alerts.Stalled)*time.Minute), but not in its current location?

@dylanschultzie
Copy link
Collaborator Author

seems like that's what's happening here... https://github.com/blockpane/tenderduty/blob/main/td2/rpc.go#L120

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant