Post
Topic
Board Announcements (Altcoins)
Re: [ANN][DASH] Dash | First Anonymous Coin | Inventor of X11, DGW, Darksend and InstantX
by
orangecycle
on 04/02/2016, 12:55:31 UTC
Anyone else experiencing stability issues with their masternodes at the moment? Mine have been bulletproof for months but the last couple of weeks I'm constantly restarting them etc. I haven't made any changes to the underlying system. Has something on the network changed?

Walter
Quite possibly. I had a reliable masternode (16+ weeks of uptime) go down twice in one day, which is very unusual. I reviewed my firewall settings and realized I was not filtering some incoming traffic properly. There could be malicious users out there trying to bang on masternode IPs, looking for exploits. So I would recommend closing all the ports you don't need.  

That's a good point...

It's quite likely that someone is scanning masternode IP's, then searching each server for open ports.

If someone found open ports, they might be trying to brute force crack your password, which could look like a DDOS attack, slowing your server, possibly crashing the masternode...

How much ram does your masternode have available? The budget system is being used pretty actively, that could possibly be taking up more memory.

I'll check on the ram thing. I created a large 2Gb swap file around 10 months ago on my servers as I only had around 768Mb RAM and running 3 MNs on each server. Might be causing the problem..

Walter

Thanks for your help guys. Masternodes are stable now apart from one last issue... One of them keeps going offline but the daemon continues to run fine, I do a remote masternode start-alias from my cold wallet and that fixes it for a couple of hours (don't need to do anything with the daemon on the server). Then it drops off again an hour or two later. It's persistantly happening with one masternode. All others are running fine now. Any ideas?


Cheers

Walter

What does the daemon report when you run
Code:
dash-cli masternode status

I'm guessing it is waiting for a remote start. If you do not see "status" : "Masternode successfully started" then you should connect directly to your masternode from your local wallet and issue start-alias.

https://node40.com/blog/how-to-connect-directly-to-your-masternode-from-your-local-wallet-to-issue-a-remote-start/