protx update_service pose_banned protx-dup (code -26) same ip
got pose_banned
trying to update with the same ip address
cannot do that?
after pose_banned I must switch to new ip?
or if the same IP then do new protx register? :/
proTxHash: The transaction id of the initial ProRegTx
https://docs.dash.org/en/stable/masternodes/maintenance.html#proupservtx
how do I update to a new ip?
where to get proTxHash
it does not exist
Example (remove line breaks if copying):
protx register_prepare...
dashd as root will not work?
* * * * * cd /root/.dashcore/sentinel && venv/bin/python bin/sentinel.py 2>&1 $
* * * * * pidof dashd || ~/.dashcore/dashd
and sentiel should be running every minute
and if dashd is not running then start dashd as well...
can I use dashman?
bootstrap is ok?
reindex is a must?
root@a52de8b7eaa3:~# cd ~
root@a52de8b7eaa3:~# git clone https://github.com/moocowmoo/dashman
Cloning into 'dashman'...
remote: Enumerating objects: 1265, done.
remote: Total 1265 (delta 0), reused 0 (delta 0), pack-reused 1265
Receiving...
Where are the logs?
How could I debug this bs pose ban?
After pose ban strikes I cannot access daemon right?
Mn declines connection?
Masternode connect ip unsuccessful
solution is to start docker container from scratch, otherwise won't be able to shake off deep internal corruption that will pop up some days later
remove all related to mn
and start from scratch
seems to help
just a minimal ubuntu docker + all libs needed for dash to run
docker is great, but when it goes into limbo or its docker-proxy lib then all hell breaks loose
could you add self-checking and filesystem check mechanisms to dash?