masternode status flips to inactive?

D

drDave

New member
Hello all,

I have just set up my very first masternode (hooray!) about 24 hours ago and all seems to be going well except that for some reason the status keeps turning from active to inactive, after maybe 2 hours. I am not sure the significance of this since I'm still new at this but I'm guessing it's bad. I have restarted it I think twice now using the masternode start-alias which, if I understand correctly, puts my masternode at the end of the queue ... ?

Details:
pubkey: Xm5VW42wfi1AWY8iLYPBXMdZ4z2CaCw6Ca
0.12.1.1
Port has remained open continuously
1000 dash have not been moved

I followed TAO's setup guide for dummies, including using VULTR, with VPS specs as per the updated 12.1 guide for dummies.

I was thinking I would start with a new wallet as suggested on the Dash Ninja Masternodes Monitoring page but I thought I'd see if anyone here might help me understand the problem before I do that. Any thoughts will be appreciated :)
 
Please update to 0.12.1.2 and make sure you installed sentinel correctly i.e. cron is configured the way it's described in https://github.com/dashpay/sentinel#3-set-up-cron and it gives you no error when you run tests https://github.com/dashpay/sentinel#4-test-the-configuration

If all is good but problem persists, pls send (zipped) debug.log from that masternode to [email protected]
(or upload it somewhere. Hint: I personally like https://transfer.sh because it lets you upload via simple cmd line)
 
UdjinM6 said:
Please update to 0.12.1.2 and make sure you installed sentinel correctly i.e. cron is configured the way it's described in https://github.com/dashpay/sentinel#3-set-up-cron and it gives you no error when you run tests https://github.com/dashpay/sentinel#4-test-the-configuration

If all is good but problem persists, pls send (zipped) debug.log from that masternode to [email protected]
(or upload it somewhere. Hint: I personally like https://transfer.sh because it lets you upload via simple cmd line)
Click to expand...


Have you tried to replace the sqlite sentinel database with a database that supports the client-server model?
I think this is the cause of your sync problems.
 
Thanks guys. Looks like my cron was configured incorrectly -- error in the path to sentinel folder. Fixed it and if that keeps it active for a while, I'll turn my attention to upgrading to 0.12.1.2 :)
 
You must log in or register to reply here.
Back
Top