gLiveView Errors

This section documents common issues you may encounter when using gLiveView and their corresponding solutions.

gLiveView Does Not Start

This can be caused by one of the following:

Reason 1: Node Not Fully Started

If your node has not started correctly, gLiveView will also not start. This can happen in the following situations:

  • During initial setup when the database has not yet completed syncing.

  • If the Cardano binaries have not been fully installed like during initial setup or in the middle of an upgrade

Solution: Wait for the database to sync and complete all updates then try again

Reason 2: An Incompatible Update Was Applied

If you applied a gLiveView update that is for a higher Cardano version than the one you are using, you may lose access to gLiveView.

Solution: Upgrade your Cardano binaries. In the future, do not update gLiveView before you update your Cardano bonaries

gLiveView Starts But Behaves Inconsistently

This is usually caused by wrong configuration.

Solution: Edit the env file and ensure that the PORT and CNODE_HOME values are correct than start gLiveView again.

Number of In/Out Not Correct in BP

By right, in your block producer node, you should only have In/Out connections the same number as the number of your relays. So, if you have 1 relay, you should have 1 In and 1 Out. If you have 2 relays, you should have 2 In and 2 Out and so on. If you see any number other than that, then there is something wrong. For example, you see 2 In and 1 Out when you only have 1 relay.

This problem is most likely caused by a wrong port number setting.

Solution: Check the port number at the top of the gLiveView screen. If this is not the same as your node’s port number, stop gLiveView, edit the env file and update the PORT variable. Run gLiveView again after saving the env file.

No Transactions Processed

The Mempool Tx/Bytes fields are good indicators that show if you are processing transactions. Even if you are not minting blocks, the Mempool Tx number should increase. In the Testnet environment this value may increase very slowly. In Mainnet however, thenvalue should increase every minute at least. If you find this value not moving, you have a problem.

Solution: This is a more difficult problem to troubleshoot as there many possible causes. If your nodes were processing transactikns before, try to recall what were the last changes you performed and start investigating from there. Other things yiu can look at are:

  • Port number and server IP address in your startup scripts

  • Port number and server IP address in the env file of gLiveView

  • Firewall port open settings between BP, relay and outside world

  • Topology file of BP must have its relays

  • Topology file of relays must have the BP and external relays that are confirmed to be accessible

  • All topology files must be correctly formatted, with no tabs and with commas between entries

  • You are running the correct version of the Cardano binaries

Slow Average Peer Response Time

If you are connecting out to slow peers, you may have issues sending out your block after you mint it. Ideally, all of your peers should have fast response times around 200ms or below.

Solution: Turn off any automatic update of your topology files and manually add peers yourself. I recommend to select peers near your location but also remember to select some peers that are intermediately far and 1 or 2 that are far. This will ensure you have both speed and redundancy. Restart the Cardano service for the changes to take effect.

Last updated