-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
amber/flint validator loses peer to sentry after "Invalid justification provided by $SENTRY_IDENTITY for #..." #259
Comments
seen exactly the same on flint couple days ago: invalid justification => Reserved peer disconnected => 0 peers |
looks related to this paritytech/substrate#4678 |
so possibly this can also be related to this paritytech/substrate#2187 |
Is there any update to this? Looking to see if this was anything to do with file descriptor limitations that were previously seen on polkadot (similar behavior with the node not being seen by sentries: paritytech/polkadot#856) Looking at TCP connections alone, it doesn't look anything like the same magnitude, but it does showcase the spike, clean connections, repeat. The gaps are when the service is restarted. Will create a script to temporarily monitor this and post logs |
Sentry setup has been deprecated by Parity, closing for now |
seen it several times on Amber and Flint networks. looks like peer is lost after invalid justification by sentry:
full logs for tonight's issue on Amber (it was handled by my script https://github.com/AGx10k/substrate-restart-stalled-blocks):
amber-validator (QmPfsj2YrU8aW6A6PJZrcfNgnCxLVB1Ea5Ekt2uf8Bq8Jb is sentry):
amber-sentry for the same time period:
The text was updated successfully, but these errors were encountered: