Crown Forum

Author Topic: [LEGACY] Updating Nodes to v0.12.4.1  (Read 2650 times)

EdwardMorra

  • Administrator
  • Full Member
  • *****
  • Posts: 31
  • Karma: +2/-0
  • One day at a time, every day
    • View Profile
[LEGACY] Updating Nodes to v0.12.4.1
« on: March 12, 2018, 12:54:28 pm »
Crown Master/Systemnode Update Guide

Firstly, make sure your local wallet is on the latest version (find it at https://crown.tech/wallet).

All managed hosting providers will auto update (Node-VPS, NodeSupply and Crown-VPS). You may need to restart the nodes from your local wallet, we recommend you keep an eye on your nodes.

If you have access to your nodes' terminal then it is not managed and you need to do the following.

Copy and paste the following script into your terminal (through PuTTy or otherwise).
Code: [Select]
sudo apt-get install curl -y && curl -s https://raw.githubusercontent.com/Crowndev/crowncoin/master/scripts/crown-server-install.sh | bash
This script will automatically look for the latest release. To check if the update worked, enter the following command into your VPS and check if the version is 0.12.4 or later.
Code: [Select]
crown-cli getinfo
IMPORTANT: You will need to restart your nodes from your local wallet!
You do this by navigating to the Masternodes or Systemnodes tab in your wallet and either right-clicking a node and clicking 'Start MISSING' at the bottom of the screen. You can select the 'start all' check box in the pop-up that appears.
Beware that checking this box this will restart all your nodes and put them in the back of the queue, so make sure you've updated your nodes before performing this step!

If you start alias and crown-cli systemnode status or crown-cli masternode status returns waiting for remote activation please check that you have enough peers with the new version 0.12.4.1 with crown-cli getpeerinfo. Should you not have any peers running the new version, do the following:

Code: [Select]
crown-cli stop
rm -rf ~/.crown/peers.dat
crownd &

This will stop the client, clear your peers.dat and restart the client. Peers with the new version will be added automatically.

After this step, click start alias and check if the master- or systemnode is "successfully started".

If you have any trouble following the above guide, please email support@crown.tech
« Last Edit: July 13, 2018, 12:17:46 pm by higherbridge »