Waiting for keymanager to initialize validator client with web UI...
You'll usually see this message when your beacon node is trying to interact with a validator client before the beacon node is fully synced. This is a known limitation. When your beacon node is finished syncing, this message should go away. Visit Check Node and Validator Status to learn how to check the sync status of your beacon node. If your beacon node is reporting that it's synchronized and you're still seeing this message, reach out to us on Discord and we'll help you troubleshoot.
If your validator client is running fine without errors but you're seeing your validator balance decrease, your beacon node may be experiencing issues with connectivity, stability, or synchronization. Check your beacon node logs to see if there are any errors or crashes.
Could not import accounts: could not write accounts: file already exists without proper 0600 permissions
This usually happens when the account you're using doesn't have permission to read and write to the target directory. See this GitHub issue for a workaround.
Waiting for enough suitable peers before syncing
msg="Peer disconnected" active=0
Peers will continuously disconnect and reconnect, so don't worry about
Peer disconnected messages. If your beacon node is struggling to find peers:
- Your beacon node might be suffering from connectivity problems. Visit Improve P2P connectivity for connectivity troubleshooting guidance.
- Make sure that your firewall isn't restricting any outbound ports for Prysm.
- You may be using an incorrect genesis state or network flag. Every test network requires its own genesis state and network flag. Visit our Quickstart for the latest test network parameters.
If your node seems stuck in a loop while it is syncing the blockchain, a restart will usually resolve the problem.
level=error msg="Could not request attestation to sign at slot" error="rpc error: code = Unavailable desc = the node is currently optimistic and cannot serve validators" prefix=validator pubKey=0x860f48f1a502 slot=65740
This usually means that your execution client isn't yet synchronized. Visit Check Node and Validator Status to learn how to check the sync status of your execution client. If your execution client is reporting that it's synchronized and you're still seeing this error, reach out to us on Discord.
chain not synced beyond EIP-155
This usually means that your execution client needs more time to "catch up". If you see that your node is connected to peers and is importing data, your node is healthy. If you're still seeing this error after a few hours, let us know on Discord.
Feel free to reach out to us on Discord and we'll help you troubleshoot.