-
Notifications
You must be signed in to change notification settings - Fork 305
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
Doppelgänger stuck when primary node isn't Teku #7595
Comments
Hi @stefa2k, according to the logs, the DG detection doesn't look stuck: |
There are no more logs, there is simply nothing happending in more than 25 minutes between
I expect logs like this:
but there's nothing in the logs provided in the op. The 500 keys were alive and ready to perform duties, after switching the Teku beacon node (previously 4th in the list) to the first in the list Teku vc started without an issue immediately with duties after So I guess the conclusion is that |
The |
Actually the validators statutes requests when registering the validators do not fallback to the configured failover BNs unfortunately. I guess what's happening here is that the |
Thanks @mehdi-aouadi to look into this, I'll have a closer look and re-evaluate this after the next release including #7423 ! If you don't mind, I'll post an update after that. |
@stefa2k Could you also look into logs of first bn when it's not Teku, Prysm or whatever. If there are any errors in it, it could give us an idea, what's going wrong |
I'm closing this issue for now. As discussed, the next release will include some validators registration improvements. Feel free to reopen it if despite of that you still have the same issue |
Description
VC is connected to 5 nodes (in order):
Teku vc doesn't start any validator duties after performing doppelgänger check successfully.
Changing the order of the nodes, making Teku the primary node, seems to resolve the issue.
Steps to Reproduce (Bug)
Connect a vc to multiple bn, primary should be not Teku.
Expected behavior: Teku vc performs doppelgänger check and successfully starts performing validtor duties.
Actual behavior:
Frequency: Pretty often
Versions (Add all that apply)
The text was updated successfully, but these errors were encountered: