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

The node suddenly encountered an error and cannot sync the latest block, showing the error: "sequencer batches out of order; after batch" #2584

Open
yongjun925 opened this issue Aug 17, 2024 · 0 comments

Comments

@yongjun925
Copy link

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. The node suddenly can’t sync blocks anymore.

Expected behavior
How can it be fixed? The current version is: nitro/v3.1.0-7d1d84c/linux-amd64/go1.21.10.
number: 243057221

Screenshots
image

Additional context
WARN [08-17|14:31:33.678] error reading inbox err="sequencer batches out of order; after batch 0xc0233b9ba0 got batch 669446" WARN [08-17|14:31:35.946] error reading inbox err="sequencer batches out of order; after batch 0xc00087a550 got batch 669446" WARN [08-17|14:31:37.953] error reading inbox err="sequencer batches out of order; after batch 0xc0e8a92870 got batch 669446" WARN [08-17|14:31:39.975] error reading inbox err="sequencer batches out of order; after batch 0xc0ebd1ede0 got batch 669446" INFO [08-17|14:31:41.154] examining existing potential successors count=1 INFO [08-17|14:31:41.154] staker: waiting for node to catch up to assertion batch current=669,446 target=669,482 WARN [08-17|14:31:41.985] error reading inbox err="sequencer batches out of order; after batch 0xc0ebd1fe10 got batch 669446"

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

1 participant