Introduction
This FAQ answers key questions about the LFG Node CLI, covering workload management, hardware requirements, and node operations.
Frequently Asked Questions
Q: What are the hardware requirements for running an LFG Node CLI?
A: You need a minimum of 4 GB RAM, 2 CPU cores, 60 GB disk space, an x86/x64 processor, and a stable internet connection. For full details, see LFG Node CLI Hardware Requirements.
Q: How do I install the LFG Node CLI?
A: The LFG Node CLI is supported only on Ubuntu Linux 22.04 or higher. You download and run an installation script for that operating system. For a step-by-step guide, see Install LFG Node CLI on Ubuntu Linux.
Q: How do I monitor my node?
A: The LFG Node Dashboard gives an overview of node performance, status, and workloads. You can track uptime, active workloads, and more.
Q: What does the cycle timer indicate in the LFG Node Dashboard?
A: The cycle timer shows the time remaining until the next LFG node cycle, which resets every day at 2 AM UTC.
Q: How can I manage my workloads?
A: Using the LFG Node CLI, you can add, remove, and check the status of workloads. The dashboard lets you track workload performance, restart workloads when needed, and monitor activity in real time.
Q: What are the workload requirements for projects?
A: Some workloads have additional or more demanding hardware requirements, involving higher data processing, storage, or bandwidth needs. Review the requirements for each specific project workload you plan to run on your node.
Q: Can I run multiple workloads on the same machine?
A: Yes, you can run multiple different workloads on the same machine, but not multiple instances of the same workload. This depends on your system's ability to meet each workload's hardware requirements, so ensure your machine has enough memory, CPU, and storage to handle all of them at once.
Q: Where can I get help with LFG Node setup?
A: For guidance and troubleshooting, visit the LFG Discord Community for real-time support from the team and community.
Thanks for the feedback.