Updating dash core on Ubuntu 18.04

Krill

New Member
Nov 9, 2017
7
3
3
38
Hi everyone,

Sorry if this is posted elsewhere, couldn't find anything.

Does anyone have a step by step (non gui, terminal) guide to updating dash core on Ubuntu 18.04?

Kind regards,

~Krill
 

Krill

New Member
Nov 9, 2017
7
3
3
38
Thank you!

Didn't get any errors but didn't update "Dash Core RPC client version v0.13.2.0"
 

splawik21

Moderator
Dash Core Team
Foundation Member
Dash Support Group
Apr 8, 2014
1,942
1,303
1,283
All you need to do is simply stop the dashd
copy the binaries and replace old with new and start dashd
Of course you need to update sentinel as well by going to dashcore/sentinel and execute git pull
 

qwizzie

Well-known Member
Aug 6, 2014
1,720
840
183
I suggest you also install Dash Central monitoring and restart service.
That way you only need to stop dashd, replace binaries, update sentinel
and after 10 minutes your masternode will be automatically restarted
(which shows up in the "incidents" section of Dash Central).

The Dash Central restart script seems more reliable then other restart
scripts i tried.

If you have Dash running from within a home directory, you should check this guide with regards
to Dash Central monitoring and restart script (which was easier to understand for me then the guide from Dash Central itself, which put its instructions mostly outside of home directory):
https://docs.dash.org/en/stable/masternodes/maintenance.html#masternode-software-update
 
Last edited:

Krill

New Member
Nov 9, 2017
7
3
3
38
Figured it out. Had dashd and dash-cli in /usr/bin for some reason. Replacing those worked.

Thank you all!
 
  • Like
Reactions: qwizzie

Antti Kaikkonen

Active Member
Jun 20, 2017
258
170
103
dashradar.com
Dash Address
XnZdwT1w2kGeH6RujwoyJ7BBNrukdyTBRB
Some people who updated late were stuck in the wrong chain. To make sure that you are in the correct chain you can use the "getblockchaininfo" dash-cli command and compare the bestblockhash to any block explorer.
 

Krill

New Member
Nov 9, 2017
7
3
3
38
Some people who updated late were stuck in the wrong chain. To make sure that you are in the correct chain you can use the "getblockchaininfo" dash-cli command and compare the bestblockhash to any block explorer.
Hi,

Thanks for that, yes, looks like I'm stuck on block 1091182, how can I fix this?

--reindex-chainstate ?
 
Last edited:

qwizzie

Well-known Member
Aug 6, 2014
1,720
840
183
Hi,

Thanks for that, yes, looks like I'm stuck on block 1091182, how can I fix this?

--reindex-chainstate ?
My first thought is to indeed use --reindex-chainstate
If that does not work you can try to have block 1091182 "reconsidered"

command in debug console : reconsiderblock hashfromblock1091182
to get the hash you can check block 1091182 in an (up to date and on the right chain) block explorer

Source (after a quick google search) : https://www.reddit.com/r/dashpay/comments/7ksem6/dashcore_refuses_to_synchronize_past_block_723541/
 
Last edited:

Krill

New Member
Nov 9, 2017
7
3
3
38
My first thought is to indeed use --reindex-chainstate
If that does not work you can try to have block 1091182 "reconsidered"

command in debug console : reconsiderblock hashfromblock1091182
to get the hash you can check block 1091182 in an (up to date and on the right chain) block explorer

Source (after a quick google search) : https://www.reddit.com/r/dashpay/comments/7ksem6/dashcore_refuses_to_synchronize_past_block_723541/
Thank you very much for those! --reindex-chainstate seems to have done the job.