-
Notifications
You must be signed in to change notification settings - Fork 202
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
Nimbus falling back to doppelgänger unexpectedly #5845
Comments
Sorry, but this happens not unexpectedly, VC thinks that corresponding Beacon Node did not respond in time
In such case it reactivates doppelganger detection. |
Thank you for taking the time looking into this issue! I discussed this with @tersec on Discord and we weren't sure what caused it. The Nimbus VC got 3 healthy beacon nodes, just the 4th one coming back to life, that's it. We (RockLogic) do this a lot, maintainance requires taking fullnodes connected to Nimbus VCs offline, updating, etc. and getting them online again. We never experienced this behaviour on the Nimbus VC before. Discord messages: https://discord.com/channels/613988663034118151/613988663034118153/1199672828258168892 /E: Sorry, it was @arnetheduck whom I had the discussion, not tersec 🙏 |
Describe the bug
Nimbus Validator Client running for 12 days unexpectedly fell back to doppelgänger mode. This incident occurred on January 24, 2024. The VC was configured with 4 beacon nodes, with 3 of them in sync and working properly. This behavior is not a regular occurrence, and it's the first time it has been observed despite long-term use of Nimbus with multiple instances.
Log:
To Reproduce
Steps to reproduce the behavior:
unknown
Additional context
The text was updated successfully, but these errors were encountered: