Masternode setups can be tricky. The masternode and the wallet run on the same computer. Since a masternode needs a 24/7 internet connection, the wallet on it is, as they say, “hot”. It’s always connected.
Masternode setups can be tricky. With this cold wallet setup, we run going to run the masternode with an empty wallet. The wallet with the actual collateral coins will be located on a different computer (this can be your Windows, Mac or Linux workstation. Anywhere else but the masternode itself will do).
So, as of last Sunday all java servers in my park started running at 100% CPU capacity. Turns out there’s a leap second bug in current java releases on Linux servers. I found this post where a temporary workaround/fix is provided.
Some users have this (nasty) habit of staying logged into their shells. Not just one, but A LOT of them, very annoying to see all those idle connections (IMHO). So to prevent these idle connections from staying open until the end of days is to set a simple environment variable called “TMOUT”.