Topic: Updating masternode files on VPS

As of classic masternode consists of 2 parts - desktop wallet and server on VPS - here is short manual to update VPS part. This manual is for newbies, who is unfamiliar with linux.

So, let's connect to our VPS. You need to use Putty client, like you do when creating masternode. After connecting to VPS, let's have a look at the contents of our directory:

my-vps:~$ ls
urals-cli uralsd urals-tx

We need to stop our masternode temporarily, because main files may fail to update, as it used by a system.

my-vps:~$ ./urals-cli stop
Urals server stopping

So, we're going to copy an archive with needed files:

my-vps:~$ wget https://github.com/JohnMnemonick/UralsCoin/releases/download/1.1.0.13/urals-1.1.0.13-ubuntu_x64-16.04.tar.gz
--2018-06-21 14:23:29--  https://github.com/JohnMnemonick/UralsCoin/releases/download/1.1.0.13/urals-1.1.0.13-ubuntu_x64-16.04.tar.gz
Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
Connecting to github.com (github.com)|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/135063026/b19a12e8-68d9-11e8-8a5a-ed8fe39dfd90?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180621%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180621T112330Z&X-Amz-Expires=300&X-Amz-Signature=517114bcfb5c9d775022e3b768909bce2f0881c4adfbf5b46c5e23277a115e36&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Durals-1.1.0.13-ubuntu_x64-16.04.tar.gz&response-content-type=application%2Foctet-stream [following]
--2018-06-21 14:23:30--  https://github-production-release-asset-2e65be.s3.amazonaws.com/135063026/b19a12e8-68d9-11e8-8a5a-ed8fe39dfd90?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180621%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180621T112330Z&X-Amz-Expires=300&X-Amz-Signature=517114bcfb5c9d775022e3b768909bce2f0881c4adfbf5b46c5e23277a115e36&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Durals-1.1.0.13-ubuntu_x64-16.04.tar.gz&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)... 54.231.72.147
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|54.231.72.147|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3402810 (3.2M) [application/octet-stream]
Saving to: 'urals-1.1.0.13-ubuntu_x64-16.04.tar.gz'

urals-1.1.0.13-ubun 100%[===================>]   3.25M   802KB/s    in 4.1s

2018-06-21 14:23:35 (802 KB/s) - 'urals-1.1.0.13-ubuntu_x64-16.04.tar.gz' saved [3402810/3402810]

Extracting files from archive:

my-vps:~$ tar zxvf urals-1.1.0.13-ubuntu_x64-16.04.tar.gz
urals-1.1.0.13-ubuntu_x64-16.04/
urals-1.1.0.13-ubuntu_x64-16.04/uralsd
urals-1.1.0.13-ubuntu_x64-16.04/urals-tx
urals-1.1.0.13-ubuntu_x64-16.04/urals-cli

After unpacking, all files are located in urals-1.1.0.13-ubuntu_x64-16.04/ directory, so we move it into main dir :

my-vps:~$ mv urals-1.1.0.13-ubuntu_x64-16.04/* .

Done! Launching masternode:

my-vps:~$ ./uralsd
urals server starting

Now we need to check the current daemon version:

my-vps:~$ ./urals-cli getinfo
{
  [b]"version": 1010013[/b],
  "protocolversion": 70083,
  "walletversion": 61000,
  "balance": 0.00000000,
  "blocks": 90257,
  "timeoffset": 0,
  "connections": 11,
  "proxy": "",
  "difficulty": 3.623015456537316,
  "testnet": false,
  "keypoololdest": 1504273491,
  "keypoolsize": 1002,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Check the first "version" parameter, I try to make it bold. If version is equal to version in archive name -  that's ok.

If you got some troubles - ask your questions here, or telegram channel, bitcointalk thread, discord chat.

Share