Skip to content
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

failed to get logs for block #26498859 #274

Open
karlb opened this issue Nov 15, 2024 · 9 comments
Open

failed to get logs for block #26498859 #274

karlb opened this issue Nov 15, 2024 · 9 comments
Assignees

Comments

@karlb
Copy link

karlb commented Nov 15, 2024

cast logs --from-block 26498859 --to-block 26498859 --rpc-url https://alfajores-forno.celo-testnet.org/

fails with
Error: server returned an error response: error code -32000: failed to get logs for block #26498859

I can reproduce the same error with a local synced node. The logs show the following error

op-geth-1  | ERROR[11-15|13:10:42.752] Invalid receipt array RLP 
hash=877281..16a7c3 err="rlp: expected input string or byte for []uint8, decoding into ([]*rawdb.receiptLogs)[2](rawdb.storedReceiptRLP).PostStateOrStatus"

The block has three txs, one of them is a CIP-64 tx, so it could be related to the CIP-64 receipt handling.

@karlb
Copy link
Author

karlb commented Nov 15, 2024

Getting the receipts for each tx separately works fine with:

export ETH_RPC_URL=https://alfajores-forno.celo-testnet.org
cast receipt 0xce9354c212ca4d8fa5c6020d7dae2ce3f3839f685ce16d87c86fa1e5e06733f1
cast receipt 0xf6217b381bc60209b91dfe9885f48cda229b232b1b5128b9a13c7c0c209aa669
cast receipt 0xa9a7307dbd08f485fab290ddbdb89989f926e37634cb07690a935683290f36fc

@karlb
Copy link
Author

karlb commented Nov 15, 2024

The problem also affects other blocks like 29876133.

@carterqw2
Copy link

Same happens for 30819231.

@alecps alecps self-assigned this Nov 18, 2024
@karlb
Copy link
Author

karlb commented Nov 27, 2024

@palango palango added this to the 5 - Celo MVP Mainnet milestone Nov 28, 2024
@piersy
Copy link

piersy commented Nov 28, 2024

@karlb So I guess we can consider this closed once we've updated our alfajores nodes with the next release?

@karlb
Copy link
Author

karlb commented Nov 29, 2024

I think forno is already running a fixed version, but I would keep the issue open until there is an official release with the fix in it.

@lvpeschke
Copy link

Have partners who've noticed problems been made aware of the fix and has someone verified it works on their end?

@karlb
Copy link
Author

karlb commented Dec 2, 2024

A release should happen really soon, then we'll let everyone know, so that they can take advantage of the fix even if they run their own node. I also sent the link to this issue to the two parties noticing this problem, so they could follow that way in the mean time if they are interested.

@palango
Copy link

palango commented Dec 10, 2024

Can we close this, now that https://github.com/celo-org/op-geth/releases/tag/celo-v2.0.0-rc1 is released?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants