Masternode ninja fatality!

hookbot

hookbot

New member
I'm using dashman ( https://github.com/moocowmoo/dashman )

Here is my output from dashman status:

host uptime/load average : 41 days, 0.63 0.43 0.38
dashd bind ip address : 204.44.93.5
dashd version : 0.12.2.1
dashd up-to-date : YES
dashd running : YES
dashd uptime : 3 days, 20 hours, 10 mins, 25 secs
dashd responding (rpc) : YES
dashd listening (ip) : YES
dashd connecting (peers) : YES
dashd port open : YES
dashd connection count : 26
dashd blocks synced : YES
last block (local dashd) : 789374
(chainz) : 789374
(dash.org) : 789374
(dashwhale) : 789372
(masternode.me) : 789372 - no forks detected
dashd current difficulty : 73540982.20315154
masternode started : YES
masternode visible (local) : YES
masternode visible (ninja) : NO
masternode address :
masternode funding txn : -
masternode queue/count : 4301/4630
masternode mnsync state : MASTERNODE_SYNC_FINISHED
masternode network state : ENABLED
masternode last payment : never
masternode balance : 0
sentinel installed : YES
sentinel tests passed : YES
sentinel crontab enabled : YES
sentinel online : YES
Exiting.

When I run "dashman vote" it just throws this horrible error:

"cannot retrieve masternode info from dashninja"

Why isn't my masternode in the dashninja?
And why doesn't my "masternode address" and my "masternode funding txn" appear correctly?
I'm pretty sure I've already clicked START over 20 times in my Dash Core client.

How can it say "masternode network state : ENABLED" but it refuses to show my "funding txn" properly?

I have my Dash Core configured perfectly to use this txn: "0a7f6912c0d6fef5896e9261f0f201a9a80f6d8d20a5230c3808c8c8dd37e84f-1" and it even shows "ENABLED" in my Dash Core client.

How many more weeks do I have to wait until the ninja system is finally working better?

Or what am I doing wrong?

Do I have to start over AGAIN?
 
My Dash Core client is showing my masternode is "ENABLED". So am I safe to just ignore all the horrible scary output coming from "dashman status"? But that still doesn't explain why my masternode isn't showing on the dashninja.pl list. Have I been blacklisted or something? Or what is so special about this masternode?

One of my masternodes is showing fine:

https://www.dashninja.pl/mndetails.html?mnpubkey=XnRArArksQMJTE57notCyJi2z3RcJEcjDH

But this one pretending like there is a problem:

https://www.dashninja.pl/mndetails.html?mnpubkey=XrcxRCXo9GJjby9PzSFKrR4aH5hLacKM9a

Yet both masternodes are configured exactly the same.

I don't want to keep restarting my masternode, since I always go to the end of the queue, and it never helps anyways. WHY does this have to be so hard? Any other ideas?
 
hookbot said:
My Dash Core client is showing my masternode is "ENABLED". So am I safe to just ignore all the horrible scary output coming from "dashman status"? But that still doesn't explain why my masternode isn't showing on the dashninja.pl list. Have I been blacklisted or something? Or what is so special about this masternode?

One of my masternodes is showing fine:

https://www.dashninja.pl/mndetails.html?mnpubkey=XnRArArksQMJTE57notCyJi2z3RcJEcjDH

But this one pretending like there is a problem:

https://www.dashninja.pl/mndetails.html?mnpubkey=XrcxRCXo9GJjby9PzSFKrR4aH5hLacKM9a

Yet both masternodes are configured exactly the same.

I don't want to keep restarting my masternode, since I always go to the end of the queue, and it never helps anyways. WHY does this have to be so hard? Any other ideas?
Click to expand...

Your masternode with a public key of XrcxRCXo9GJjby9PzSFKrR4aH5hLacKM9a no longer has 1,000 Dash. https://dash-insight.node40.com/insight/address/XrcxRCXo9GJjby9PzSFKrR4aH5hLacKM9a
 
