Jump to content
Sign in to follow this  
J3ll3

Tips and tricks to starting a masternode!

Recommended Posts

Introduction

This article is explaining the most commonly used tips and tricks that I use to start a troublesome masternode. It has to be said, that some newly installed masternodes start at the first attempt, while at other times it seems to be nearly impossible to get it going. One trick appears to be resolving a troublesome masternode in over 90% of all cases, while the remaining tricks might be needed in the last 10%. 

You should go through the procedures from tip to bottom, trying number 1 first! Please not that these procedures are for those that choose to install a masternode from scratch on a VPS or computer at home using our installation script that can be downloaded from Github. It requires that you have ssh access to the masternode. Masternodes provisioned by our hosting partners, may need you to contact the partners support lines.

TRICK #1

1.1 Procedure

A very common problem people run into is that when you have installed the masternode with the script and has fully synchronised, that when you try to activate it from the masternodes tab in the local wallet you are presented with the following error:

432528009_Screenshot2018-12-31at15_23_55.thumb.png.ca0a2889ea05f0a4a36303f540debdae.png

(Thanks to Discord user @AlexaUA for uploading this screenshot)

The first time I encountered this problem, I spent a lot of time trying to work out what IP address exactly was wrong. And I imagine some of you have been going through the same process. I found the answer on a DASH forum, which means that this error has been inherited from DASH and PIVX. All masternode coins derived from DASH and PIVX must have this problem, unless they have fixed it themselves.

The answer is simple. You can start the masternode in the local wallet by using the Debug Console. The Debug Console can be accessed by choosing Tools from the top menu, followed by Debug Console (1). After that you type the following in the text box as shown below (2):

startmasternode alias 0 VPS07

Bear in mind, that the VPS07 is the name of the masternode you have used in the masternode.conf file when you setup the masternode in your local wallet!
tip1.thumb.png.725f9784f7b609d023d994e128c5e08c.png

As soon as you press enter, the following, or very similar output, should show in the Debug Console window:

{
    "overall" : "Successfully started 1 masternodes, failed to start 0, total 1",
    "detail" : [
        {
            "alias" : "VPS07",
            "result" : "successful",
            "error" : ""
        }
    ]
}

You should now see the masternode as enabled in the masternode tab.

1.2 Verification

This step is very important, to make sure the masternode has started. If you don't verify this, and the masternode has not "received" the activation, it will switch to MISSING again after a few hours and no rewards will come in.

After you see the "Successful" message in 1.1, you need to login to the masternode with SSH, just like you did to install it. Now you need to run the following command on the commandline prompt:

paws-cli getmasternodestatus

It is very important, that the status that is displayed in the output is 4 (four).

If it is, all is in order, and you should start to see rewards after an initial wait of 3x the reward cycletime as displayed on our explorer (http://chain.paws.fund) in the top left corner.

Please contact us on discord if your experience problems.

TRICK #2

2.1 Procedure

If the masternode does not start after the verification in 1.2 has been performed, you can do the following. This procedure is know to start 90% of all masternodes that will not start after enabling it in the local wallet.

Use SSH to login to your masternode. You should see a prompt as follows:

root@yourvps:~$

Now you should stop the masternode service by typing the following command on the above commandline prompt and press enter. Do not proceed with the steps below, until the above shown prompt has reappeared:

systemctl stop PAWS

After that you execute the following commands one by one. Do not paste them all in at the same time, it is important that we see possible errors that might occur. The below commands remove the blockchain database on the masternode and will force it to download a clean copy from the network when the masternode is activated again:

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

Now we need to start the masternode service again. The masternode software will detect that the blockchain was removed and start a fresh download from the blockchain. This will take some time, so please be patient:

systemctl start PAWS

The service starts in the background and the prompt should reappear. Do not logoff from the server yet. We need to wait from the masternode to synchronise with the blockchain. We can do this by executing the following command multiple times, until the block count is the same as on our explorer (http://chain.paws.fund):

paws-cli getblockcount

The response will be a number, which is the current block that has been downloaded from the blockchain. This number will be low initially, but increase rapidly until it reaches the current blockheight of the PAWS blockchain. Please repeat the command, until you are satisfied that the number returned by the above command is the same as the blocknumber on our explorer in the Status section (http://chain.paws.fund).

Once the numbers match, you can return to the local wallet, and try and start it from the masternode tab in your local wallet. If you are presented with the "Invalid IP" error, please look at TRICK #1.

2.2 Verification

This step is very important, to make sure the masternode has started. If you don't verify this, and the masternode has not "received" the activation, it will switch to MISSING again after a few hours and no rewards will come in.

After you see the "Successful" message your local wallet, you need to execute the following command on the masternode on the commandline prompt:

paws-cli getmasternodestatus

It is very important, that the status that is displayed in the output is 4 (four).

If it is, all is in order, and you should start to see rewards after an initial wait of 3x the reward cycletime as displayed on our explorer (http://chain.paws.fund) in the top left corner.

Please contact us on discord if your experience problems!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
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.