Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

POSE_BANNED: 100%

Discussion in 'Masternode Questions and Help.' started by Rodrigo Fernandez, Sep 2, 2019.

  1. Rodrigo Fernandez

    Rodrigo Fernandez New Member

    Joined:
    Jan 24, 2016
    Messages:
    13
    Likes Received:
    8
    Trophy Points:
    3
    Dash Address:
    XhaUJfb7kpmTpUXX5dzqPJiFU6xNDvZRKY
    I have set up a dash masternode with a hardware wallet, and it started working fine for a few days.
    Then I started getting this message from DashCentral monitoring and the masternode stopped working:

    Error: There is a problem with the status of your masternode on the masternode list:
    ENABLED: 0%
    POSE_BANNED: 100%

    How can I fix this issue?

    Thanks for all your help.
    Regards,

    Rodrigo
     
  2. qwizzie

    qwizzie Well-known Member

    Joined:
    Aug 6, 2014
    Messages:
    1,441
    Likes Received:
    698
    Trophy Points:
    183
    What to do with a PoSe Penalty score on your masternode ?

    Run "./dash-cli masternode status" on the masternode and it will tell you if your node is configured well
    If your masternode fails to provide service to the network in accordance with the current consensus rules, it will receive a Proof of Service Ban.
    If your masternode is in the POSE_BANNED status, you should check the following settings are configured correctly:
    Ensure you are running the latest version of Dash
    Ensure your masternode has sufficient memory, swap, processing power and hard drive space
    (use recommended specs : https://docs.dash.org/en/stable/masternodes/understanding.html#masternode-requirements)
    Ensure you are fully synced to the correct blockheight, and that you are on the correct chain and not forked off
    Ensure that a BLS private key is specified using the masternodeblsprivkey option in the masternode’s dash.conf file
    Ensure that the BLS private key on the masternode is unique on the network and not shared with any other masternodes
    Ensure that the BLS private key on the masternode corresponds to the BLS public key registered on the blockchain in the ProRegTx or ProUpRegTx
    Ensure that the externalip (and port if using testnet) are specified correctly and not blocked by a firewall or port forwarding service
    Ensure that Sentinel is installed, updated, not exiting with an error and is entered in your crontab to run every 1-2 minutes”
     
    • Like Like x 1
  3. Rodrigo Fernandez

    Rodrigo Fernandez New Member

    Joined:
    Jan 24, 2016
    Messages:
    13
    Likes Received:
    8
    Trophy Points:
    3
    Dash Address:
    XhaUJfb7kpmTpUXX5dzqPJiFU6xNDvZRKY
    Thanks for your extensive answer.
    I will follow as instructed
    Regards

    Rodrigo
     
  4. qwizzie

    qwizzie Well-known Member

    Joined:
    Aug 6, 2014
    Messages:
    1,441
    Likes Received:
    698
    Trophy Points:
    183
    Credits for that extensive answer goes to the Dash Core Developers (codablock i think ? i have difficulty remembering who it was exactly).
    I just saved it in a text file, so i could use it in a situation like this.

    Good luck.
     
    #4 qwizzie, Sep 3, 2019
    Last edited: Sep 3, 2019
  5. europound

    europound Member

    Joined:
    Oct 22, 2016
    Messages:
    113
    Likes Received:
    1
    Trophy Points:
    68
    same problem here
    this update is bad
    all prev updates were flawless

    what exactly is not good enough ?
    where is the log?
     
    #5 europound, Sep 6, 2019
    Last edited: Sep 6, 2019
  6. splawik21

    splawik21 Grizzled Member
    Dash Core Team Foundation Member Dash Support Group

    Joined:
    Apr 8, 2014
    Messages:
    1,902
    Likes Received:
    1,277
    Trophy Points:
    1,283

Share This Page