orangecycle said:
Your masternode with a public key of XrcxRCXo9GJjby9PzSFKrR4aH5hLacKM9a no longer has 1,000 Dash. https://dash-insight.node40.com/insight/address/XrcxRCXo9GJjby9PzSFKrR4aH5hLacKM9a
Click to expand...

Oh! You are absolutely correct! How embarrassing that I pasted my OLD masternode address. I was having SO MUCH trouble with that old one so I moved the funds to a new address:

https://www.dashninja.pl/mndetails.html?mnpubkey=XrcxRCXQ9V8TJ4mAefCSS5gYXpRHBDxWpi

Notice it has enough funds:

https://dash-insight.node40.com/insight/address/XrcxRCXQ9V8TJ4mAefCSS5gYXpRHBDxWpi

The funding txn "0a7f6912c0d6fef5896e9261f0f201a9a80f6d8d20a5230c3808c8c8dd37e84f 1" that I mentioned which it's pinned to within my Dash Core is exactly perfect.

So the question is, why is the ninja not seeing it as valid when everything is so perfect?
 
Currently, ninja seems to have an issue detecting newly created masternodes. The total number is way too low. I started a perfectly running masternode 3 days ago and it is still not recognized there.Not a reliable source ATM.
 
Same here - I moved to a new address and even after 6 days it hasn't appeared in ninja...
 
Well, I guess if ninja is so choking busted that it can't detect new masternodes anymore, then THAT would explain all the problems I've been seeing over the past week.

#1. My Dash Core client shows my masternode is "enabled"

#2. My "dashman status" is also reporting it as "ENABLED"

#3. But "dashman status" does not even show the address or txn. THAT is the big confusing part for me. I haven't looked at the dashman code, but maybe it completely relies on the www.dashninja.pl website instead of just running "dash-cli masternode status" to obtain it, which would exactly explain this bizarre output I'm seeing. I'll try to send another pull request to moocowmoo to provide a patch to repair this horrible flaw.

Wow! What a HORRIBLE timing to have this problems with dashninja right exactly as I'm trying to configure my new masternode. I mean, I just barely got one masternode setup end of November and it actually showed up in ninja. So I thought I knew how to do it by now. But then because I didn't see this new masternode on ninja, I naively clicked the [START ALL] button in my Dash Core client. I thought it would help to keep restarting all of them, but instead I just made it WORSE!

So I'm guessing I just bumped up everyone in the queue so all the other masternodes can get their payment a few minutes sooner now thanks to me.

Merry Christmas to everyone from ME. :-D

So I guess I just lost all those Dash to help pay for my tuition to learn how this stuff works.

Also, do you happen to know the webmasters for dashninja.pl? It might be a good idea to let them know about this issue, in case they are just not aware. I have no idea how to do that or I'd do it myself.

I think with a little more work, this Dash can really do well in the future.

Thank you all for all your clarifications!
 
UdjinM6 said:
Pinging @elbereth - the ninja man :rolleyes:
Click to expand...

Okay, it appears that the dashninja.pl website is finally working again. The Ninja even detects all my new masternodes properly again here:

https://www.dashninja.pl/masternodes.html

And dashman is finally showing all green for the first time in weeks.

masternode started : YES
masternode visible (local) : YES
masternode visible (ninja) : YES <=================
masternode address : XrcxRCXo9GJjby9PzSFKrR4aH5hLacKM9a
masternode funding txn : 0610521429dda555247f11b7410271f62e3066d77bd2814cbed0e34b39fdbbf7-4
masternode queue/count : 2664/4655
masternode mnsync state : MASTERNODE_SYNC_FINISHED
masternode network state : ENABLED
masternode last payment : never
masternode balance : 1000.000000000
sentinel installed : YES
sentinel tests passed : YES
sentinel crontab enabled : YES
sentinel online : YES


Thank you Mr Ninja Man!!
 
You must log in or register to reply here.
Back
Top