Ok, then the issue is caused by cncli leaderlog…
Increase the swap to 6G and should be ok
free -m
sudo swapoff /swapfile
sudo fallocate -l 6G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
free -m
start/stop the node, if not working apply the WA provided earlier
now it should be ok
Restoring VM from pre-update state.
What the best stable version to go to ? before 1.34.1 ?
Don’t do it, ugrade the swap file… soon 1.35.x version will be released (vasil hf)
Too late already restoring :)))))))) Wasted 4 days trying to fix.
Is 1.34.0 stable ?
nope, 1.33.1 but next month u will be “forced” to upgrade to 1.35.x version
Thanks man, will do 1.33.1 for now
Update,
Restored my nodes from back up on 1.33.0 and all is working fine no issues. Will be waiting for stable version.
Just checking, do you have enough storage left? I remember having a similar odd issue and it was just that I ran out of storage, so when the node was starting, it would work away for a while until all the remaining storage was used and then crash. Just a thought,
Thanks for the tip man, lots of storage on all 3 nodes.
Quick update on my issue. Looks like it is fixed by adding more memory, which is very strange my node had 16 GB of RAM, should be enough right. So I was not sure if RAM was my bottle neck and decided to add 24 GB dynamically. My VM Configuration looks like this now
BP Ram utilization look like this now
No issues for 4 days now.