Verify the node is running¶

Provided you have registered your node and started it, it's time to verify it is running as a candidate on the network.

You can view the status of the process using the following commands:

Validate if the process is running¶

pgrep rbbc

Check the status of the process¶

journalctl -u redbelly.service

Check the status of the Redbelly service¶

sudo systemctl status redbelly.service

Check the Redbelly logs¶

sudo tail -f /var/log/redbelly/rbn_logs/rbbc_logs.log

Check the error logs¶

sudo tail -f /var/log/redbelly/rbn_logs/rbbc_logs_error.log

Redbelly Node Status Monitor¶

A python terminal dashboard for monitoring the health of a Redbelly node.

Requirements¶

During the Redbelly installer process you must have chosen yes to the following:

Enable UDP status server which allows tracking basic node statistics (y/n) (default: y):

This monitoring script needs python, pip, and the following packages installed:

pip install python-dateutil requests

Usage¶

python status.py

By default the script connects to localhost:6540 via UDP and refreshes every 5 seconds.

Options¶

Flag	Description	Default
`-a`, `--address`	Node hostname (or full URL when using `--http`)	localhost
`-p`, `--port`	UDP port	6540
`-mb`, `--minBalance`	Minimum RBNT balance before warning	10
`-r`, `--refreshSeconds`	Refresh interval in seconds	5
`--http`	Use the deprecated HTTP mode	off

Examples¶

# Monitor a remote node
python status.py -a {your node URL e.g. mynode.com}

# Custom port and faster refresh
python status.py -a {your node URL e.g. mynode.com} -p 7000 -r 2

# HTTP mode (deprecated)
python status.py --http -a http://localhost:6539

HTTP Deprecation Notice¶

As of node version 1.3.5, the status endpoint uses UDP port 6540 by default. The previous HTTP /status endpoint is still accessible via the --http flag but is considered deprecated and may be removed in a future release.

A note on Governance¶

Important

Please note that as a candidate node, your node will not be able to submit transactions to be written to the network as this responsibility is reserved to the governor nodes.

As we run regular network reconfigurations in the future, your node might be randomly promoted to governorship for a pre-determined period of time (usually 2 weeks).

Until your node is promoted to governorship, you will need to use a currently available RPC endpoint, should you wish to submit a transaction to the network via a wallet such as Metamask. Learn more about Redbelly Network Governance.