-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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: method trace_block raises errors #5306
Comments
Same here, using same version (2022.09.1-alpha).
|
Getting this as well (happens on trace_transaction and trace_filter as well). Two more examples:
The second fails on this transaction: https://goerli.etherscan.io/tx/0x5ac02c918167f0e1b9b3c0497a70a04414a5aa21da596ebec82063648b194ff0 Error is Any ideas here? FWIW these traces work on Geth debug_. |
we will check, all three cases... |
Looks like an issue with tracing flashbot blocks - probably because the eth is received and sent within the same block there is some issue. Investigation continues with @enriavil1 |
@noam-alchemy can you attach the correct traces (geth or parity-style) for a couple of cases? I think that could speed up the debugging. |
@noam-alchemy thanks! not sure if that flashbots though, could be red herring, because it looks like people have different blocks... |
@mandrigin sorry tested on mainnet instead of goerli. posting correct traces now. one moment. |
@fedecastelli can you also attach here at least txs and block numbers you having issues with? |
@noam-alchemy also if you have older blocks on Goerli that you have issues with, post them here too (pre-merge ideally), because I want to check something |
ALL ON GOERLI Problematic block: 7507055 https://goerli.etherscan.io/tx/0x31489e528b8f786c684eafc7c257d5a08e65a5a81bd7351d7b9f78183a9839d6 output with
|
Here's another one: https://goerli.etherscan.io/tx/0x76789508c0a29ade6f8206d7a6c0b7b102366c86c5c4494fab676bf4bfcae96d
|
Note they're both in the second to last index in the block, not sure if that's related. |
Let me know if you're able to confirm or deny the Flashbots theory - that would be helpful. |
maybe, but if you can find something before block 7183830 -- that would be useful |
basically we need to check if these are the same blocks broken for people, if so -- probably the issue is in the tracing code, if not -- maybe there is some index being broken |
Asking and will keep you updated. Haven't seen any reports until pretty recently. |
@mandrigin here's another one. also the second to last transaction in the block (not before your threshold though). https://goerli.etherscan.io/tx/0x5ac02c918167f0e1b9b3c0497a70a04414a5aa21da596ebec82063648b194ff0 |
So far all the blocks have been flashbot blocks so it might not be a red-herring |
@mandrigin I'm sorry for my late reply but I didn't receive the notification. I'm getting errors on the mainnet and the first block with the error is |
do we have any news about this issue? |
The Flashbots theory doesn't seem right. Here's a block that works fine: https://goerli.etherscan.io/block/7547026. |
Hey guys - getting multiple reports of this on Mainnet Ethereum now. Is it possible to prioritize a fix now that the Merge has landed (which is absolutely big time, congrats 🐼)? |
Any updates on this issue? This is affecting multiple subgraphs like that of gnosis-safe and multiple others on The Graph's hosted service. |
Culprit transaction on mainnet: https://etherscan.io/tx/0x2fdf04a1d70c3cfa1f9d89baf080377ca110c5dbc28def63b01e18b270e85f6f Note that like all the other reports, this is the second to last index in the block. That seems to be the one common theme here. |
Did anyone find any other block on the Mainnet apart from 15539509? I tested 1000 blocks after that and didn't find the issue in those. Dump here: https://privatebin.net/?0b81eea974d7a1e8#CzVVSGZhZLv15vSfFzAtxMVWfcjcpLV1f6H7E7Pus6YV It's important to note that the same thing is happening on Goerli; however, we're seeing frequent occurrences (many blocks) of this on Goerli. |
Hey, is there any ETA to fix this issue? |
Encounter the same problem with block 15539509 |
Same issue using the release version 2022.09.02. I hope it will be fixed soon. |
Believe got fixed on devel already |
@enriavil1 do you know if it's safe to use the Is there a chance my database will be corrupted?
|
You can upgrade to the new alpha version now |
I upgraded |
If you previously ran non-released version prior to 2022.09.02, then your block bodies are probably broken (there was a flawed code in devel for several days, but it did not get into released version). You need to reset headers to fix that This is how to do it. First, stop Erigon, then run this (make sure that
It will trigger re-downloading of headers and bodies after the snapshot and the whole thing may take hour or two |
This issue is fixed in devel, please check the above solution if you still have issues (block bodies may be broken if you used a previous devel version with the issue). |
@revitteth I was not using a
How can I fix it without re-sync everything? |
A similar issue is still present with {"id": 0, "jsonrpc": "2.0", "method": "trace_transaction", "params": ["0x78738a28e62b9ab4250b0fa3baaaa93961b2d657ae17fb9e4adb49cebde7b350"]} I'm getting the following result: {
"jsonrpc": "2.0",
"id": 42,
"error": {
"code": -32000,
"message": "first run for txIndex 0 error: nonce too high: address 0x72d9E579f691D62aA7e0703840db6dd2fa9fAE21, tx: 2423619 state: 0"
}
} Currently working on a similar issue with Nethermind: NethermindEth/nethermind#5936 |
System information
Erigon version: v2022.09.01
OS & Version: Linux
Commit hash : 4067b7c
Expected behaviour
I updated my erigon client version from
2022.99.99-dev
tov2022.09.01
. I restarted the client and I started to get errors extracting traces.Actual behaviour
When I try to extract traces from my archive node, I see this error:
Could someone help me with this issue?
The text was updated successfully, but these errors were encountered: