Common Flux Node Diagnostic Commands

Created by John K, Modified on Wed, 16 Nov 2022 at 11:34 AM by John K





Flux Node Update Script


As a flux node operator you will need to keep not only your Flux Node components up to date (Fluxbench, Flux OS and Flux Daemon), but also the Linux operating system that is on your host machine. Here is a quick and easy script that you can run that will update your Flux packages, Flux OS and Linux OS.


sudo apt-get update -y && sudo apt-get --with-new-pkgs upgrade -y && sudo apt autoremove -y && cd zelflux && git checkout . && git checkout master && git reset --hard origin/master && git pull && sudo reboot


Copy and paste the above commands into your node's terminal. After it completes successfully the host machine will reboot.




Flux Node Command Line Tools


The Flux packages include a command line tools that you can use to control your Flux node components. These allow you to check things like benchmark results and also allow for flux service controls.


▶  COMMANDS TO MANAGE FLUX DAEMON
Start Flux daemon: sudo systemctl start zelcash
Stop Flux daemon: sudo systemctl stop zelcash
Help list: flux-cli help

▶  COMMANDS TO MANAGE BENCHMARK
Get info: fluxbench-cli getinfo
Check benchmark: fluxbench-cli getbenchmarks
Restart benchmark: fluxbench-cli restartnodebenchmarks
Stop benchmark: fluxbench-cli stop
Start benchmark: sudo systemctl restart zelcash

▶  COMMANDS TO MANAGE FLUX
Summary info: pm2 info flux
Logs in real time: pm2 monit
Stop Flux: pm2 stop flux
Start Flux: pm2 start flux

▶  COMMANDS TO MANAGE WATCHDOG
Stop watchdog: pm2 stop watchdog
Start watchdog: pm2 start watchdog --watch
Restart watchdog: pm2 reload watchdog --watch
Error logs: ~/watchdog/watchdog_error.log
Logs in real time: pm2 monit




Flux Node Debug and Error Logs


Accessing your Flux node logs is an important step is diagnosing issues with your node if problems arise. When contacting support we will likely ask you to provide us with these debug logs to help you diagnose any issues with your node.


tail -400 .fluxbenchmark/debug.log
tail -400 ~/.flux/debug.log
tail -400 ~/zelflux/error.log
tail -100 ~/watchdog/watchdog_error.log



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article