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

op-reth Base fails sync - payload builder stuck #12175

Open
1 task done
Ethics3606 opened this issue Oct 29, 2024 · 0 comments
Open
1 task done

op-reth Base fails sync - payload builder stuck #12175

Ethics3606 opened this issue Oct 29, 2024 · 0 comments
Labels
C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled

Comments

@Ethics3606
Copy link

Describe the bug

2024-10-29T17:08:53.642084Z INFO reth_payload_builder::service: New payload job created id=0x05abef14ca0a55fe parent=0x23c69610fb964fd0814fa84ccb37f4cacf5c8f8dd7b8cb572729b7a12145a605
2024-10-29T17:08:53.642182Z DEBUG payload_builder: building new payload id=0x05abef14ca0a55fe parent_hash=0x23c69610fb964fd0814fa84ccb37f4cacf5c8f8dd7b8cb572729b7a12145a605 parent_number=21682329
2024-10-29T17:08:53.642547Z DEBUG payload_builder: no best payload yet to resolve, building empty payload id=0x05abef14ca0a55fe
2024-10-29T17:08:53.642611Z DEBUG payload_builder: awaiting in progress payload build job id=0x05abef14ca0a55fe

2024-10-29T17:09:13.657726Z DEBUG payload_builder: building new payload id=0x05abef14ca0a55fe parent_hash=0x23c69610fb964fd0814fa84ccb37f4cacf5c8f8dd7b8cb572729b7a12145a605 parent_number=21682329
2024-10-29T17:09:13.658092Z DEBUG payload_builder: no best payload yet to resolve, building empty payload id=0x05abef14ca0a55fe
2024-10-29T17:09:13.658125Z DEBUG payload_builder: awaiting in progress payload build job id=0x05abef14ca0a55fe

The client will loop over this error. If you unwind some blocks, it will loop/error over that point as well.

I tested and the problem does not exist on the commit used by the Base team:
https://github.com/base-org/node/blob/main/reth/Dockerfile COMMIT=1ba631ba9581973e7c6cadeea92cfe1802aceb4a

The bug was introduced sometime in the last 18 days

Steps to reproduce

Restore chaindata from snapshot: publicnode.com/snapshots

Attempt normal run

Node logs

No response

Platform(s)

Linux (ARM)

What version/commit are you on?

main

What database version are you on?

main

Which chain / network are you on?

base

What type of node are you running?

Archive (default)

What prune config do you use, if any?

No response

If you've built Reth from source, provide the full command you used

No response

Code of Conduct

  • I agree to follow the Code of Conduct
@Ethics3606 Ethics3606 added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled
Projects
Status: Todo
Development

No branches or pull requests

1 participant