which will monitor your masternode to be sure it's running, and restart it if it should stop.

Dashninja does have a lot of scripts running the pages, and I also have trouble keeping it open on my old machineBut try this: https://dashpay.atlassian.net/wiki/pages/viewpage.action?pageId=8880256 actually, that script is more complex, and is supposed to deliver an email notification. All you really need is to restart. See how I have it belowAlso, So that if the server goes down, but comes back up within an hour, your masternode will be restarted automatically. Make a cron-job. You can do this either as root or as the user. I think it's better as the user of the masternode, so a cron job per masternode/user. You do this so:type in:choose your favorite editing thingy, I use nano, others vi (most popular) and hopefully one of them is installed on your machine. Just enter the number next to the choice:At the bottom of the file that opens, insert this: (Use the down arrow key to get to the bottom of the file)Copy and past into screen:writes the changessaves the file and closes nanoWell, that's what I have in there. The first line means to restart dashd when system is rebooted. The second line checks to see if dashd is running, and if not, executes the mn_watch.sh script I placed in home/user/ folder. The second cron job on the list checks every minute (probably too often, come to think of it) and if dashd isn't running, executes this sh file that I have at that location. It's called mn_watch.sh, I made it in nano, and the only thing inside is this:To make this file, again open nano:this opens a new file named mn_watch.sh.Now copy this and paste it into your screen:and finally, again, doandto save.And this is because I keep my dashd, dash-cli and dash-tx files in usr/local/bin so that I don't have to do ./ before every command. Also, I have two masternodes on this machine, and I only have to update once, then start dashd for each user.explaination: 'pidof dashd' refers to dash.pid which you can see in your .dash folder when dashd is running. I think it links to the running service. So if it's not there, it means dashd isn't running, hence the "then" statement of executing dashd. make sense? I'm still learning too. LOL, I just tried to open my dash.pid file to see what's inside and it disappeared! Wonder if my dash will try to restart now, LOL.I really think your masternodes might not be running properly. The consensus system has actually been running perfectly as I understand it?Edit: My pid file version wasn't working, so I tried this and it seems to work.Edit2 The original does indeed work, don't know what went wrong in my testing, but this is simpler, and probably better, as it uses pid file instead of grep