Topic: Darknet DNET Masternode VPS support MP-Hosting now taking DNET as payment. - page 8. (Read 18874 times)

No probs. I think it's understandable this time around as we are all trying to ensure this fork is a success.
But unless we have another hard fork to synchronize, it's probably better to let the users do it next time?

Anyways, really appreciate your work on helping DNET.

Hi
I will be mass updating the servers today
Sorry I'm not able to pick out some nodes all must done at the same time

Thanks
Paul

Hi Paul, are you going to mass update to 2.1.0.0 that was just released?

I think I prefer to update them on my own as I can update them when I'm ready.
In fact, I've just upgraded all of my MN's to v2.1.0.0 already. Now syncing.

Maybe your script can check for a certain file and if exists, it skips the mass upgrade? (such as .ignore)

Hi Guys
im mass updating my servers
ALL MP-Hosting servers  will be updating now
you don't need to update your MN's im doing it all for you




thanks
Paul

Hi
fine all done
i can now update any of the servers wne every we need to now

thanks
Paul

hows the script going?

Hi Guys

just so that you know im doing a test mass update of Canada 4
this will affect the folloing ip ranges


149.56.184.*
149.56.165.*
142.4.193.*


thanks
Paul

Thanks Paul. I'm happy with the mass update to ensure every masternode you host is upgraded correctly the first time.

HI
it will to the very latest wallet v2.1.0.0
if you update your nodes  that up to you BUT they WILL get updated again
i need to do ALL the nodes on the servers 

thanks
Paul

I assume you mean you'll mass update to v2.1.0.0 wallet (once out) which rolls back to block 259200? (and not the test v.2.0.4.0 out right now)
Once you are ready, please let us know exactly when they will and/or do get updated as some might want to update sooner without delay. Thanks!

Hi Guys

just so that you  are aware  im will be doing a mass update of my servers  when i have been given the ok
from the Devs.  So don't be to eager  to update your masternodes  as  the WILL get updated in the mass update


thanks
Paul

cheers once #990726 is sorted can finally leave me computer alone for abit past couple of days trying get it all working been a pain.

Hi
ticket #762228
sorted out

looking at ticket #990726
now


thanks
Paul

ok i made some changes to the last script from pjcltd for the new update

the script will also remove all addnode lines and add the nodes from dev post to the config file and download the blockchain from dev post.
please read more here:
https://bitcointalksearch.org/topic/m.15885081

note: i was not able to download the chain from dropbox (see the dev post above) with wget so i uploaded the chain to my google drive.
you can change the wget lines if you don't trust my files

#!/bin/bash
echo "Stopping darknet"
./darknet-cli stop
echo "Removing old Version"
rm darknetd
rm darknet-cli
sleep 90
echo " Removing old blockchain data "
cd
cd .darknet
rm -R blocks   chainstate  db.log   fee_estimates.dat  mncache.dat   peers.dat mnpayments.dat debug.log budget.dat backups  darknetd.pid  database
sed -i.bak '/addnode/d' ~/.darknet/darknet.conf
echo 'addnode=72.49.184.206' >> ~/.darknet/darknet.conf
echo 'addnode=68.227.30.210' >> ~/.darknet/darknet.conf
echo 'addnode=74.118.192.18' >> ~/.darknet/darknet.conf
echo 'addnode=138.68.50.249' >> ~/.darknet/darknet.conf
echo 'addnode=173.245.157.244' >> ~/.darknet/darknet.conf
echo 'addnode=173.245.158.8' >> ~/.darknet/darknet.conf
echo 'addnode=coin-server.com' >> ~/.darknet/darknet.conf
echo 'addnode=24.119.187.242' >> ~/.darknet/darknet.conf
wget -O darknet.zip https://doc-0s-1k-docs.googleusercontent.com/docs/securesc/ha0ro937gcuc7l7deffksulhg5h7mbp1/kh7r01tkfoc67nqbr3orghq58nkn7v6h/1470909600000/11974072493119325818/*/0B_Egj11irGZyem5ld0VHSUo3Z00?e=download
unzip darknet.zip -d ~/.darknet
rm -R darknet.zip
cd
echo "Downloading new version"
wget https://github.com/Darknet-Crypto/Darknet/releases/download/v2.0.2.0/darknet-cli
wget https://github.com/Darknet-Crypto/Darknet/releases/download/v2.0.2.0/darknetd
echo "setting permissions"
chmod +x darknet*
echo "Starting Darket damon"
./darknetd
sleep 120
echo "Starting Masternode"
./darknet-cli getinfo
sleep 10
./darknet-cli masternode start
echo "all done "


happy updating

ticket #762228
and
ticket #990726

please

New v2.0.2.0 wallet is out. It bans older clients. Looks to finally have fixed it.
https://bitcointalksearch.org/topic/m.15885081

Update: Resyncing using dev's blockchain is working fine so far.

doesnt look like that update has fixed the probs they getting stuck again.

ticket #990726 as well.

Yes, I know, my controller wallet seems to have forked some minutes ago. 

theres some very strange things going on

On the other hand, Paul, I had received two payments, one confirmed and one conflicted, from my MN in V2000 when I have updated my controller wallet to v2010. Just for info.