MultiNode Update - 17th Oct, 2024

Summary

For operators managing Oasis Nodes either locally or remotely (AWS) - with this update, you can now run multiple nodes on a single VPS or machine, simplifying your setup and reducing the need for additional resources.

Key Update:

• Multi-Node Support: You can now configure and run multiple Oasis Nodes on a single VPS or machine, reducing hardware requirements and simplifying your setup.

Note: This update is specifically for operators using local setups or remote servers such as AWS. If you're running your node through NodeOps, the platform will handle the update automatically. No changes or actions are required on your part.

---

Step 1: Stopping the PlayAI Node

• Navigate to your PlayAI Node directory and stop the running instance by executing:

  sudo docker-compose down

Step 2: Pull the Latest Docker Images

• Ensure you are in the PlayAI Node directory, then run:

  sudo docker-compose pull
  git pull --reb
  

• This command pulls the latest updates from the PlayAI GitHub repository.

Step 3: Delete and Recreate the .env File

1. Remove the Existing .env File:

   • Delete the current .env file to remove outdated configurations:

     sudo rm .env

2. Create a New .env File:

   • Create a new .env file and open it using a text editor:

     nano .env

   • Copy and paste the following into the file, updating the values:

     NODE_WALLET_ADDRESS='xx'
     NODE_SIGNER_KEY='xx'
     NODE_TOKEN_IDS=[x,x]

   • After filling in the details, save the file by pressing Ctrl + X, then Y, and hit Enter.

Step 4: Start the PlayAI Node with the Updated Configuration

1. Run the PlayAI Node:

   • Start the PlayAI Node using Docker Compose:

     sudo docker-compose up -d

   • This command starts the containers in the background with the updated configuration.

---

Managing Your Updated PlayAI Node

• Start the PlayAI Node: If it stops, start it again using:

  sudo docker-compose up -d
  

• Stop the PlayAI Node: To stop it, run:

  sudo docker-compose down
  

• Check the Status: To verify if the node is running, type:

  sudo docker ps
  

This revised guide outlines the steps to update the PlayAI Node configuration and Docker images, ensuring that the latest version runs with the new environment settings.

---

FAQ: Updating and Managing the PlayAI Node

1. Why do I need to pull the latest version from the GitHub repository?

   • Pulling the latest version ensures your PlayAI Node is running the most up-to-date code and includes all recent bug fixes, features, and improvements from the development team.

2. What should I do if the new Docker images fail to pull?

   • Ensure your server has internet access and that Docker is up-to-date. You can update Docker by running:

     sudo apt update
     sudo apt upgrade docker.io -y
     

   • If the issue persists, check the Docker or GitHub documentation for troubleshooting specific errors.

3. How do I edit the .env file if I make a mistake?

   • If you need to edit the .env file again, simply reopen it with:

      
     nano .env
     

   • Make your changes, and save by pressing Ctrl + X, then Y, and Enter.

4. What information is needed for the .env file, and why is it important?

   • The .env file contains critical environment variables like your wallet address, signer key, and token IDs. These values allow your node to authenticate with the network and manage specific tokens. Without accurate information, your node may fail to connect or operate correctly.

5. How can I verify if my PlayAI Node is running correctly after the update?

   • Use:

      
     sudo docker ps
     

   • This command lists all running containers. If you see your PlayAI Node container in the list, it indicates the node is up and running.

6. How can I access the logs if my PlayAI Node is not functioning properly?

   • To access the logs of the Docker container, use:

      
     sudo docker logs <container_id>
     

   • Replace <container_id> with the actual ID of the PlayAI Node container, which you can find using sudo docker ps.

7. Why should I delete and recreate the .env file?

   • Deleting and recreating the .env file ensures that any outdated or incorrect information is removed, and only the necessary and correct details are used for the updated node configuration.

8. How do I restart the PlayAI Node if I need to apply changes or fix issues?

   • To restart, you can run:

      
     sudo docker-compose down
     sudo docker-compose up -d
     

   • This stops the node and restarts it, applying any recent changes.

9. What should I do if I encounter permission issues while managing the node?

   • Make sure you are running the commands with sudo to ensure you have the necessary permissions. If issues persist, review your instance’s user permissions or check Docker's documentation.

10. Can I change the instance type or configuration if the current setup is insufficient?

    • Yes, you can stop your instance, create a snapshot of your current setup, and launch a new instance with a larger instance type (e.g., t3.large) to accommodate higher resource needs.

11. How often should I update my PlayAI Node?

    • It is recommended to check for updates periodically, especially when notified by the PlayAI team, to ensure your node has the latest features and security patches.