jakiman
Legendary
Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
August 10, 2016, 04:25:26 AM |
|
Could someone post a similar command script to something that was posted before? (to upgrade each MN) For example: you can use that script, but instead change v1.1.0.0 to v2.0.0.0 Trying to update my MN VPS's via above script. But the files are not there for v2.0.1.0. I'm no guru when it comes to this stuff so not sure what the best method is now.
|
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
August 10, 2016, 04:37:21 AM |
|
Could someone post a similar command script to something that was posted before? (to upgrade each MN) For example: you can use that script, but instead change v1.1.0.0 to v2.0.0.0 Trying to update my MN VPS's via above script. But the files are not there for v2.0.1.0. I'm no guru when it comes to this stuff so not sure what the best method is now. fixed
|
|
|
|
bathrobehero
Legendary
Offline
Activity: 2002
Merit: 1051
ICO? Not even once.
|
|
August 10, 2016, 05:06:53 AM |
|
Still stuck at 259200 after a fresh resync.
End of debug.log is not helpful either:
UpdateTip: new best=0000000000b469fb33c2e0911409d6c06183c13e6dd88ac5d827d39ecf3e1b4a height=259200 log2_work=55.779852 tx=367155 date=2016-08-07 21:04:10 progress=0.990812 cache=106818 2016-08-10 04:54:53 ProcessNewBlock : ACCEPTED socket recv error An existing connection was forcibly closed by the remote host. (10054)
but I still have connections.
Can someone maybe share a blockchain that is beyond 259200?
|
Not your keys, not your coins!
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
August 10, 2016, 05:32:28 AM |
|
Ok, so... there are a lot of different block heights going around, so here is what we need you to do. Only do this from the v2.0.1.0 wallet. first, from your wallet console, type this 'getblockhash 259880' (Without the tick marks) If your hash matches this one [f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098] then no need to resync the chain. Please shut down your wallet, add these addnodes ONLY to your darknet.conf file. then delete your peers.dat file and restart your wallet addnode=72.49.184.206 addnode=68.227.30.210 addnode=74.118.192.18 addnode=68.227.23.166 addnode=138.68.50.249 addnode=173.245.157.244 addnode=173.245.158.8 addnode=coin-server.com If your blockhash for block 259880 is different, then download this copy of the blockchain and resync your wallet https://www.dropbox.com/s/2ernxp6aad3k9i0/darknet.zip?dl=0
|
|
|
|
StakeBox
|
|
August 10, 2016, 05:36:02 AM |
|
Anyone know when trex is planning on fixing their wallet?
We asked them to put it into maintenance until we get things squared away. We had to pay them hundreds of thousands of DNET the last time when they sent coins on the wrong chain. We don't want to do that again, as I am sure you can understand.
|
|
|
|
NotMyFarm
|
|
August 10, 2016, 05:38:09 AM |
|
Ok, so... there are a lot of different block heights going around, so here is what we need you to do. Only do this from the v2.0.1.0 wallet. first, from your wallet console, type this 'getblockhash 259880' (Without the tick marks) If your hash matches this one [f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098] then no need to resync the chain. Please shut down your wallet, add these addnodes ONLY to your darknet.conf file. then delete your peers.dat file and restart your wallet addnode=72.49.184.206 addnode=68.227.30.210 addnode=74.118.192.18 addnode=68.227.23.166 addnode=138.68.50.249 addnode=173.245.157.244 addnode=173.245.158.8 addnode=coin-server.com If your blockhash for block 259880 is different, then download this copy of the blockchain and resync your wallet https://www.dropbox.com/s/2ernxp6aad3k9i0/darknet.zip?dl=0tx for that all good here just updated wallet - flipped on and on right track/chain staking and How do i stake without unlocking the whole wallet ? somebody mentioned unlock for anonymising - how does that work ? command line console ?
|
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
August 10, 2016, 05:41:16 AM |
|
Ok, so... there are a lot of different block heights going around, so here is what we need you to do. Only do this from the v2.0.1.0 wallet. first, from your wallet console, type this 'getblockhash 259880' (Without the tick marks) If your hash matches this one [f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098] then no need to resync the chain. Please shut down your wallet, add these addnodes ONLY to your darknet.conf file. then delete your peers.dat file and restart your wallet addnode=72.49.184.206 addnode=68.227.30.210 addnode=74.118.192.18 addnode=68.227.23.166 addnode=138.68.50.249 addnode=173.245.157.244 addnode=173.245.158.8 addnode=coin-server.com If your blockhash for block 259880 is different, then download this copy of the blockchain and resync your wallet https://www.dropbox.com/s/2ernxp6aad3k9i0/darknet.zip?dl=0tx for that all good here just updated wallet - flipped on and on right track/chain staking and How do i stake without unlocking the whole wallet ? somebody mentioned unlock for anonymising - how does that work ? command line console ? Make sure you delete your peers.dat and only use those addnodes. we are trying to get everyone syncing with the known updated wallets, annot the other ones..
|
|
|
|
|
jakiman
Legendary
Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
August 10, 2016, 06:14:32 AM |
|
Make sure you delete your peers.dat and only use those addnodes. we are trying to get everyone syncing with the known updated wallets, annot the other ones.. I did all of that but the hash was still different. (deleted peers.dat, only added the nodes you listed etc) So I've deleted everything but 3 files and resyncing from scratch again to see if I can get the right hash.
|
|
|
|
mxnsch
|
|
August 10, 2016, 07:24:19 AM |
|
There is no point in writing a guide for a script at that level. It is meant to be used on a scale and work 99% automatically without input and any "schischi" as we say around here.
Run this script on a Ubuntu 16.04 vultr VPS and replace the masternode keys in the config files. There is nothing complicated to it, just give it a shot.
Can you explain how it works with multiple ips? How many ips does vultr give you? What spec would you need for it to work on however many vps you have running? Of course. Vultr gives you a free ipv6 subnet with every host and that gives a lot of addresses to play with: https://www.vultr.com/tools/subnet-calculator-ipv6/?ipv6_address=2001%3A19f0%3A6801%3A3a%3A%3A&prefix_length=64&display=long
|
██ ███ nope ██ ███
|
|
|
bathrobehero
Legendary
Offline
Activity: 2002
Merit: 1051
ICO? Not even once.
|
|
August 10, 2016, 07:25:15 AM |
|
Ok, so... there are a lot of different block heights going around, so here is what we need you to do. Only do this from the v2.0.1.0 wallet. first, from your wallet console, type this 'getblockhash 259880' (Without the tick marks) If your hash matches this one [f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098] then no need to resync the chain. Please shut down your wallet, add these addnodes ONLY to your darknet.conf file. then delete your peers.dat file and restart your wallet addnode=72.49.184.206 addnode=68.227.30.210 addnode=74.118.192.18 addnode=68.227.23.166 addnode=138.68.50.249 addnode=173.245.157.244 addnode=173.245.158.8 addnode=coin-server.com If your blockhash for block 259880 is different, then download this copy of the blockchain and resync your wallet https://www.dropbox.com/s/2ernxp6aad3k9i0/darknet.zip?dl=0Thanks, finally now I could get past 259200 But, I got stuck at 260029 for about 15 minutes and it only synced to 260049 after I restarted the wallet. It wasn't just a visual bug since debug.log was also silent about new blocks. Anyway, it's great progress.
|
Not your keys, not your coins!
|
|
|
kbhutto
Sr. Member
Offline
Activity: 1288
Merit: 250
PredX - AI-Powered Prediction Market
|
|
August 10, 2016, 07:47:55 AM |
|
Ok, so... there are a lot of different block heights going around, so here is what we need you to do. Only do this from the v2.0.1.0 wallet. first, from your wallet console, type this 'getblockhash 259880' (Without the tick marks) If your hash matches this one [f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098] then no need to resync the chain. Please shut down your wallet, add these addnodes ONLY to your darknet.conf file. then delete your peers.dat file and restart your wallet addnode=72.49.184.206 addnode=68.227.30.210 addnode=74.118.192.18 addnode=68.227.23.166 addnode=138.68.50.249 addnode=173.245.157.244 addnode=173.245.158.8 addnode=coin-server.com If your blockhash for block 259880 is different, then download this copy of the blockchain and resync your wallet https://www.dropbox.com/s/2ernxp6aad3k9i0/darknet.zip?dl=0Thanks, finally now I could get past 259200 But, I got stuck at 260029 for about 15 minutes and it only synced to 260049 after I restarted the wallet. It wasn't just a visual bug since debug.log was also silent about new blocks. Anyway, it's great progress. I am at 260021 with full sync.......are we all on same chain?
|
|
|
|
bathrobehero
Legendary
Offline
Activity: 2002
Merit: 1051
ICO? Not even once.
|
|
August 10, 2016, 07:56:34 AM |
|
Ok, so... there are a lot of different block heights going around, so here is what we need you to do. Only do this from the v2.0.1.0 wallet. first, from your wallet console, type this 'getblockhash 259880' (Without the tick marks) If your hash matches this one [f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098] then no need to resync the chain. Please shut down your wallet, add these addnodes ONLY to your darknet.conf file. then delete your peers.dat file and restart your wallet addnode=72.49.184.206 addnode=68.227.30.210 addnode=74.118.192.18 addnode=68.227.23.166 addnode=138.68.50.249 addnode=173.245.157.244 addnode=173.245.158.8 addnode=coin-server.com If your blockhash for block 259880 is different, then download this copy of the blockchain and resync your wallet https://www.dropbox.com/s/2ernxp6aad3k9i0/darknet.zip?dl=0Thanks, finally now I could get past 259200 But, I got stuck at 260029 for about 15 minutes and it only synced to 260049 after I restarted the wallet. It wasn't just a visual bug since debug.log was also silent about new blocks. Anyway, it's great progress. I am at 260021 with full sync.......are we all on same chain? Unlikely as I'm already at 260087 but now the block explorer doesn't work so I can't check if I'm on the same chain.
|
Not your keys, not your coins!
|
|
|
NotMyFarm
|
|
August 10, 2016, 07:57:23 AM Last edit: August 10, 2016, 08:19:29 AM by NotMyFarm |
|
260088 here
|
|
|
|
mxnsch
|
|
August 10, 2016, 08:21:07 AM Last edit: August 10, 2016, 08:31:39 AM by mxnsch |
|
Updated my script to fix some bugs and install the new DNET version. Get the updated script at: https://github.com/marsmensch/masternode-vps-setup/blob/master/dnet_vps.shroot@development:~# /usr/local/bin/darknetd --version Darknet Core Daemon version v2.0.1.0-db34f50
Installation is only three steps: 1) create a vultr node with Ubuntu 16.04 2.) wget and run script from github 3.) replace masternode keys Chain is still a little crowded because of the update though. If you have replaced the masternode keys and maybe some other tweaks, start all nodes via /usr/local/bin/restart_masternodes.sh . Use my vultr reflink or the one of DNET devs if it exists if you want to support the development of this script http://www.vultr.com/?ref=6903922
|
██ ███ nope ██ ███
|
|
|
mikegi
|
|
August 10, 2016, 08:50:46 AM |
|
Would also be good to which is the valid version of software to run...
Looking at github, there the latest tag v2.0.1.0 which is at 922f368 and master has some other changes and is at db34f50.
Updating 922f368..db34f50 Fast-forward src/kernel.cpp | 12 ++++++++---- src/kernel.h | 2 +- src/main.cpp | 2 +-
Which is correct? Should the changes in master be used "in production". Maybe a new tag should be made... and the version increased so we can be sure we are on the right version.
Anyway, it's nice to see that a decision has been made about which chain is valid and which peers we should use.
|
|
|
|
|
werwortmann
Member
Offline
Activity: 80
Merit: 10
|
|
August 10, 2016, 09:04:39 AM |
|
I re-synced with the specific addnodes. Everything seems to be staying synced now, but I am not staking. Been synced for a few hours now. What is the staking maturity time?
|
|
|
|
jakiman
Legendary
Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
August 10, 2016, 09:29:29 AM |
|
My controller wallet is on the right chain and now starting up my MNs also.
|
|
|
|
jakiman
Legendary
Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
August 10, 2016, 09:37:26 AM |
|
I re-synced with the specific addnodes. Everything seems to be staying synced now, but I am not staking. Been synced for a few hours now. What is the staking maturity time?
Is your wallet unlocked? Also, are you on the right chain? "getblockhash 259880" should return "f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098".
|
|
|
|
|