-
Notifications
You must be signed in to change notification settings - Fork 336
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
moonriver chain stop catching the latest block #853
Comments
@niy655 I'm not sure what you mean, but |
hello, crystalin. For example now, my node is idle at 597740 after I restarted it. but the highest block is currently at 597756. Sep 25 03:15:54 instance-1 moonriver[43233]: 2021-09-25 03:15:54 [🌗] 💤 Idle (29 peers), best: #597740 (0x1ad7…5d33), finalized #63 (0xf049…d1b8), ⬇ 8.5kiB/s ⬆ 0.2kiB/s |
Ok, there seems to be something wrong with the finalization. It is probably not importing more because it is trying to finalize the previous ones. The question is why isn't the finalized one not moving. |
Got it, let me try to resync the parachain. Will update the result here |
After I delete the parachain db and sync it again (with relaychain completely synced), the node can catch up the latest block. Thanks a lot @crystalin. |
Had the same issue; deleting the parachain db (with the relay completely synced) and syncing the parachain again from scratch worked in one node, but did not work in another one. The parachain will basically sync to the latest block and then go idle for a while, then sync again and go idle again. This is normal if the relay is not synced, but it is. It appears it does not recognize that the relay chain is synced. Tried deleting all records except parachain db, and relay db, and restarted a few times. Problem persists. |
If after syncing it doesn't follow the best blocks anymore, usually a simple restart is enough. Otherwise it might be some networking issues |
It will catch up to the best block but after some time. And then it will get stuck again until it repeats the process. I have noticed the parachain doing this (going idle) when the relay chain is not synced, but the problem is it is fully synced. Restarts haven't helped. Resyncing the parachain from scratch works sometimes, although it is a 2-day experiment. Fixing it (sometimes) by resyncing suggests this is a software issue and not network. |
Is there a flag to run moonbeam with to enable verbose networking logs? If the parachain goes idle due to some networking error (whilst relay is fully synced) there should be an error somewhere? |
Not really, because it is simply the node not receiving new blocks, so it is hard to put an error on that. However I don't think that is the case. Simply restart the node and print the logs here |
-- Logs begin at Mon 2021-10-25 00:44:47 UTC. -- |
Parachain reached imported block 828,053, and then stopped there. Finalized block at #0. Relay kusama was at #9896806, which at the time, was the current block. Relay chain will follow the block height, whereas parachain gets left behind. |
Node eventually caught up. I guess the key here is to resync relay, restart + wait for at least an hour or so. |
Sep 25 02:17:36 instance-1 moonriver[42084]: 2021-09-25 02:17:36 [🌗] 💤 Idle (26 peers), best: #597459 (0xe8a7…881f), finalized #63 (0xf049…d1b8), ⬇ 2.8kiB/s ⬆ 1.8kiB/s
Sep 25 02:17:41 instance-1 moonriver[42084]: 2021-09-25 02:17:41 [Relaychain] 💤 Idle (38 peers), best: #9373427 (0xa1bd…8743), finalized #9373424 (0x06cb…64ee), ⬇ 154.2kiB/s ⬆ 390.6kiB/s
Sep 25 02:17:41 instance-1 moonriver[42084]: 2021-09-25 02:17:41 [🌗] 💤 Idle (26 peers), best: #597459 (0xe8a7…881f), finalized #63 (0xf049…d1b8), ⬇ 10.3kiB/s ⬆ 1.4kiB/s
Sep 25 02:17:42 instance-1 moonriver[42084]: 2021-09-25 02:17:42 [Relaychain] ✨ Imported #9373428 (0xbf50…5804)
Hello, I am trying to run a full node. The relaychain is working fine, it keep import the latest block. However, the moonriver chain stop syncing to the latest block, it stay idle. I tried restart the node, the moonriver chain will import to the latest block but then it stop syncing again.
I am using the latest release binary Moonbeam v0.12.3.
The text was updated successfully, but these errors were encountered: