MN pose banned

C

coinjohn

New member
Hi,

I would like to ask for help. My MN has started being pose banned since Sunday. I updated to last ver 21.0.2 and started again but it got banned again.
I briefly checked VPS and there is no issue in terms network availability. I am running 2CPU 4GB RAM Ubuntu 20.04 LTS x64

I also checked logs not sure what should I look for.

2024-08-06T11:55:22Z CDeterministicMNManager::BuildNewListFromBlock -- MN 9e7f60a9857d04bac259262d55ef457c300222a213c828b2c67c735904658ed2 added at height 2117136: CProRegTx(nVersion=2, nType=1, collateralOutpoint=7a2acd6a2cb443287aee9714c58e82c04010571bfb1d2151d8a0072ef3be2685-1, addr=185.119.196.136:9999, nOperatorReward=0.000000, ownerAddress=Xk2QHTCxb95YhzKoaQBvSgAVrainAcu4R9, pubKeyOperator=95fecd5c42217a2e3cfa4fbf077e2324005e47ba4698aa6a0a82f4a382bf1ab294403fc6cd067b448b545121aad9ee97, votingAddress=Xer8QSQ9GM6CAqMAGmxndTXxX5ZM548P6N, scriptPayout=Xe7xsCztEFLpUuJL8JWG65P4T8FXXEMVkM, platformNodeID=b439f25abe95293c1b25eaa1319309a9696417a6, platformP2PPort=26656, platformHTTPPort=443)
2024-08-06T11:55:22Z UpdateTip: new best=00000000000000252dc10a32ae2c75b011fbed82e5785e3cd38ac21ccf960c93 height=2117136 version=0x20000000 log2_work=79.258525 tx=53944855 date='2024-08-06T11:55:17Z' progress=1.000000 cache=0.7MiB(5031txo) evodb_cache=0.0MiB
2024-08-06T11:55:22Z ProcessNewBlock : ACCEPTED
2024-08-06T11:55:22Z IsValidMNActivation: set MnEHF for bit=10 is valid
2024-08-06T11:55:22Z CDKGSessionManager::InitNewQuorum -- height[2117136] quorum initialization failed for llmq_50_60 qi[0] mns[0]
2024-08-06T11:55:22Z CDKGSessionManager::InitNewQuorum -- height[2117136] quorum initialization OK for llmq_100_67 qi[0]
2024-08-06T11:55:24Z ThreadSocketHandler -- removing node: peer=857 nRefCount=2 fInbound=1 m_masternode_connection=0 m_masternode_iqr_connection=0
2024-08-06T11:56:00Z ThreadSocketHandler -- removing node: peer=858 nRefCount=2 fInbound=1 m_masternode_connection=0 m_masternode_iqr_connection=0
2024-08-06T11:56:31Z ThreadSocketHandler -- removing node: peer=859 nRefCount=2 fInbound=1 m_masternode_connection=0 m_masternode_iqr_connection=0
2024-08-06T11:56:54Z [ProcessBlock] h[2117137] numCommitmentsRequired[0] numCommitmentsInNewBlock[0]
2024-08-06T11:56:54Z UpdateTip: new best=00000000000000106cc76703ee25065e1ef7c2b0d47c15243b8d39bdabe774ef height=2117137 version=0x20000000 log2_work=79.258525 tx=53944872 date='2024-08-06T11:56:49Z' progress=1.000000 cache=0.7MiB(5085txo) evodb_cache=0.0MiB
2024-08-06T11:56:54Z ProcessNewBlock : ACCEPTED
2024-08-06T11:56:54Z IsValidMNActivation: set MnEHF for bit=10 is valid
2024-08-06T11:56:55Z [ProcessBlock] h[2117138] numCommitmentsRequired[0] numCommitmentsInNewBlock[0]
2024-08-06T11:56:55Z UpdateTip: new best=0000000000000011bda1eee4370db296a18cd52ac4ce8bffb357449188c0afa4 height=2117138 version=0x20000000 log2_work=79.258526 tx=53944875 date='2024-08-06T11:56:54Z' progress=1.00000

Any ideas or tips?

Thanks in advance
 
@coinjohn

You need to issue a protx update_service (Masternode) or protx update_service_evo (Evonode) command to fix your PoSe ban.
You can either do that through Dash Masternode Tool through Update service or you can do it manually through your (unlocked) Dash Core wallet - Console. If you do it through DMT make sure you add your BLS info there, in DMT that will be your public and private operator key.

Full command in case you want to do it through Dash Core wallet :

Masternode : protx update_service "proTxHash" "ipAndPort" "operatorKey" ( "operatorPayoutAddress" "feeSourceAddress"
Evonode : protx update_service_evo "proTxHash" "ipAndPort" "operatorKey" "platformNodeID" platformP2PPort platformHTTPPort ( "operatorPayoutAddress" "feeSourceAddress" )

Note : operatorPayoutAddress can be "" to keep it unchanged, the rest need to be filled.

If you use DMT you dont need to have funding for the pose ban fix transaction, if you want to do it manual through Dash Core wallet - Console you will need to have a funded fee source address that will handle the transaction fee.
 
Last edited:
qwizzie said:
@coinjohn

You need to issue a protx update_service (Masternode) or protx update_service_evo (Evonode) command to fix your PoSe ban.
You can either do that through Dash Masternode Tool through Update service or you can do it manually through your (unlocked) Dash Core wallet - Console. If you do it through DMT make sure you add your BLS info there, in DMT that will be your public and private operator key.

Full command in case you want to do it through Dash Core wallet :

Masternode : protx update_service "proTxHash" "ipAndPort" "operatorKey" ( "operatorPayoutAddress" "feeSourceAddress"
Evonode : protx update_service_evo "proTxHash" "ipAndPort" "operatorKey" "platformNodeID" platformP2PPort platformHTTPPort ( "operatorPayoutAddress" "feeSourceAddress" )

If you use DMT you dont need to have funding for the pose ban fix transaction, if you want to do it manual through Dash Core wallet - Console you will need to have a funded fee source address that will handle the transaction fee.
Click to expand...
How can I do it from DMT? I see update service in MN actions which is only for changing payout address
 
coinjohn said:
How can I do it from DMT? I see update service in MN actions which is only for changing payout address
Click to expand...
You use Update service also to fix PoSe bans. If you click on 'show commands for manual execution' you will see most of the command filled out for you. So you could just copy and paste that and add a fee source address to it, if you want to go through Dash Core wallet. Or just click on 'Sent update transaction' if you want to do this through DMT. Just make sure you have added both your operator privkey (BLS priv key) and operator pubkey (BLS pubkey) to DMT, or your transaction will not go through.

Knipsel.JPG

At the far right you can use that little down arrow to switch from view as public key to view as private key. That way you can add both keys to DMT in edit mode.
 
Last edited:
@coinjohn no need to go into manual solution.
On DMT hit MN actions/Update service, do not change anything there and just "Send update transaction" on the bottom right to the network. It will solve the issue of your MN remaining in the pose_ban status.
 
@splawik21 thanks it fixed pose ban. However there needs to be some rootcause why it is happening every two days. As I said the network availability of VPS is 100%. Not sure what should I look for in the logs.
 
The log is full of these messages:

Code: 
2024-08-06T08:40:52Z ThreadSocketHandler -- removing node: peer=126884 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:52Z ThreadSocketHandler -- removing node: peer=126877 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:53Z ThreadSocketHandler -- removing node: peer=126885 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:55Z ThreadSocketHandler -- removing node: peer=126888 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:57Z ThreadSocketHandler -- removing node: peer=126890 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:58Z ThreadSocketHandler -- removing node: peer=126891 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:58Z ThreadSocketHandler -- removing node: peer=126892 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:58Z ThreadSocketHandler -- removing node: peer=126893 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
 
coinjohn said:
The log is full of these messages:

Code: 
2024-08-06T08:40:52Z ThreadSocketHandler -- removing node: peer=126884 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:52Z ThreadSocketHandler -- removing node: peer=126877 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:53Z ThreadSocketHandler -- removing node: peer=126885 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:55Z ThreadSocketHandler -- removing node: peer=126888 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:57Z ThreadSocketHandler -- removing node: peer=126890 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:58Z ThreadSocketHandler -- removing node: peer=126891 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:58Z ThreadSocketHandler -- removing node: peer=126892 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
2024-08-06T08:40:58Z ThreadSocketHandler -- removing node: peer=126893 nRefCount=2 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0
Click to expand...
try searching for ERROR or WARNING in your log
I think the above is normal.

Also you need to update A.S.A.P to v21.1.0 that came out a few hours ago.
Network is already at 40% and will start PoSe scoring Masternodes and Evonodes not on v21.1.0 around 70%

See :

https://www.dash.org/forum/index.ph...1-1-0-release-announcement.55150/#post-239072
https://www.dashninja.pl/deterministic-masternodes.html
 
Last edited:
In the logs i found this

Code: 
23f035e3e17935111cda19c25d6a, bad-fork-prior-to-checkpoint
2024-08-08T07:49:27Z ERROR: ContextualCheckBlockHeader: forked chain older than last checkpoint (height 1874881)
2024-08-08T07:49:27Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000000000000318dd8ec152a49c221d14d                                                                                    23f035e3e17935111cda19c25d6a, bad-fork-prior-to-checkpoint
2024-08-08T08:12:04Z ERROR: ContextualCheckBlockHeader: forked chain older than last checkpoint (height 1874881)
2024-08-08T08:12:04Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000000000000318dd8ec152a49c221d14d                                                                                    23f035e3e17935111cda19c25d6a, bad-fork-prior-to-checkpoint
2024-08-08T10:23:34Z ERROR: ContextualCheckBlockHeader: forked chain older than last checkpoint (height 1874881)
2024-08-08T10:23:34Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000000000000318dd8ec152a49c221d14d         

2024-08-06T11:25:03Z WARNING: option -rpcallowip was specified without -rpcbind; this doesn't usually make sense

I am already running on 21.0.2
 
coinjohn said:
In the logs i found this

Code: 
23f035e3e17935111cda19c25d6a, bad-fork-prior-to-checkpoint
2024-08-08T07:49:27Z ERROR: ContextualCheckBlockHeader: forked chain older than last checkpoint (height 1874881)
2024-08-08T07:49:27Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000000000000318dd8ec152a49c221d14d                                                                                    23f035e3e17935111cda19c25d6a, bad-fork-prior-to-checkpoint
2024-08-08T08:12:04Z ERROR: ContextualCheckBlockHeader: forked chain older than last checkpoint (height 1874881)
2024-08-08T08:12:04Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000000000000318dd8ec152a49c221d14d                                                                                    23f035e3e17935111cda19c25d6a, bad-fork-prior-to-checkpoint
2024-08-08T10:23:34Z ERROR: ContextualCheckBlockHeader: forked chain older than last checkpoint (height 1874881)
2024-08-08T10:23:34Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 00000000000000318dd8ec152a49c221d14d

2024-08-06T11:25:03Z WARNING: option -rpcallowip was specified without -rpcbind; this doesn't usually make sense

I am already running on 21.0.2
Click to expand...
You need to update to v21.1.0 (hotfix) ASAP !! 53.7% of masternode & evonodes already updated to v21.1.0
Wait too long and you will be PoSe scored and ultimately PoSe banned.

I will check on Discord if those errors are a problem or not.
 
qwizzie said:
you need to update to v21.1.0 (hotfix) ASAP !! 53.7% of masternode & evonodes already updated to v21.1 wait to long and you will be PoSe scored and ultimately PoSe banned.

I will check on Discord if those errors are a problem or not.
Click to expand...
Aha I overlooked version, OK I just updated to v21.1. Thanks for help
 
nothing changed got pose banned again. I am thinking to build it again from scratch. What is recommended to bu used? I used masternod zeus, but but I also noted tehre is new ver of dashman.
 
coinjohn said:
nothing changed got pose banned again. I am thinking to build it again from scratch. What is recommended to bu used? I used masternod zeus, but but I also noted tehre is new ver of dashman.
Click to expand...
Dashmate is being recommended in Dash Discord.
 
@coinjohn

dashman has been superceded by dashmate. So dashman is a no go.

When going with Dashmate for setting up a regular 1K masternode :

curl -fsSL https://get.docker.com -o get-docker.sh && sh ./get-docker.sh
sudo usermod -aG docker $USER
newgrp docker

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
source ~/.bashrc
nvm install 20

npm install -g dashmate
dashmate setup (select mainnet, select masternode 1000 dash, yes to masternode already registered, no to importing data from existing blockchain data)
dashmate start

wait 20 minutes

set PUTTY to full screen / maximize, to avoid misalignment of on-screen output from below commands
dashmate status
dashmate status masternode

Since you are downloading from scratch check from time to time with above dashmate status commands how you are progressing with your dashmate start proces. Downloading and syncing from scratch to 100% can take up to 5 hours, maybe even longer.

After it is fully synced (100%) your masternode is most likely in PoSe ban status and need a DMT (Dash Masternode Tool) Update Service + 1 transaction confirmation). dashmate status masternode will tell you if your masternode is fine or if it is indeed in PoSe ban status.
At this point you can remove any cronjob (crontab -e) and remove the blockchain of Masternode Zeus.

To update dashmate in the future, due to a new Core version :

dashmate stop
npm install -g dashmate
dashmate update
dashmate start

Usefull commands to know :

docker stats --no-stream (show you some nice metrics about your Core docker container)
dashmate status host (show you some basic info about your masternode hardware)
dashmate status services (i suspect this give you some info about running Core services)
dashmate core reindex (in case you need a reindex through dashmate, hopefully you will never need it)
 
Last edited:
You must log in or register to reply here.
Back
Top