europound Member Oct 16, 2017 #1 if ninja pl says masternode is inactive and port open but dashman says all YES + masternode queue/count is moving and ./dash-cli masternode list full | grep IP is ENABLED + timer ticking then ok?
if ninja pl says masternode is inactive and port open but dashman says all YES + masternode queue/count is moving and ./dash-cli masternode list full | grep IP is ENABLED + timer ticking then ok?
Miner237 Active member Foundation Member Oct 17, 2017 #2 you may want to consult a third or fourth party node to confirm, maybe check a dash client wallet for your node status. some nodes could have you banned and appear inactive to them only...
you may want to consult a third or fourth party node to confirm, maybe check a dash client wallet for your node status. some nodes could have you banned and appear inactive to them only...
Weber K. New member Nov 1, 2017 #3 Hi! I am facing the same situation. In Dash Ninja is inactive. In Dash Central: Your masternode dropped off the masternode list and is not enabled! Dash wallet masternodes tab says: ENABLED. Dash wallet masternode list says: ENABLED. dashman says: queue position nn/4428 (and moving down). Your post makes me less anxious... Edit: Mine is solved! Stopped dashd, deleted *.dat, restarted dashd and issued start-alias. Last edited: Nov 1, 2017
Hi! I am facing the same situation. In Dash Ninja is inactive. In Dash Central: Your masternode dropped off the masternode list and is not enabled! Dash wallet masternodes tab says: ENABLED. Dash wallet masternode list says: ENABLED. dashman says: queue position nn/4428 (and moving down). Your post makes me less anxious... Edit: Mine is solved! Stopped dashd, deleted *.dat, restarted dashd and issued start-alias.