Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 336. (Read 782375 times)

Thanks for this check list, its very handy.  Everything on it checks out and no MN payments are showing on the blockchain.  When I got back from my weekend away on Tuesday I opened the wallet and received a bunch of payouts for the nodes I have.  I started an Obfuscation with 500 DNET and a short while later discovered that my nodes swap files ran over 312% (they have been generously increased).  I think this caused a block chain error so I deleted all the necessary files and did a -rescan on all of them activating when synced (which was surprisingly fast), they have been up ever since with only 1 payment on MN1 in roughly 70 hours.  

I really need to work out if this is a problem at my end or there is just a really long delay.  I have a few friends that are considering investing in a few nodes and I want to show them it running smoothly and need to know the delay from activation so they can calculate ROI with a few restarts a month included.  I personally came here as a geek who loves playing with technology rather than an investor, in the time I have been here I have started to realise that DNET might actually be a good long term investment and have sparked a lot of interest because it is a genuinely interesting project with a solid dev team and awesome community.  A mixture of crypto enthusiasts, server admins and non technical people looking to get into crypto are interested.  I mentioned some of the more ambitious in-wallet plans to some coders and their eyes lit up.  I have even been speaking to non technical friends who are interested in me setting up and managing nodes for a cut of the MN payments and a small setup fee.

I need to get things running smoothly for myself for at least a few weeks/month before I start bringing people in.  All of the people I have spoken to have skills that the community could benefit from coders, artists, designers, web developers, writers, event managers etc so I would like them to have the best possible experience.

EDIT:  Took a while but MN payments are coming in. 

Thank you very much for this clear reply s3v3nh4cks! I didn't knew that .


hehehe, I agree totally.

955 Masternodes!!! Soon 1000 .

any news on the next release? this version blagging me head cant get it to work

its saying permission denied on debug and with

 /usr/local/bin/darknet-cli -rpcuser=drknetrpc -rpcpassword=xxxxx -rpcport=4441 getinfo

error: incorrect rpcuser or rpcpassword (authorization failed)

defo the right user and pass as well

this is fresh install as well

If something up with the masternode voting?

$ darknet-cli  mnbudget show
{
}


While here I see 2 budgets...

http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

Here are most of the key checks that can be done:
0. Check "masternode list-conf" from controller wallet. Ensure the status says Enabled.
1. Check "masternode list-conf" from controller wallet. Ensure the IP address matches up with yout masternode's IP address.
2. Check "masternode status" from masternode wallet. Ensure it says "Masternode successfully started".
3. Check "masternode status" from masternode wallet. Ensure the IP address is matches up to the one in your controller wallet's masternode.conf for that MN instance
4. Check "masternode status" from masternode wallet. Ensure TXID matches the one in your controller wallet's masternode.conf TXID for that MN instance.
5. Check "masternode status" from masternode wallet. Ensure Pubkey matches the correspnding receiving address with the 10K DNET for that MN instance.
6. Check masternode's darknet.conf file. Ensure the privkey in the darknet.conf file matches the one in the masternode.conf of the controller wallet for that MN instance.
7. Although I assume it is, the privkey mentioned above needs to be the one generated via "masternode genkey" from your controller wallet.
8. Check "masternode list" output from both your masternode & controller. Just confirm that the last TXID matches up to ensure they are same.
9. Check "masternode list" output from both your controller. Either find (or grep) the output and see if your masternode's TXID is listed.

Still nothing, its coming upto 72 hours.    2 days, 22 hours, 50 minutes.  Everything seems ok, just no payments.  Are there any other checks I can do to be sure?

Check the /var/lib/masternodes/darknet$/debug.log to see why it's not starting. (where $ is the instance number)
Mine was due to the script failing to create the IPv6 addresses. So my wallet's couldn't bind to the IPv6 addresses.
I ended up destroying the server, deployed a new one, re-ran the script and all worked the second time around.

still struggling with this vultr ipv6 setup. It does not auto start the nodes when reboot and are not running. i did run the script at the end of setup.

if i use the rpc command it does says it is not running and cannot connect.

before i restarted even tho the password and user were the same 3 of them were saying it was incorrect.

 

Ah. So that was you.

Going by what the devs said (with confidence) on slack just few days ago, I'm also excited about their upcoming untraceable transaction technology.

No ETA of course. Let's just hope it's sooner than later but also hope its very robust and innovative.

Announcement: due to the rapid increase in interest all across anonymous blockchain technologies I decided to up my stake considerably ,a buy order was issued for approximately 200K Dnet , coins will be parceled to master nodes

Dnet is one of few of these coins that remained a bargain it also sports strong and dedicated development team

Ah. If you have restarted the masternodes, then you mave have gone back to the back of the queue if it did expire and got removed.

Everything matches up.  I am probably being impatient.  I did read somewhere that DASH masternodes have a queuing system and in all fairness I was away for the weekend and my swap went over causing a chain corruption so I had to re sync them all and I guess i'd be way back of the queue.  I'll check again in the morning.

If you only just started them in the past 48 hours, they should start to trickle in soon. (as we have over 950 MN's now, it would take around 48 hours to start receiving first payment) If you suddenly stopped receiving payments in the past 48 hours, then that's weird. Just make sure the private key for each MN matches between your masternode.conf and on the MN's darknet.conf. Also, ensure the TXID matches between the MN wallet (masternode status) and on your controller wallet (masternode list-conf) outputs etc. As you said, if your txid is listed in the masternode list, and if your MN and controller wallets are on the correct chain, it should be good. (check getblockhash against this web site http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html)

No. It doesn't matter much really. If you have rpcallowip to 127.0.0.1, the only way an unwanted person can fire commands at your MN wallet is from the server itself that it's running on. So unless this someone can login to your server direct, they can't fire remote commands to your wallet from the outside even if they know (or can guess) your rpc username & password.

I haven't received any MN payments in over 48 hours despite them all showing up in the masternode list as enabled, all on the correct chain and synced inc controller wallet.  I tried to check the block explorers to see if they were just not getting to the wallet for some reason but they are both down so I can't.

Does anyone have any ideas why I am not getting payments after over 48 hours? or if there is something blocking payments to my wallet?

EDIT:  Tell a lie MN1 paid 29.25 yesterday but nothing else since on any of the nodes.

Does it matter they all the same user and pass?

If your rpcallowip is the loopback address, then the username/password doesn't really matter much
Script by mxnsch creates all the instances with same username & password. Just different rpc port.

So to fire CLI commands at each instance from the server's console, it's as easy as:

/usr/local/bin/darknet-cli -rpcuser=xxxx -rpcpassword=yyyy -rpcport=zzzz getinfo

(where zzzz is the rpcport of each instance. e.g. 4441, 4442, 4443, 4444, 4445)

Remembering all the user names and passwords bit of a pain and don't like saving them. I try to make them unique and not the same as well. Does it matter?

You could run ./darknet-cli -rpcconnect=IPNUMPER  -rpcuser=masternodeusername -rpcpassword=yoursecurepassword getinfo

I assume you are running this from within your masternode's server...

You might need to set "rpcallowip=" to allow you to connect from wherever you are trying to connect to.
It's prudent to set rpcallowip to  only  allow internal connections. (best to firewall all unnecessary ports).
RPC could be used over ssl, but I suppose this could be used to generate extra load on the server if left open,
and worse is possible if you use easily guessable usernames and passwords.