-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Struggling to sync - prysm blames geth while geth blames prysm #13810
Comments
Do you have logs @lil0uuu ? |
Same issue, started happening after upgrading Prysm to |
Same issue here, using nethermind. Was happening on 5.0.0, just updated to 5.0.2, hasn't changed. Prysm: WARN execution: Execution client is not syncing Edit: finally started syncing. Something is very slow when rebooting the client. |
Same issue |
This should be fixed in the next release, in the mean time you can try |
Here is a sample of logs I'm seeing on the prysm side, where nothing seems processed for a while, then at 01:55:09 things are moving again [2024-04-01 01:51:04] WARN p2p: Attestation is too old to broadcast, discarding it attestationSlot=8761029 currentSlot=8761153 |
Same problem.. Is there a quick fix ? |
Facing same issue ? Any updates yet ? |
This should be fixed in v5.0.3. Closing this issue unless someone observes that they are still running into this |
With 5.0.3 I keep seeing the same problem after upgrade. geth 1.14.3, windows node. It looks like node running for about 1d normally and then beacon node start flooding message repeatedly: Attestation is too old to broadcast, discarding it attestationSlot=9113540 currentSlot=9113577 logs full of these messages, slot number and current slot varies. Once node restarted, it keeps running for one more day and then story repeats. |
These logs can be safely ignored. I am going to propose a PR to remove the log message or push it to debug or trace levels. |
The same problem with prysm, I'm always getting a 4 WARN log messages with cycle "Execution client is not syncing" waiting 3-5 minutes and after syncing to new blocks. I don't understand how to fix it, but I didn't get last blocks, I have missed about a 10-20 blocks, sometimes I have current block, but not always. Version of my prysm 5.0.4 if you have ideas, solutions it would be excelent |
Facing similar issue with geth version 1.14.7 and prysm 5.0.3 Any fixes/suggestions/configs needed to fix this? |
Describe the bug
Every day my eth node struggles to sync, stuck in some kind of deadlock, where the beacon chain reports:
[2024-03-27 01:55:16] WARN execution: Execution client is not syncing
[2024-03-27 01:55:30] WARN execution: Execution client is not syncing
While execution says:
WARN [03-27|01:51:45.835] Beacon client online, but no consensus updates received in a while. Please fix your beacon client to follow the chain!
After some times (like ten minutes), it sometimes automatically resolve. Other times, I have to restart prysm, geth, or both. When restarting, it sometimes keeps happening.
geth suggests prysm is the problem ethereum/go-ethereum#28899
What's the issue?
geth: v1.13.14
beacon prysm: v5.0.1
Has this worked before in a previous version?
No response
🔬 Minimal Reproduction
No response
Error
No response
Platform(s)
No response
What version of Prysm are you running? (Which release)
No response
Anything else relevant (validator index / public key)?
No response
The text was updated successfully, but these errors were encountered: