Skip to content

Masternode Troubleshooting Guide V0.12.2.5

Jump to bottom
Crypto Centric edited this page Mar 26, 2019 · 1 revision

Masternode troubleshooting guide

Troubleshooting “Watchdog Expired” and “Masternode not in masternode list” Issues on Cold Node VPS – (Ubuntu)

  1. After installing your VPS cold node and running “start alias” from your windows wallet. Wait 30 minutes before troubleshooting any further.

  2. Log in to your VPS using Putty

  3. Run command: cd Absolute

  4. Check you are on the latest block and have a number of connections to the network. Run command: absolute-cli getinfo (You can check the current block number from: http://explorer.absolutecoin.net/ ) You can also run the command: absolute-cli mnsync status, this will tell your masternode has synced correctly with the network. The command should report back "AssetName": "MASTERNODE_SYNC_FINISHED".

  5. Run this command in the same folder: "absolute-cli masternode status" If the node reports “Masternode successfully started”, continue to step 11 If the node reports “not capable Masternode: Masternode not in masternode list” proceed to the next step

  6. Return to root, run command: cd

  7. Read the node list Wiki page here: https://github.com/absolute-community/absolute/wiki/Node-List-for-V0.12.2.5

  8. Add V0.12.2.5 node list to all absolute.conf files. We recommend adding the node list to the absolute.conf file in .absolutecore on your Linux VPS.

This can be done using this command set from root or home directory:

cd .absolutecore
nano absolute.conf

Add the node list to the bottom of the file

Then add the same list to the absolute.conf in windows. This can be found where your wallet.dat file is stored. The default absolutecore folder location is in %appdata% (you can type this into start menu and hit enter)

Open absolute.conf Add the node list to the bottom of the file

  1. Make sure you have installed Sentinel on the VPS. If you have installed using our script, then Sentinel should be installed and will be found in “/root/.absolutecore/sentinel” the guide for manually installing Sentinel can be found here: https://github.com/absolute-community/absolute/wiki/Installing-Sentinel-(V1.2)-on-Linux

  2. Find the sentinel folder. Depending on your install method this will normally be either “/root/.absolutecore/Sentinel” or “/root/Sentinel/”. Use the command ls – a to find the folder if you are unsure where it is.

  3. Change directory to this folder. For instance "cd .absolutecore/sentinel”

  4. Run this command: git pull

This will update sentinel from the absolute repository on Github. If your sentinel installation was done a very long time ago, you may find it was installed from the original repository which is now not in service. If it says it is up-to-date and you know that the last time you installed sentinel was before 8 of July 2018. Then double check the version in the next step.

  1. Run this command from the Sentinel folder: ./venv/bin/py.test ./test (You should a return message reading “23 passed”

  2. Check that your sentinel version is correct. From the sentinel folder:

cd lib
nano config.py

Check on line 15 that it says: sentinel_version = "1.2.0"

If it does say "1.2.0" continue to step to 18 If it says any number lower than 1.2.0, continue to step 16.

  1. reinstalled Sentinel, to do this delete the sentinel folder using this command from the. absolutecore folder: rm –r sentinel. Then follow the sentinel installation guide to install the latest version: https://github.com/absolute-community/absolute/wiki/Installing-Sentinel-(V1.2)-on-Linux

  2. Recheck the version as of step 15.

  3. Check that Sentinel is configured in crontab

from any folder on your VPS run: crontab –e

at the bottom of the file make sure this line is present:
* * * * * cd $HOME/.absolutecore/sentinel && ./venv/bin/python bin/sentinel.py >/dev/null 2>&1

If it’s not, add it. exit using crtl +O, then crtl + X.

  1. Restart both wallets, wait two minutes then start alias from the windows wallet.

  2. Check step 5 again, your node should go enabled after these steps. If not report back to the support channel on Discord: https://discord.gg/FhtgzY8

Clone this wiki locally