Troubleshooting - Archived
Last updated
Was this helpful?
Last updated
Was this helpful?
| | | |
👇 You can also join our Discord or Telegram worker group to discuss your issue. 👇
Most symptoms are solved by restarting your node. If you experience issues running your node, try stopping the node by:
And attempt a restart with
If you still have issues attempt to .
Get an overview of your worker’s status first.
In case your node is stuck, a typical scenario would look like the following:
(image showing stuck node on the worker)
Now check the status of the node again.
If the local node block height is empty first, check if all required containers are running.
You should have three containers running as shown in this example:
(image showing the worker node’s running docker containers)
To get the most recent logs of each container, you may execute:
Note that <container_ID/container_name> must be replaced with the container you wish the receive the logs from. In the example above the container_ID is 8dc34f63861e and container_name would be phala-pherry.
If you attempt to post on the phala forum and do not know where the issue lies, please post the logs of all three docker containers. Copy-paste the container logs from the terminal into the forum post.
If a container is missing (<3 are running), you may attempt to restart it separately with the respective commands below.
Use the applicable command to restart your missing container.
In some cases, it might be beter to reinstall the mining script. To do this, first uninstall the script:
And delete the mining script repository by executing:
Now you may reinstall the mining script.
Some users running nodes may find their nodes are struggling to connect to peers, which causes nodes to be dropped from the network. You can check your node connections through executing:
For an optimal setup, you should have between 40 and 50 peers.
If you have insufficient peers do the following:
Check your firewall settings
Ensure there are no NAT or Policy-based filters
ℹ️ The most common issue is that your motherboard may not support a DCAP driver. In this case, the script cannot automatically install the isgx driver and results in the following error message.
(image of the terminal showing the DCAP driver error message)
In this case, prior to running sudo phala start, you need to manually install the isgx driver:
If the synchronization still fails, you may try to delete the khala chain database on your worker’s node. It is located in /var/khala-dev-node/chains/khala.
(image showing the khala blockchain files of the worker node)
It is located in /var/khala-dev-node/chains/khala.
First, stop your node with:
To delete the khala blockchain database on your node, execute the following commands:
To delete the Kusama blockchain , run:
If you encounter any issues uninstalling the mining scripts and all dependencies except the drivers, you may delete them by executing the following commands:
With the symptom in the scenario above, the right method to solve the issue would be restarting the node container only, with the commands mentioned , and restarting the containers.
You may now .
Feel free to read for more information if you are curious about the root causes. Also, do not hesitate to look for existing before posing your issue if you are stuck.
If the Khala Chain stops synching and is stuck at a specific block and does not continue to sync, we advise you first to .
You can to redownload and reinstall the new phala mining scripts.
