Jump to content
Sign in to follow this  
J3ll3

Manual upgrade of a Masternode to v1.1.0.0

Recommended Posts

INSTRUCTIONS

This guide is for those that want to do a manual update of their masternode running on a VPS.

People that should not use this guide
Please do not use this guide if you have your masternode with any of our masternode hosting providers as listed below. Those masternodes will be updated by your hosting service. You might have to start the masternode after they announce that they have completed the update:

  • Stakinglab.io
  • CryptoHashTank
  • Nodehub.io
  • GTM
  • Snode
  • Maiks masternode hosting service
  • BitHostLive
  • Pecunia
  • MIDAS
  • Apollon 

Detailed manual upgrade instructions

This guide tells you in detail, which steps you should follow for updating your masternode running on a VPS. Alternatives are creating a new VPS and installing the masternode from scratch or rerunning the install script on an existing masternode. Remember to disable the masternode first using this command:

systemctl stop PAWS

Now... over to the instructions for a manual update:

  1. Login to the VPS using putty or any other ssh program that you normally use as described in the installation guide.
     
  2. You should now have a window with a black screen like the one shown below:

    stepc6-mnguide.png.33ef46afa262e6e34d1a6520f30003e8.png
     
  3. The first thing you do, is stop the masternode service running.

    systemctl stop PAWS

  4. Wait like 10 seconds for the masternode service to shutdown properly. Now, change into the data directory, as we have to remove some files to make sure the upgraded PAWS wallet can be activated without a problem once we have upgraded. We need to remove the old blockchain and we do that as follows:

    cd .paws
    rm -rf blocks
    rm -rf chainstate
    rm mncache.dat
    rm peers.dat
    cd


    Make sure you add the lines one by one. I have had people experiencing problems cut/paste from this page... so if you experience problems, please type the above in by hand.

  5. The next thing we do is download the new software:

    wget https://github.com/pawsfund/PAWS-Core/releases/download/v1.1.0.0/paws-1.1.0.0-x86_64-linux-gnu.zip

    This should output some lines, that indicate the file is being downloaded.
  6. Once the prompt returns, we need to unzip the archive we just downloaded. Do the following:

    unzip paws-1.1.0.0-x86_64-linux-gnu.zip
     
  7. You should now have 3 more files in your home directory. Please do the following to make them executable:

    chmod +x paws*
     
  8. The files now need copying over the existing executables in /usr/local/bin. We do that as follows:

    mv paws-cli /usr/local/bin
    mv pawsd /usr/local/bin
    mv paws-tx /usr/local/bin

     
  9. We are now ready to start the masternode service for the first time:

    systemctl start PAWS
     
  10. We now need to wait and sit back. Repeat the following command with 1-2 minutes interval, or simply go for a coffee and check when you get back. The wallet is synchronising and the blockcount has to go up until it reaches the current block count. The current block count can be seen on the explorer in the top left corner as shown below.

    305291596_Screenshot2019-01-27at12_46_23.thumb.png.6f9125ff8a165b6bcf146d61c35abb0f.png
     
  11. Once you confirmed that the blockheight is the same as on the explorer, you are ready to proceed with the final step. We need to restart the masternode shortly and the best results I have achieved by doing it as follows:

    paws-cli stop

    What happens here, is that we stop the wallet via the commandline, but since the wallet is running as a service the service will start it again once it detects it is shutdown. So this really means that the wallet is stopped, and started immediately after.

  12. You now have to open your local wallet and start the masternode, just like you did with your first installed the masternode. Chances are that it says it is enabled already, and this is because the wallet is really slow to detect that a masternode has going offline.This is a good thing, as it might prevent you from having to wait the initial 18 hours before getting your first reward.

    So open the local wallet, and start the masternode by selecting it and clicking "Start Alias".
     

  13. The final step is to check if the masternode has started. On the masternode (VPS) type the following command:

    paws-cli getmasternodestatus

    It should return something like:

    {
        "txhash" : "f1355f7864ff97f395b5b51a10ec5ckpe82b0f2c6170b6956ee81f264137821b",
        "outputidx" : 0,
        "netaddr" : "1.1.1.1:34120",
        "addr" : "PPUg6iQtMrHjhaYqxYrtFaxMjmcqLzC7pt",
        "status" : 4,
        "message" : "Masternode successfully started"
    }
    


    Status 4 means you are good to go.

Any problems let us know here on the forum or on Discord.

The PAWS Team

 

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.