Update to 0.9.4.4 or 0.10.8.4 to prepare for the hardfork on May 25!
- Thread starter eduffield
- Start date
Updated to 10.8.6, all instantly working fine, numbers agree everywhere. :smile:
Well, I updated again and got two different lists. One has a count of 47, the other of 89. The one with 47 doesn't show my masternodes, the one with 87 shows both of my masternodes. Both lists have all node ip's with :1
Well, I stopped and restarted my remote as well as my local QT wallet and now they're showing things properly
Is there any way to check and see if my masternodes are being voted on, not necessarily winning? Or after a couple of days, will there be any way to see if my masternodes have won like we used to be able to see in the debug log?
Well, I stopped and restarted my remote as well as my local QT wallet and now they're showing things properly
Is there any way to check and see if my masternodes are being voted on, not necessarily winning? Or after a couple of days, will there be any way to see if my masternodes have won like we used to be able to see in the debug log?
Last edited by a moderator:
Its been an hour and a half since I updated successfully to 10.8.6, node count up to 91
But I cant see myself on the list! Am I being impatient?
EDIT, so I tried manually searching for mine, and couldnt find it and found something weird. I tired some random IP from the list to test the grep command was working, and on the server it flags IP as :0, while on local it shows :1
So I did a list on each, and there is a HUGE discrepancy. I'm guessing a lot of people are still updating etc, but even still, my local pick up everything as :1
And I still cant find myself!
Local list;
From remote
But I cant see myself on the list! Am I being impatient?
EDIT, so I tried manually searching for mine, and couldnt find it and found something weird. I tired some random IP from the list to test the grep command was working, and on the server it flags IP as :0, while on local it shows :1
So I did a list on each, and there is a HUGE discrepancy. I'm guessing a lot of people are still updating etc, but even still, my local pick up everything as :1
And I still cant find myself!
Local list;
From remote
Last edited by a moderator:
More or less... lots and lots of updates today, and masternodes only ping the network to be alive every 30mins, IIRC...
Propulsion
The buck stops here.
Shut off remote server for 10 minutes. Restarted both clients. My node is now appearing on Chaeplin's website.
*Just a note* I do not have anything in the config file on the remote except for daemon=1. rpc user and pass.
*Just a note* I do not have anything in the config file on the remote except for daemon=1. rpc user and pass.
how can that be? you need the nodes, externalip, genkey, masternode=1, tesnet=0 ... ??
But yeah, will do that, shut them off at EC2 Instance level, generate new public IP to see if that helps. I wonder if genkey is linked to external ip? ...
Last edited by a moderator:
Propulsion
The buck stops here.
Nodes are hardcoded in.
Testnet= 0 is not needed because default is mainnet.
masternode=1 is not needed on remote. (my experience)
The only thing I have in local config is
masternode=1 (1 means true, 0 means false)
masternodeprivkey=xxxxxxxxxxxxxxxxxxxxxxxxx
masternodeaddr=xxx.xxx.xxx:9999
In Remote Config I have
daemon=1
rpcuser=sdafjasd
rpcpassword=sadfljasdf (RPC is needed for daemon=1 flag)
Propulsion, do you think that having masternode=1 and masternodeprivkey=etc.... cause problems when on the remote wallet?
My nodes seem to come and go still, sometimes with =1 and other times with =0 I'm checking on an unrelated wallet. I did rebuild the peers.dat file and recently turned the remote servers off for 10 minutes. Right now everything is showing up well. Just wonder how long it will last!
My nodes seem to come and go still, sometimes with =1 and other times with =0 I'm checking on an unrelated wallet. I did rebuild the peers.dat file and recently turned the remote servers off for 10 minutes. Right now everything is showing up well. Just wonder how long it will last!
Propulsion
The buck stops here.
Well I think it's because of all the different daemon versions being simultaneously run at the same time. Once the 25th happens and more people are forced to update, the problem should fix itself.
EDIT: Once again though, my MN has removed itself from the list. Will just have to wait for the network to prune itself I'd imagine.
Last edited by a moderator:
I updated my two MN to 10.8.6 and everything seemed to be ok (same count everywhere, always flagged 1...), but a few minutes ago I checked at http://drk.poolhash.org/darksend.html and they were gone. I logged into them and everything seemed to be fine. Now they are back into the website count. Confused
Last edited by a moderator:
It does make sense as is is the local who calls up to wake up the node. I'll try that, see it today they show up.
By the way, I never ended up setting up Elastic IP I think. Do you think with remote/local setup this is really necessary? What about encrypting the remote (always empty) wallet?
Did like you said... still dont show in the list. Do I did count them and went from 42 -> 43 -> 44 as soon as I got the masternodes started. But they dont show up at all.
Getting real bummed, testnet went flawlessly, not I cant get mainet to show my IP's al at...
Last edited by a moderator:
Ok, status report so far.
have 2 VM with Ubuntu doing local wallets to amazon EC2. Re-read Evan's procedure, Minotaur's recommendation, and even tried Propulsion's way (though it does not seem correct dude!)
One is Singapore, the Other North Virginia,
All versions 10.8.6
- Stopped all daemons local / remote
- Went to config files and deleted all nodes I had from testnet etc except = 23.23.186.131
- flagged masternode = 0 and delete previous masternodeprivkey - saved conf
- ran darkcoind, then darkcoind masternode genkey (on each side, local / server)
- stopped daemons
- nano darkcoin.conf and added each brand new key to each it own (local and remote)
- flagged masternode=1 on each side local/remote
- saved conf file.
- deleted peers.dat on both sides as well.
- Started remote with only "darkcoind" ... masternode count = 43
- Started local, as usual darkcoind -masternodeaddr:xx.xx.xx.xx:9999
- unlock wallet
- darkcoind masternode start - successfull !! (remote count jumps to 44, but local reports 48)
I try - darkcoind masternode list | grep '77' - to find my MN, no show.
What the heck am I doing wrong ?!
Local sees 48 nodes, server (singapore) sees 44.
EDIT: Just restarted my other MN (north virginia) checking the procedures, both local and server count 49 active nodes - so I guess maybe that was me?... though I still cannot see myself on the list
have 2 VM with Ubuntu doing local wallets to amazon EC2. Re-read Evan's procedure, Minotaur's recommendation, and even tried Propulsion's way (though it does not seem correct dude!)
One is Singapore, the Other North Virginia,
All versions 10.8.6
- Stopped all daemons local / remote
- Went to config files and deleted all nodes I had from testnet etc except = 23.23.186.131
- flagged masternode = 0 and delete previous masternodeprivkey - saved conf
- ran darkcoind, then darkcoind masternode genkey (on each side, local / server)
- stopped daemons
- nano darkcoin.conf and added each brand new key to each it own (local and remote)
- flagged masternode=1 on each side local/remote
- saved conf file.
- deleted peers.dat on both sides as well.
- Started remote with only "darkcoind" ... masternode count = 43
- Started local, as usual darkcoind -masternodeaddr:xx.xx.xx.xx:9999
- unlock wallet
- darkcoind masternode start - successfull !! (remote count jumps to 44, but local reports 48)
I try - darkcoind masternode list | grep '77' - to find my MN, no show.
What the heck am I doing wrong ?!
Local sees 48 nodes, server (singapore) sees 44.
EDIT: Just restarted my other MN (north virginia) checking the procedures, both local and server count 49 active nodes - so I guess maybe that was me?... though I still cannot see myself on the list
Last edited by a moderator:
FWIW I followed pretty much the same steps as you and had the same result. I found that stopping and restarting my remote darkcoind again (after starting masternode from my local comp) got me on the list for both my remote and local machine. However after a good hour or so I'm still not showing on the list at http://drk.poolhash.org/masternode.html so maybe it still isn't working properly.
FYI... 2 hours later, local reports 52 and remote 57 MN's... mine still dont show up anywhere. I'll try your "workaround" jcarl1987, worth a shot.
I got two nodes, so did it only to one to see... stopped remote daemon, waited a few seconds, restarted. Still counts 57 and I cant see myself :sad:
Yeah, and I am checking everywhere! linux local, server, and mac QT 9.4.6 ... not even flagged as :0
I got two nodes, so did it only to one to see... stopped remote daemon, waited a few seconds, restarted. Still counts 57 and I cant see myself :sad:
Yeah, and I am checking everywhere! linux local, server, and mac QT 9.4.6 ... not even flagged as :0
Last edited by a moderator:
My test with remote/local with cold storage is that it just doesn't work with the new protocol. It activates for a time, then switch to "0" in the list and then disappears completely. I did the tests with 0.10.8.4, .5 and .6 same result. The setup was working fine (or so it seemed, the masternode was showing in the list and on the testnet I received payments) prior to 0.10.8.x.
