Matrix Masternode Logging

Disarmm
3 min readApr 21, 2020

If you have issues with your masternodes, we will need to collect logs to troubleshoot. Please follow the steps below to enable the logging.

Please use verbosity level 5 on all your nodes and use a script to delete older log files to keep disk usage to a minimum. You should at least keep the last 24 hours of logs. Longer if you’re having ongoing issues and need help.

If you use docker containers:

In order to collect the necessary logs, we need everyone to update their container to change the verbosity back to level 5. This was a mistake on my part to ever change this to 1 in the container. I have updated it to use level 5 (more logs) and I have set it to remove logs older than 24 hours. This will allow the collection of important error logs without the using up too much space. I have made the process for updating all your containers very easy.

If you are using my docker containers, then you should be aware of my installer. If you run the following command…

bash < <(curl -s https://raw.githubusercontent.com/disarmm/MatrixSetup/master/MatrixInstaller.sh)

It will start the installer shown below. Choose option 6 to update your container image with the latest version.

When you select this option it will read all the containers on your server, remove them one by one, upgrade your container image, and then recreate them using the same ports and data paths originally used. No data will be lost in this process and you wont need to re-sync anything. This will also be the way you update your containers from now on when new gman files are released.

Once that finishes, it will also add my nodeMaint script to your system that can be used for various maintenance tasks. In order to run this, you can type

nodeMaint

from anywhere on your server and you’ll get the maintenance menu.

In order to collect the logs, you will need to chose option 6 to obtain the logs. It will let you choose which container to pull the logs from and then it will place the logs in the /tmp/MatrixLog directory. You will then need to retrieve those logs either with a USB drive or copy them over the network using SCP.

Note: Before you do this, please let your containers run for at least an hour to collect the more detailed logs.

If you are running a single standalone node:

With a standalone setup, it is much simpler to retrieve the logs. The are stored in the MatrixLogs directory. You will find this directory in the same path as your gman file that you use to launch your node. Please provide the most recent 5 logs when submitting your support ticket. If you are using verbosity 1 to save space, you will need to relaunch your node with verbosity 5 and let it run for an hour to collect more detailed logs.

--

--