I just updated my masternodes... given that this one is a bit more complicated because the the blockchain needs to be resynced and some database files need to be deleted I made some notes to speed up the process for myself, the someone here surely will find them helpful.
Read through everything before starting to copy paste... this works for me, your setup may differ.
Build the latest version ... I assume you already have an old version in git
Your configuration options or paths may differ.
Probably also a good time to
and
and
so I haven't mentioned stopping your currently running masternode daemons.
$ cd git/Darknet/
$ ./autogen.sh
$ ./configure
$ make clean
$ make -j4
$ cd src/
$ tar zcvf ~/dnet.tar.gz darknet-tx darknet-cli darknetd
Copy the
to the machine(s) running your masternode(s) and unpack it over your current executables
Preparation... on a working node running the latest dnet (you need to at least delete some files in the .darknet dir ... and start a dnet nodes with the latest version) Stop the node before tarring!!
$ darknet-cli stop
$ tar zcvf dnet_base70200.tar.gz .darknet/blocks/ .darknet/peers.dat .darknet/chainstate/ .darknet/budget.dat .darknet/mncache.dat
copy this file to each machine that has masternodes to be updated:
Updating a masternode:
$ cd .darknet
$ rm -r fee_estimates.dat mncache.dat mnpayments.dat budget.dat chainstate blocks peers.dat
$ cd ..
$ tar zxvf /tmp/dnet_base70200.tar.gz
$ darknetd
$ watch darknet-cli masternode status
When your masternode is waiting for activation run the following on the masternode controller...
$ darknet-cli masternode start-alias abc123
Check that your masternode is
"status" : "Masternode successfully started"
and move on to the next one...
If you found this helpful and you are so inclined, a small gift to this address will go towards my next masternode or beer (in which case it will be traded to BTC which will be used to pay for beer.)
D8zVCiBSRehy2xR4tfaapjz75BYAyg2tAH