Skip to content
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

Errors and Warnings after power outage #13546

Closed
honcho26 opened this issue Jan 27, 2024 · 3 comments
Closed

Errors and Warnings after power outage #13546

honcho26 opened this issue Jan 27, 2024 · 3 comments

Comments

@honcho26
Copy link

Hello! I had a power outage that took down my Validator yesterday. I brought it back up when the power came back on, and my consensus and execution clients are back up and in synch (Geth and Prysm). However, my validator is showing me constant errors with this messaging:

[2024-01-27 11:42:10] WARN validator: slots stream interrupted error=rpc error: code = Unimplemented desc = unknown method StreamSlots for service ethereum.eth.v1alpha1.BeaconNodeValidator: could not connect
[2024-01-27 11:42:10] ERROR validator: Could not receive slots from beacon node, could not connect error=rpc error: code = Unimplemented desc = unknown method StreamSlots for service ethereum.eth.v1alpha1.BeaconNodeValidator

If I look at BeaconChain, it appears to be attesting just fine, but I'm worried about these errors, as that's not what I'm used to seeing. I've tried restarting the validator, but the issue persists.

Any ideas what might be causing this?

@honcho26
Copy link
Author

honcho26 commented Feb 8, 2024

Bumping this up for consideration. It continues to be an issue, even after intentionally shutting down my consensus and execution clients and updating Prysm to latest version.

@prestonvanloon
Copy link
Member

@honcho26 Looks possible that your validator was updated to the latest version and your beacon node is on an old version? Could you confirm the version(s) of the client you are running?

@honcho26
Copy link
Author

Thanks for this. You were right. I had updated my validator, but my beacon node wasn't updated after my reboot. Closing this issue.

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

No branches or pull requests

2 participants