Troubleshooting
Panic: resource temporarily unavailable
This error means you have an already running instance of the node. Follow the step below to kill all nodes and restart just one instance.
Command GO not found
Check your .bashrc file
At the very end you should see
If there are duplicates, remove them, save and exit and then run source ~/.bashrc
If instead those lines are not there, add them by running this command.
Now try again to do whatever you were doing.
If you still get the command GO not found error you may try to simply export those variable temporarily, by running
See if this fixes the issue. If it does, keep in mind that you will have to run again those variable every time you reboot your server, because they are active only temporarily.
Node not visible to bootstrap peers
The first thing to do is to check your node/.config/config.yml file and see if all the settings are correct.
Got to Set up the gRPC calls , run the automatic script but also check manually to be sure.
Check also that your 8336 port is open, run sudo ufw status, the response should be similar to this one:
gRPCurl not found
Try the same solution as Command GO not found
Remove gRPC calls settings from config.yml
If you want to remove the gRPC calls setting from your config.yml file here is what you have to do:
Open the file root/ceremonyclient/node/.config/config.yml on your local pc using WinSCP
Find
listenGrpcMultiaddr: /ip4/127.0.0.1/tcp/8337and replace it withlistenGrpcMultiaddr: ââFind
statsMultiaddr: "dns/stats.quilibrium.com/tcp/443"and remove the line completely now your config.yml should be as it was generated by the node itself
How to debug your config.yml
A simple way to debug your config.yml file if you are not a dev is to create a node from scratch and download locally the config.yml file. Then download the config.yml of your working node, the one you have edited either via a script or manually.
The encryption keys will be different of course, and you may have some more lines in the "bootstrapPeers" section of one of the files, but you should easily see the lines you have added or if there is any typing error in the file you edited.
Frame number: 0
If you see Frame number:0 in your node log for a long time, one way to debug is to check if access to the network is healthy and that port 8336 is accessible remotely.
From your local PC or a system other than the node:
Make sure you have netcat installed:
sudo apt install netcatConfirm reachability of bootstrap:
nc -vzu YOUR_SERVER_IP 8336Replace YOUR_SERVER_IP with your node's IP*
Panic: get parent data clock frame: item not found
If you imported an external "store" folder to kickstart your node synchronization, you may see this error, while the node keeps crashing. Stop the node, delete the "SELF_TEST" file from your ".config" folder, and restart the node. If this doesn't solve, try to import in the ".config" folder the "REPAIR" file from another working node, and delete the existing one. Give the node 10â15 minutes to see if everything works correctly.
Last updated
