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
ERROR powchain: Subscription to new head notifier failed error=websocket: close 1006 (abnormal closure): unexpected EOF #4517
Comments
Was this an error you saw only once? Your node kept running after it? |
I encountered the same here:
Afterwards the client continues to run but did not process blocks any more, there's just p2p connect & disconnect messages and more repetitions of the same error:
|
still getting those errors: [2020-01-18 15:47:28] INFO initial-sync: Processing block 246/62337 - estimated time remaining 5m57s blocksPerSecond=173.5 peers=2/2 |
[2020-01-18 16:23:13] ERROR powchain: Subscription to new head notifier failed error=websocket: close 1006 (abnormal closure): unexpected EOF |
ERROR powchain: Subscription to new head notifier failed error=websocket: close 1006 (abnormal closure): unexpected EOF I have been receiving this over and over today. I only get to about 4-8 thousand processed blocks. docker run -it -v /tmp/prysm-data:/data -p 4000:4000 -p 13000:13000 gcr.io/prysmaticlabs/prysm/beacon-chain:testFix --datadir=/data --p2p-host-ip |
This can be resolved by running your own Goerli node. The goerli node that we provide is not very stable with so many websocket connections. This error is mostly benign, your beacon chain node should attempt to reconnect and there is no penalty for not voting on eth1 data. |
thought I would share:
The text was updated successfully, but these errors were encountered: