-
Notifications
You must be signed in to change notification settings - Fork 262
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
Node did not receive new block events anymore, had to restart #543
Comments
Can't start my node. Here is the log: INFO [04-13|08:27:08.358] New LLR summary last_epoch=0 last_block=79266627 new_evs=0 new_ers=0 new_bvs=60 new_brs=0 age=none |
Describe the bug
My read only node got stuck, meaning no new block events and therefore no pool reorgs, mempool piled up.
To Reproduce
No idea how to reproduce that
Expected behavior
Node does not get stuck
Screenshots
Here are the last few loglines:
WARN [04-13|06:59:34.865] Pre-internal transaction reverted txid=0xafbd6d03a6acfb591e90e8e5d89dfffa61f3ceb6351648e814aef6e933c17882
WARN [04-13|06:59:34.865] Internal transaction reverted txid=0xa8c423405c7cb80923925b3b1104c75326e02f43a6705dbde9d74feefbd0b157
INFO [04-13|06:59:34.889] New block index=79264528 Atropos=276163:6035:e57490 root="268b90…69cb73" gas_used=3,734,054 txs=4/0 age=3.122s t=24.466ms
WARN [04-13|06:59:35.790] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:35.791] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:35.794] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:35.796] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:35.806] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:35.807] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
INFO [04-13|06:59:36.115] New DAG summary new=174 last_id=276164:1:652fdc age=340.215ms t=219.406ms
WARN [04-13|06:59:36.115] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:36.655] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:37.423] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:37.643] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:37.996] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:38.056] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:38.356] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:38.398] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:38.545] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
WARN [04-13|06:59:40.462] Incoming event rejected event=276164:1:652fdc creator=17 err="wrong event epoch hash"
Desktop (please complete the following information):
Ubuntu
The text was updated successfully, but these errors were encountered: