-
Notifications
You must be signed in to change notification settings - Fork 44
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
v2.60.0
cannot read from datastream
#1513
Comments
Please could you share your config, it looks like your node is having trouble getting anything from the stream. I have just synced from scratch using v2.60.0 without issue. |
@hexoscott For sure! Here's the compose entrypoint and command, and the mainnet.yaml compose
mainnet.yaml
|
same here, but for xlayer,
|
I was unaware that 2.60.0 requires a full re-sync. Re-syncing now to see whether that solves the issue. "As for older DBs, version 2.60.X is incompatible with a DB created by a 2.0.X version so will require a full re-sync on the newer version." |
mine is already sync from scratch |
Yes, same result here. After resyncing xlayer and polygon-zkevm on 2.60.0, I still see these error messages "Error downloading blocks from datastream" |
Can you can try netcat or similar to connect to the datastream port from your Docker environment? We have been unable to replicate this issue from our side. |
That's from inside the cdk-erigon container During sync, the datastream connection is healthy:
|
Log of an xlayer sync, maybe you can see where these errors may originate from, with more context. |
Issue also seen in |
To clarify, even with these warn messages and "Error downloading blocks from datastream error" including the "garbage" output on that line, the node still keeps up with head. It is staying synced from what I can see; it is also throwing out these warnings frequently. |
Could you confirm what these values are set to on the sequencer node this RPC is consuming from? zkevm.data-stream-inactivity-timeout Are you using any datastream repeaters in between the original sequencer and the RPC consuming them or anything like that? |
If you're staying synced but the connection is being frequently dropped the issue is likely in the repeater or in these config settings being too short of a timeframe |
This is the sequencer and the streams we are using in the config yaml. No repeaters, and I don't know how the sequencer is configured: But maybe you do?
For Polygon zkEVM it's similar:
|
Erigon command as seen by
|
Is there any update regarding this error ? I also face it after syncing from scratch both zkevm and xlayer on V2.61.0 |
@yorickdowne do you encounter this error syncing from datastreams other than xlayer? Are we able to establish the datastreamer version being used by xlayer? |
Hello @revitteth, I’ve encountered this on Polygon zkEVM and on XLayer. I do not know how to check data stream version for either. |
Hello @revitteth we see it on both xlayer and zkevm mainnets and testnets |
Tested on Polygon-zkEVM mainnet and XLayer mainnet
Batches stage shows an error:
followed by this, which means it recovers? This alternates, the next run of 3/15 will show an error again
v2.0.1
does not show these errors.The text was updated successfully, but these errors were encountered: