Troubleshooting your node
Below are some common issues that you may run into with your node, here's how to fix them!
Last updated
Below are some common issues that you may run into with your node, here's how to fix them!
Last updated
Sometimes, the CUDA toolkit is installed in a non-standard location. The error message here is often not able to find libcu*12. For example, you might have CUDA installed with your Python setup. The following command would install CUDA into Python's enviornment.
The easiest way to fix is simply to link those non-standard CUDA libraries to the standard location, like this:
On Windows WSL, you could see this error while running gaianet init:
Import the Qdrant collection snapshot ... The process may take a few minutes. Please wait ... * [Error] Failed to recover from the collection snapshot. {"status":{"error":"Service internal error: Tokio task join error: task 1242 panicked"},"time":0.697784244}
When you look into the ~/gaianet/log/init-qdrant.log file, you could see this line of error:
The solution is to disable the autoMemoryReclaim feature in WSL. Step to turn on/off this feature:
Edit C:\Users<Your user name>.wslconfig
Remove or comment out autoMemoryReclaim in [experimental] section.
You can learn more about it here, this was discovered by RoggeOhta.
Port 8080 is in use. Exit ...You may see the following error when you run gaianet start.
The solution is to run gaianet stop first to kill all processes, and then run gaianet start to start the node.
On Windows WSL, you may see this error when running curl -sSfL 'https://github.com/GaiaNet-AI/gaianet-node/releases/latest/download/install.sh' | bash
The error is caused by the lack of libgomp.so.1, a library that should be automatically installed on Ubuntu by default.
To solve this, you must install the libgomp.so.1 library:
If you're using CentOS, you can use:
This issue was fixed in version 0.2.2.
It typically indicates that the Qdrant instance was not shut down properly before you try to init it again with a new snapshot. The solution is to stop the GaiaNet node first:
Alternatively, you could mannually kill the processes from the terminal or in the OS's Actvity Monitor:
Then you can run gaianet init and then gaianet start again.
It typically indicates that the Qdrant instance was not shut down properly before you try to init it again with a new snapshot. The solution is to stop the GaiaNet node first:
Alternatively, you could mannually kill the processes from the terminal or in the OS's Actvity Monitor.
Then you can run gaianet init and then gaianet start again.
The reason for this type of error is a mis-configured config.json file. The solution is to delete the comments in config.json and re-run the gaianet init command.
When running gaianet init to initialize a new node on macOS, you may encounter an error related to snapshot recovery if your snapshot contains a large amount of text. The error message may be the following:
This issue is caused by the default file descriptor (FD) limit on macOS, which is set to a relatively low value of 256.
To resolve this issue, you can increase the default FD limit on your system. To do so, run the following command:
This will temporarily set the FD limit to 10,000. Next, use gaianet init and gaianet start commands in the SAME terminal.
When running curl -sSfL 'https://github.com/GaiaNet-AI/gaianet-node/releases/latest/download/install.sh' | bash to install GaiaNet node software, you may meet the permisson denied error especially installing the WasmEdge runtime.
This error is caused by the lack of /tmp write permission. You can use --tmpdir to specify where you want to install the WasmEdge runtime. Please note, you will need to have written permission to the <YOUR_PATH> folder.
This problem is fixed in version 0.2.3.
