Fizz Node
Fizz Node FAQ

Fizz Node FAQ

1. Is Docker installation mandatory before installing a Fizz Node?

No, it's not mandatory. The Fizz Node installation script handles Docker installation for you. However, if you already have Docker installed, please ensure it is updated to the latest version.

2. How do I know if my Fizz Node is active?

To check if your Fizz Node is active, visit Fizz Node Status (opens in a new tab). If it shows as active, your node is running. If not, please reach out to our Discord community for assistance.

3. How much can I earn, or is there a token allocated to Fizz Node Runners?

Spheron aims to maximize your earnings by creating a resource pool of idle resources. However, your earnings depend on various factors, including demand. In addition to direct utilization points, Spheron offers IDLE rewards in Fizz Node Points. The network requires a token to operate, and any related information will be communicated publicly.

4. Can I run a Fizz Node on a Windows device?

Support for Windows is currently unavailable, but you can run it on Windows Subsystem for Linux (WSL).

5. When installing Docker, I'm receiving an "Incompatible CPU Detected" error on my M1/M2/M3 Mac. What should I do?

This error occurs because Homebrew installs the amd64 (Intel) version of Docker, which isn't compatible with Apple Silicon (arm64) chips like M1, M2, and M3. To resolve this issue, you need to install the Docker version designed for Apple Silicon manually:

  1. Download the Correct Docker Version:

  2. Install Docker Manually:

    • Open the downloaded .dmg file.
    • Drag and drop the Docker icon into the Applications folder.
    • Launch Docker from the Applications folder.

  3. Verify the Installation:

    • Open a terminal window.
    • Run docker --version to ensure Docker is installed correctly and the error is resolved.

Installing Docker directly from the official website ensures compatibility with your Apple Silicon device and eliminates the "Incompatible CPU Detected" error. After you've installed Docker on your Mac and verified it's working, re-run the Fizz Node installation script. This time, it should work for you without any hiccups.

6. Can I run multiple Fizz Nodes on a single device?

No, you can only run one Fizz Node per device. Each Fizz Node is designed to operate independently on a single machine. Additionally, each Fizz Node is mapped to a single wallet address, and you cannot use the same address for multiple Fizz Nodes. This limitation is in place for several reasons:

  1. Resource Management: Running multiple nodes on a single device could lead to resource conflicts and performance issues.
  2. Fairness: Limiting to one node per device helps maintain a fair distribution of nodes across the network.
  3. Security: Mapping each node to a unique wallet address enhances the security and accountability of the network.

If you want to run additional Fizz Nodes, you'll need to use separate devices, each with its own unique wallet address.

7. I have two or more GPUs in my device. Can I run the node to add them all?

This limitation is due to the Fizz Node Software's current design, which is optimized for single-GPU setups. However, the Spheron team is actively working on enhancing this capability.

Future updates aim to allow Fizz Nodes to utilize multiple GPUs simultaneously, which will enable users with multi-GPU setups to contribute more computational power to the network. This improvement will maximize the potential of high-performance systems and provide more flexibility for node operators.

Stay tuned for announcements from the Spheron team regarding updates that will enable multi-GPU support in Fizz Nodes.

8. I'm getting a permission denied error when running the fizzup.sh script. How do I fix this?

If you encounter a "permission denied" error when running the fizzup.sh script, it's likely because the script is trying to access /root/.spheron, which your current user doesn't have permission to access. This error might look something like this:

Permission Denied Error

To resolve this issue, you need to switch to the root user before executing the script. Follow these steps:

  1. Switch to the root user:

    sudo bash

  2. Once you're in the root shell, run the fizzup.sh script:

    ./fizzup.sh

This should allow the script to access the necessary directories and complete the installation process. Remember to exercise caution when operating as the root user, as it has unrestricted access to your system.

9. Is my data secure using someone else's GPU through a Fizz Node?

When you use a Fizz Node, your data is processed on another user's GPU system. At present, there is no way to prevent a technically savvy GPU owner from accessing your data. We advise against using private or sensitive data on Fizz Nodes. If you need to work with sensitive information, consider using the Provider mode to deploy on data center-grade GPUs with enhanced security measures.

Alternatively, you can implement a system where a proxy server handles your data manipulation and storage. You can send data to the service running on the Fizz Node at runtime using secure connections or encryption for tasks like training or fine-tuning. After processing, the results can be retunred to your proxy server for further handling and secure storage. This approach makes accessing your data more difficult for the Fizz Node runner during runtime.

10. How do I check the status of my Fizz Node?

To check the status of your Fizz Node, follow these steps:

  1. Access the Fizz Node Dashboard:

    • Go to the Fizz Node dashboard by navigating to the URL provided in the setup process.
    • If you're using the Spheron Fizz App, click the "Check Status" button.
    • Alternatively, you can use the command docker compose -f ~/.spheron/fizz/docker-compose.yml ps or docker-compose -f ~/.spheron/fizz/docker-compose.yml ps to check the status of your Fizz Node.

  2. Review the Status Information:

    • The status information will be displayed in the output.
    • Look for the container status, which should indicate if the container is running (Up) or not (Exited).

  3. Check the Logs:

    • If the container is not running, you can check the logs for any errors or issues by using the command docker compose -f ~/.spheron/fizz/docker-compose.yml logs or docker-compose -f ~/.spheron/fizz/docker-compose.yml logs.

  4. Verify the Node Status:

    • If the container is running, your Fizz Node is active.
    • If the container is not running, you can start it again using the command <your-fizz-node-directory>/fizzup.sh.

By following these steps, you can verify the status of your Fizz Node and troubleshoot any issues if the container is not running.

11. How do I check the reward details of my Fizz Node?

To check the reward details of your Fizz Node, follow these steps:

  1. Access the Fizz Node Dashboard:

    • Go to the Fizz Node dashboard by navigating to the URL provided in the setup process.

  2. Review the Reward Details:

    • The Fizz Node dashboard will display the reward details in FN points.

By following these steps, you can check the reward details of your Fizz Node.

12. When I ran the Fizz Node script, I got an error saying "brew command not found". How do I fix this?

If you encounter an error stating that the "brew command not found" when running the Fizz Node script, it means that Homebrew is not installed on your system or is not properly configured in your PATH. Homebrew is a package management system for macOS on which the Fizz Node script relies. To resolve this issue, follow these steps:

  1. Install Homebrew: Open your terminal and run the following command to install Homebrew:

    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

    This command downloads and runs the Homebrew installation script.

  2. Set up the PATH to Homebrew: After installation, you need to ensure that Homebrew is in your system's PATH. Run this command to add Homebrew to your PATH:

    echo 'PATH="/usr/local/bin:$PATH"' >> ~/.bash_profile

    This command appends the Homebrew binary path to your bash profile.

  3. Reload your bash profile: To apply the changes immediately, run:

    source ~/.bash_profile

  4. Verify Homebrew installation: Test if Homebrew is working correctly by running:

    brew help

    If Homebrew is properly installed and configured, you should see the help output for Homebrew commands.

  5. Run the Fizz Node script again: If the brew command is now working properly, you can run the Fizz Node script again:

    ./fizzup.sh

By following these steps, you should be able to resolve the "brew command not found" error and successfully run the Fizz Node script. If you continue to experience issues, ensure that your system meets all the prerequisites for running a Fizz Node and consider reaching out to the Spheron support community for further assistance.

13. How can I change my Gateway if my current one is down?

We've introduced a new feature that allows you to change your gateway if your current one is experiencing downtime. This is particularly useful when a gateway faces extended periods of unavailability. Here's how you can change your gateway:

  1. Edit Gateway:

    • Click on the edit ✏️ icon next to your current gateway.

  2. Select a New Gateway:

    • Choose a new gateway from the list provided.
    • The list is sorted based on proximity, so it's recommended that you select a gateway nearest to you for optimal performance.

  3. Update and Confirm:

    • Click the "Update Gateway" button.
    • Confirm the transaction in MetaMask.

