Welcome to the Autonomi Network Node Setup Assistant! This custom assistant is designed to guide you through the process of setting up nodes on the Autonomi Network, ensuring a smooth and efficient experience. Whether you’re a volunteer supporting the network or part of Wave 1 or Wave 2, our assistant provides step-by-step instructions tailored to your operating system and node management preferences.
Key Features:
System Detection: Identifies your operating system and provides specific commands for Windows, Mac OS, and Ubuntu.
Purpose-Based Setup: Customizes instructions based on whether you’re volunteering or part of specific waves.
Node Management Choice: Offers options between the easy-to-use Node Launchpad and the advanced Safenode-Manager.
Comprehensive Guidance: From downloading necessary software to verifying installation and starting node services, every step is covered.
How to Use:
Initial Setup: Determine your operating system and purpose of running nodes.
Choose Your Management Tool: Decide between Node Launchpad for ease or Safenode-Manager for more control.
Follow Step-by-Step Instructions: Execute commands provided for downloading, installing, and running node management tools.
Verify and Configure: Ensure everything is set up correctly and configure paths if necessary.
Add and Manage Nodes: Add nodes based on your role and manage services efficiently.
Additional Support:
For any additional commands or help, the assistant provides easy access to help commands for both Safeup and Safenode-Manager.
By following the detailed instructions, you can set up and manage your nodes on the Autonomi Network with confidence. If you encounter any issues or have further questions, the assistant is here to help.
it defaults to running with --home-network. Maybe it should ask what type of setup the user has? --home-network (I believe still) is kind of a last resort?
when I told it that I has issues with the start command it says:
Let's troubleshoot the issue. First, check the logs to see what might have gone wrong.
Run the following command to view the logs:
bash
sudo journalctl -u safenode-manager.service
Which will not give the user anything as the safenode-manager is not the service.
I told it start didn’t work because I always have to give it my own --peer because the list is too long and I have issues on ubuntu 24 and always end of peering off my own nodes.
Overall it seems excellent and will walk you properly down the happy path if all goes well. I’m not sure how to teach it to troubleshoot though. Maybe if we could have it read /store the #beta-support channel?
I gave it all the links for the beta. Told it to always scrape the data for the links before interacting with the user. This way it is up to date. I instructed it to go step by step and mapped out the paths.
Actually, though it got the service name wrong, consulting the journal was a reasonable course of action to recommend. Most services log there. The safenode binary is non-standard in that respect, though in my personal opinion, it shouldn’t be. I think the logs should go to stderr by default (in which case they would show up in the journal), and only go to file if you request that. In my opinion, it’s a bit obnoxious for a program to fill up your disk with logs unless you tell it to do that.
Hit a paywall as well on the AI bot