-
-
Notifications
You must be signed in to change notification settings - Fork 353
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
masternode: CDeterministicMNList::PoSePunish -- punished MN 7cc86b2c1e31b7e9d8e4a2e79dbbfd835607635af60a8cb82ff6d6a277259e3c #1235
Comments
Got another one today:
|
ANOTHER...
No different from the others. |
My suspicion is that this is swap related. It looks like firod requires ~2GB of memory at times. We're moving swap to faster volumes and seeing what happens. |
From my experience, firod requires at least 1.7-2.4 GB when first downloading the blockchain. Otherwise it will crash. |
That's what I'm seeing too. I turned OOM off on my MNs, so it just swaps. Even with swappiness of 1, it still does about ~500MB within a few minutes on top of the 1GB I have for the server. |
I have increased the recommended RAM size in the masternode guide and recommended having swap on. Other than these, what other things would you recommend? |
Thanks @justanwar. I'm still testing the changes where we have swap on a faster external volume than the root. It will take a while to know if the MNs I run keep getting penalties or not. I'll follow up and close this if we see less over time. |
PROTX REG TRANS ID: 7cc86b2c1e31b7e9d8e4a2e79dbbfd835607635af60a8cb82ff6d6a277259e3c
debug.log
I see nothing in the logs explaining why I was punished. What should I do? We can't keep losing nodes like this...
The text was updated successfully, but these errors were encountered: