Sentinel Web Interface Monitoring

Originally posted by @stoner19 in #commands
Using the web monitor for the Sentinel is not enabled by default, but can be with the addition of 1 line into 1 new file.

echo "start_web_listener=1" >> /var/lib/nyzo/production/preferences

This should create a new file in the /var/lib/nyzo/production/ directory by the name of preferences and add start_web_listener=1 to the very first line of the file. Then your Sentinel web monitor should be accessible simply by navigating to the IPv4 of your Sentinel in any explorer.

If permissions are denied doing this you might have to append the command with sudo first, if you still get permission denied errors, just

sudo nano /var/lib/nyzo/production/preferences

paste start_web_listener=1 into the first line
ctrl+x then, y , then press enter to save and exit.

Additional info on the Sentinel Web Monitor:

  1. Should set up a firewall if you’re accessing from a remote ip. Sentinels do not use incoming so disable that and enable whatever specific ip you want to use. Helpful article here:

  2. Understanding the Monitor display:


from Nyzo dev:
The number is the number of blocks in the block response. So, reading left-to-right, the sentinel got 1 block from Nyzo 0 in the most recent request, 1 block in the request before that, 0 before that, etc. If the sentinel were in fast-fetch mode, you'd see a lot of 10s in the boxes. And efficiency is simply the number of blocks frozen divided by the number of blocks received. If everything is running smoothly, the sentinel is querying in a pseudo-round-robin mode: it asks Nyzo 0 for a block, gets that block, then asks Nyzo 1 for a block, gets that block, etc. If the sentinel worries that it's falling behind, it may ask for the same block from all 10 verifiers at once. If it gets the block from all 10 of them, the efficiency for that block will be 10%, because it can only use 1 of the 10 copies.

1 Like