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

[yongjun925]

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

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"

[qedgardo]

Any update on this issue?

[joshuacolvin0]

The log message you provided has a pointer instead of the value, issue was fixed here:
#2488

If you use the latest verson of Nitro, you will have more informative logs. Also, any questions about running node are best asked in the Discord server for faster response.