You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
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"
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
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](https://private-user-images.githubusercontent.com/13444070/358851320-d0ada76c-5b2c-405d-b5e4-e76611327d40.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNDg1MjgsIm5iZiI6MTcyNjE0ODIyOCwicGF0aCI6Ii8xMzQ0NDA3MC8zNTg4NTEzMjAtZDBhZGE3NmMtNWIyYy00MDVkLWI1ZTQtZTc2NjExMzI3ZDQwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTEyVDEzMzcwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTYxNGRmMDMzNmE1NTI3Yjc5ZjVmODUxNzQwMzBiMDljZjhlYzRhZjA3NWJiNGMwNTY4NTI3ZDk4MTVjZDI2OGQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.p32mNwTCujUuKcc8Hf61-F4X-xPQID0HhdgQCiC0RxU)
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"
The text was updated successfully, but these errors were encountered: