-
Notifications
You must be signed in to change notification settings - Fork 457
Failed to generate blocks in v4.0.0-beta.1 #8587
Comments
@punkrock What is the environment (OS) you're running the node in? |
@sameersubudhi Ubuntu 22.04.2 LTS |
Did you happen to run the same generator (w/ same keys) on another node simultaneously? |
@sameersubudhi No, this is my only node and I did nothing. The error just showed up and my node stopped generating blocks but the chain kept moving like nothing happened. |
Today it happened again. Here the full logs (notice the time difference between logs!):
|
@punkrock Could you please run the node with |
Moving this issue to SDK for further resolution. |
I am failing to generate blocks again. Here the error logs (trace):
|
And again:
|
Not sure if it is an important info but I don't have to restart lisk core to fix it. I just have to re-enable the generator. Do you still need more logs or is it clear to you what the issue is, @ManuGowda? |
@punkrock re-enabling generator will fix the issue seems bit strange , but it looks like somehow your node is disconnected from the network. I'm investigating further |
@shuse2 Just to make sure that there is no misunderstanding: With "fix the issue" I mean that I can re-enable the generator without the need to restart Lisk Core. Of course it doesn't fix anything because it happens some hours later again. Something is just disabling the generator for what ever reason. |
Ok, new infos @sameersubudhi @shuse2 @ManuGowda: The reason why I am starting to miss blocks is because Lisk Core restarts itself for unknown reason and after a restart the generator is obviously disabled. So, we need to figure out, why Lisk Core restarts itself. Here are the logs from Core just before it restarted: lisk-core-out.log
|
Another update. From my syslogs. looks like 2 GB RAM without SWAP are not enough. I will add a SWAP of 4 GB and see if it works:
|
@punkrock thanks for the investigation. Maybe 2GB is too small to run the Core 4.0 node. Let us know how it goes after changing to the 4GB memory 🙏 |
Since there is no update, I will assume this problem is resolved |
In
v4.0.0-beta.1
the node stopped to generate blocks with the following error. The chain on the node kept moving but stopped to generate blocks.Error (no other errors in logs):
The text was updated successfully, but these errors were encountered: