bhkien Well-known member Oct 3, 2020 #1 Dear all, I had upgraded my masternode, and everything went well. However, recently I found my masternode has a state POSE_BANNED. What can I do to bring it back to work. Thanks in advance.
Dear all, I had upgraded my masternode, and everything went well. However, recently I found my masternode has a state POSE_BANNED. What can I do to bring it back to work. Thanks in advance.
qwizzie Well-known member Oct 3, 2020 #2 Looks like you got it working : https://www.dash.org/forum/threads/docs-about-pose-ban.46184/#post-223595 Make sure sentinel is updated : cd ~/.dashcore/sentinel git pull venv/bin/python bin/sentinel.py --version venv/bin/python bin/sentinel.py Make sure a cron job is active on dashd : crontab -e * * * * * cd ~/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log * * * * * pidof dashd || ~/.dashcore/dashd
Looks like you got it working : https://www.dash.org/forum/threads/docs-about-pose-ban.46184/#post-223595 Make sure sentinel is updated : cd ~/.dashcore/sentinel git pull venv/bin/python bin/sentinel.py --version venv/bin/python bin/sentinel.py Make sure a cron job is active on dashd : crontab -e * * * * * cd ~/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log * * * * * pidof dashd || ~/.dashcore/dashd
bhkien Well-known member Oct 3, 2020 #3 Thank you very much! Actually my masternode was running after update to version 0.16.0.1 ‘till this morning. Restart server doesn’t help. Finally, I had to reissue update_service command.
Thank you very much! Actually my masternode was running after update to version 0.16.0.1 ‘till this morning. Restart server doesn’t help. Finally, I had to reissue update_service command.