After changing your gateway, follow these steps:

  1. Download the New Script:

    • Go to the setup screen and download the updated script.

  2. Follow the Setup Guide:

    • Execute the steps in the setup guide in a way that is similar to your initial setup process.

  3. Check Your Status:

    • Verify your node's status to ensure everything is running smoothly.

By following these steps, you can switch to a new gateway and get your Fizz Node back up and running quickly. If you encounter any issues during this process, don't hesitate to reach out to our Discord community for assistance.

14. I'm encountering a "GPU ID not found" issue. How can I help troubleshoot?

If you're experiencing a "GPU ID not found" issue, we need your help to troubleshoot and resolve this problem. Please follow these steps:

  1. Run the diagnostic command: Open your terminal and run the following command:

    nvidia-smi --query-gpu=pci.device_id --format=csv,noheader | head -n1 | cut -c3-6 | tr '[:upper:]' '[:lower:]'

  2. Note the output: The command will return a short string. Make sure to copy this output.

  3. Identify your GPU model: We need to know your GPU model name along with the command output.

  4. Report the information: Share both the command output and your GPU model name with our team through our Discord channel.

This information is crucial for our development team to understand the scope of the issue and develop a fix. Your cooperation in this matter is greatly appreciated and will help us resolve the problem more quickly.

15. How can I update my Fizz Node resources?

We've introduced a new feature that allows you to update your Fizz Node resources. This is particularly useful if you mistakenly registered your node with incorrect GPU or CPU units or if you didn't confirm the transaction during registration. Here's how you can update your node resources:

  1. Access the Dashboard:

    • Go to your Fizz Node dashboard.

  2. Initiate the Update:

    • Click on the "Update Node Resources" button.

  3. Select New Resources:

    • Choose the GPU or CPU unit you want to assign to your node.

  4. Confirm the Update:

    • Click "Update" and confirm the transactions that appear.
    • Note: There will be multiple transactions. Make sure to confirm all of them.

  5. Wait for Reload:

    • Let the screen reload once all transactions are confirmed.

  6. Download New Script:

    • Click the "Download" button to get the new script.

  7. Run the New Script:

    • Follow the steps outlined on the setup screen to run your new script with the updated resources.

Important Notes:

  • Simply changing the script will not update your Fizz Node resources. You must first update them through the dashboard.
  • If you updated your script prior to this release, make sure to follow this "Update Node Resources" guide and run your node script again with the updated resources.

After completing these steps, your Fizz Node will run with the new resource configuration. This update ensures that your node is correctly registered and can fully participate in the Fizz network.

16. I'm getting "Error response from daemon: unknown or invalid runtime name: nvidia" when running fizzup.sh. How do I fix this?

If you encounter the error "Error creating container: Error response from daemon: unknown or invalid runtime name: nvidia" when running the fizzup.sh script or upgrading your node, this typically indicates that you're running outdated versions of Docker and NVIDIA drivers. To resolve this, you'll need to upgrade both to their latest versions.

For Windows Users:

  1. Upgrade Docker Desktop:

  2. Upgrade NVIDIA Drivers:

For Linux Users:

  1. Upgrade Docker:

  2. Upgrade NVIDIA Drivers:

After upgrading both Docker and NVIDIA drivers, try running the fizzup.sh script again.

17. I'm getting an OS mismatch error while running the script. How do I fix this?

If you encounter an OS mismatch error while running the script, you'll need to update your OS setting in the Fizz dashboard. Here's how to resolve it:

  1. Access the Fizz Dashboard:
    • Go to your Fizz Node dashboard

Edit OS Button

  1. Update OS Setting:

    • Look for the edit (✏️) button next to your current OS
    • Click it to modify your OS setting

  2. Select Correct OS:

    • If the error message says "OS_ID is set to linux": Change your OS to Linux
    • If the error message says "OS_ID is set to wsl": Change your OS to Windows

  3. Confirm the Change:

    • Confirm the transaction in your wallet when prompted

  4. Download New Script:

    • After the OS change is confirmed, download the script again
    • This new script will be configured for your updated OS setting

  5. Run the New Script:

    • Execute the newly downloaded script
    • The OS mismatch error should now be resolved
Fizz Reward DetailsChain Details