This is going to be a quick one. It follows along with the rest of my docs regarding setting up a masternode, monitoring, and now the fun subject of log rotation!
Once your masternode is running, you'll notice your debug.log is filling up. It will continue filling up, until one of two (or sometimes both things) will happen:
- Your VPS will run out of space. This will cause your masternode to die, possibly corrupting the end of the blockchain in the process.
- If you have tons of space on your VPS, the debug.log may reach a size where the masternode daemon simply is unable to add data to it. If your masternode is 32bit, this will come rather quickly, and weird things will happen. For 64bit this is less likely, but expect weirdness when hitting the hundreds of gigabytes zone.
So how to avoid this? Very easily, using a tool you already have installed called 'logrotate'.
Simply create a file called 'coins.conf' in /etc/logrotate.d:
/home/coins/.bitcloud/debug.log {
copytruncate
rotate 4
dateext
minsize 10M
notifempty
compress
delaycompress
missingok
}
Replace .bitcloud with whatever coin you use. .zcoin for Zcoin, .8bit for 8Bit coin, etc.
This will keep your masternode healthy for a long time!