• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

System wide Masternode Setup with Systemd auto (re)start RFC

Should the official guide be updated to this one

  • yes

    Votes: 20 90.9%
  • no

    Votes: 2 9.1%

  • Total voters
    22
To upgrade to v18. I strongly suggest you start using the Dash Masternode Zeus. There is a menu called 'manage masternode' and from there you can install the new dashd and the new sentinel. To get the DMZ, follow the below instructions.

Code:
cd /tmp
git clone https://github.com/kxcd/Masternode-Zeus
chmod +x Masternode-Zeus/masternode_zeus.sh
mkdir -p ~/bin
cp Masternode-Zeus/masternode_zeus.sh ~/bin/

Once you have it installed, run it with
Code:
~/bin/masternode_zeus.sh

Once you have logged out and log back in the DMZ will appear in your path, so typing in master <TAB><TAB> will auto-complete it and you can run it again.
 
Hi I would like to ask for help. I used zeus to install MN however the service does not start.

Sep 09 12:22:59 Egon dashd[6556]: Error: Error reading configuration file: parse error on line 1: [A
Sep 09 12:22:59 Egon systemd[1]: dashd.service: Control process exited, code=exited, status=1/FAILURE
Sep 09 12:22:59 Egon systemd[1]: dashd.service: Failed with result 'exit-code'.
Sep 09 12:22:59 Egon systemd[1]: Failed to start Dash Core Daemon.
Sep 09 12:23:40 Egon systemd[1]: Stopped Dash Core Daemon.
-- Reboot --
Sep 09 12:24:04 Egon systemd[1]: Starting Dash Core Daemon...
Sep 09 12:24:05 Egon dashd[682]: Error: Error reading configuration file: parse error on line 1: [A
Sep 09 12:24:05 Egon systemd[1]: dashd.service: Control process exited, code=exited, status=1/FAILURE
Sep 09 12:24:05 Egon systemd[1]: dashd.service: Failed with result 'exit-code'.
Sep 09 12:24:05 Egon systemd[1]: Failed to start Dash Core Daemon.

Can anybody advise?
 
Hi I would like to ask for help. I used zeus to install MN however the service does not start.

Sep 09 12:22:59 Egon dashd[6556]: Error: Error reading configuration file: parse error on line 1: [A
Sep 09 12:22:59 Egon systemd[1]: dashd.service: Control process exited, code=exited, status=1/FAILURE
Sep 09 12:22:59 Egon systemd[1]: dashd.service: Failed with result 'exit-code'.
Sep 09 12:22:59 Egon systemd[1]: Failed to start Dash Core Daemon.
Sep 09 12:23:40 Egon systemd[1]: Stopped Dash Core Daemon.
-- Reboot --
Sep 09 12:24:04 Egon systemd[1]: Starting Dash Core Daemon...
Sep 09 12:24:05 Egon dashd[682]: Error: Error reading configuration file: parse error on line 1: [A
Sep 09 12:24:05 Egon systemd[1]: dashd.service: Control process exited, code=exited, status=1/FAILURE
Sep 09 12:24:05 Egon systemd[1]: dashd.service: Failed with result 'exit-code'.
Sep 09 12:24:05 Egon systemd[1]: Failed to start Dash Core Daemon.

Can anybody advise?

Check your dash.conf for any errors particularly on the first line, it seems the issue is there.
 
Check your dash.conf for any errors particularly on the first line, it seems the issue is there.
Hi Thanks.
This is solved now.

But now I see sentinel failed I did already registered MN from DMT

dashd version : Dash Core Daemon version v18.0.1
IP address : xxx
Port (9999) : OPEN
dashd pid / user : 1957 / dash
Block height : !!! 433514 !!!
Blockchair height : 1735429
CryptoId height : 1735429
Masternode status : Waiting for ProTx to appear on-chain
PoSe score : N/A
Masternode sync : MASTERNODE_SYNC_BLOCKCHAIN
Sentinel : Failed
Sentinel version : Dash Sentinel v1.7.1
Next payment : Unknown
 
Hi Thanks.
This is solved now.

But now I see sentinel failed I did already registered MN from DMT

dashd version : Dash Core Daemon version v18.0.1
IP address : xxx
Port (9999) : OPEN
dashd pid / user : 1957 / dash
Block height : !!! 433514 !!!
Blockchair height : 1735429
CryptoId height : 1735429
Masternode status : Waiting for ProTx to appear on-chain
PoSe score : N/A
Masternode sync : MASTERNODE_SYNC_BLOCKCHAIN
Sentinel : Failed
Sentinel version : Dash Sentinel v1.7.1
Next payment : Unknown
Check status again when your node is synced up fully, it should stop saying failed.
 
Thank you for this guide which lets users setup, monitor and restart dashd through systemd as a system service.

I ended up adjusting your guide on some points to handle my own very specific setup, so that i did not had to install everything from scratch
and also got it working on my other masternodes.

It has been running very stable for many many months now and i agree that using systemd to monitor and restart dashd is much better then any other restart script.
Thank you.
 
Hi,

I would like to ask for help. Currently I am running v18.0.1.
The problem is if I try to updated via zeus I am getting:

Press Y to continue or another other key to return to the main menu [y [N]] y
Starting Download of dashcore...
Checking machine type to determine package for download...
No such file or directory
Download of has failed! Aborting...
Installation of dashd has been unsuccessful, please investigate or seek support!
Press any key to continue.
 
Hi,

I would like to ask for help. Currently I am running v18.0.1.
The problem is if I try to updated via zeus I am getting:

Press Y to continue or another other key to return to the main menu [y [N]] y
Starting Download of dashcore...
Checking machine type to determine package for download...
No such file or directory
Download of has failed! Aborting...
Installation of dashd has been unsuccessful, please investigate or seek support!
Press any key to continue.

See : https://www.dash.org/forum/threads/dash-masternode-zeus-replacement-for-dashman.51618/#post-233538
 
I used this setup, but how do I properly trigger a reindex?

Normally I'd call dashd with the -reindex option, but now I use sudo systemctl start/stop dashd which doesn't allow for options.
 
I used this setup, but how do I properly trigger a reindex?

Normally I'd call dashd with the -reindex option, but now I use sudo systemctl start/stop dashd which doesn't allow for options.

Recommended approaches for this is to edit the dash.conf file located in either /etc/dash.conf or /home/dash/.dashcore/dash.conf and add the parameter reindex=1 and then comment it out after restarting.
 
@xkcd
Your guide on your second post will most likely need some adjusting, as Sentinel no longer needs to be installed and configured separately (it is already integrated through a previous Dash Core update).

Affects following part of your guide : # The below will install and configure sentinel.
 
Back
Top