Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

No Masternode Payment after 15 days...is that normal?

Discussion in 'Masternode Questions and Help.' started by soybruce, Mar 16, 2017.

  1. soybruce

    soybruce New Member

    Joined:
    Mar 13, 2017
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Here is a recent output of dashman status:

    hostname : masternode01
    host uptime/load average : 7 days, 0.09 0.06 0.07
    dashd bind ip address : removed
    dashd version : 0.12.1.3
    dashd up-to-date : YES
    dashd running : YES
    dashd uptime : 2 days, 19 hours, 29 mins, 27 secs
    dashd responding (rpc) : YES
    dashd listening (ip) : YES
    dashd connecting (peers) : YES
    dashd port open : YES
    dashd connection count : 20
    dashd blocks synced : YES
    last block (local dashd) : 637018
    (chainz) : 637018
    (dash.org) : 637018
    (dashwhale) : 637018
    (masternode.me) : 637018 - no forks detected
    dashd current difficulty : 86234.34916173074
    masternode started : YES
    masternode visible (local) : YES
    masternode visible (ninja) : YES
    masternode address : addr removed
    masternode funding txn : txn-id removed
    masternode queue/count : 3660/4009
    masternode mnsync state : MASTERNODE_SYNC_FINISHED
    masternode network state : ENABLED
    masternode last payment : 1.94231 in 628873 on 02/28/2017 21:35:25 (15 days, 4 hours ago)
    masternode balance : 1000.009633020

    The Masternode shows as Enabled in my wallet. Everything is green on the screen. Is there anything other debug output I can look at to see why my node is not getting paid?
     
    #1 soybruce, Mar 16, 2017
    Last edited by a moderator: Mar 16, 2017
  2. jimbit

    jimbit Well-known Member
    Foundation Member

    Joined:
    May 23, 2014
    Messages:
    226
    Likes Received:
    103
    Trophy Points:
    203
    you active duration is: 1d1h8m34s

    did you do a start-alias from your local?

    I also have one that has not been paid for a couple weeks.. but that is because of my issues.. I upgraded, but did not install sentinal right away.. then the ddos took me offline and restarted the active duration again
     
  3. soybruce

    soybruce New Member

    Joined:
    Mar 13, 2017
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    After not getting paid for 12+ days I restarted dashd to see if that would change anything. I did not need to run start-alias as it was showing as Enabled.
     
  4. UdjinM6

    UdjinM6 Official Dash Dev
    Dash Core Team Moderator

    Joined:
    May 20, 2014
    Messages:
    3,637
    Likes Received:
    3,536
    Trophy Points:
    1,183
    There is smth/someone spawning new "start" command:
    Code:
    2017-03-08 08:55:18 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=<your IP>
    2017-03-15 00:55:23 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=<your IP>
    
    How do you have you masternode configured exactly? Can you remember what did you do to masternode/wallet on these dates/times?
     
  5. soybruce

    soybruce New Member

    Joined:
    Mar 13, 2017
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    It's now been 21 days. I've never seen the masternode queue/count (3783/4096) ever reset or even decrease during the 21 days even though I did restart dashd and the entire node.

    > How do you have you masternode configured exactly?
    dashd is running on Linux/Ubuntu 16.10 and is running as a non-root user under the default .dashcore directory. sentinel is installed and running as a crontab ever minute. I also have the dashcentral-updater running every two minutes. UFW is running and allowing ssh and dash traffic on port 9999.

    Dash Ninja shows an Active Duration of 1 week 1 hour 39 minutes 34 seconds.

    I do get sporadic alerts from dashcentral but they seem to be noise as the last recorded "Incident" on dashcentral is from 2/25 and lasted one minute. That incident happened prior to the last payment, so I don't think it is meaningful for this discussion.

    Is it normal that a masternode goes this long without payment?

    Is there any documentation on messages in the debug log. I've tried filtering through it, but I don't know what is a good and a bad log entry. I'm happy to run some commands and post the output here.



    dashman version 0.1.23 (2-g7e642f1) - Tue Mar 21 17:30:17 PDT 2017
    gathering info, please wait... DONE!

    hostname : masternode01
    host uptime/load average : 4 days, 0.23 0.12 0.10
    dashd bind ip address : removed
    dashd version : 0.12.1.3
    dashd up-to-date : YES
    dashd running : YES
    dashd uptime : 4 days, 18 hours, 59 mins, 06 secs
    dashd responding (rpc) : YES
    dashd listening (ip) : YES
    dashd connecting (peers) : YES
    dashd port open : YES
    dashd connection count : 27
    dashd blocks synced : YES
    last block (local dashd) : 640277
    (chainz) : 640277
    (dash.org) : 640277
    (dashwhale) : 640277
    (masternode.me) : 640277 - no forks detected
    dashd current difficulty : 118391.8670231827
    masternode started : YES
    masternode visible (local) : YES
    masternode visible (ninja) : YES
    masternode address : removed
    masternode funding txn : removed
    masternode queue/count : 3783/4096
    masternode mnsync state : MASTERNODE_SYNC_FINISHED
    masternode network state : ENABLED
    masternode last payment : 1.94231 in 628873 on 02/28/2017 21:35:25 (21 days, 2 hours ago)
    masternode balance : 1000.009633020