Comment on page
👇 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:
sudo phala stop
And attempt a restart with
sudo phala start
Get an overview of your worker’s status first.
sudo phala status
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.
sudo docker ps
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:
docker logs <container_ID/container_name> -n 100 -f
<container_ID/container_name>must be replaced with the container you wish the receive the logs from. In the example above the
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.
sudo phala start node
sudo phala start pruntime
sudo phala start pherry
In some cases, it might be beter to reinstall the mining script. To do this, first uninstall the script:
sudo phala uninstall
And delete the mining script repository by executing:
rm -rf $HOME/solo-mining-scripts-main
Now you may reinstall the mining script.
sudo apt update && sudo apt upgrade -y && sudo apt autoremove -y
sudo apt install wget unzip
rm -r main.zip #cleaning up the installation
cd solo-mining-scripts-main/ #note this depends on your current directory
sudo ./phala.sh install
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:
sudo docker logs -f phala-node
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
isgxdriver 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
sudo phala install isgx
If the synchronization still fails, you may try to delete the khala chain database on your worker’s node. It is located in
(image showing the khala blockchain files of the worker node)
It is located in
First, stop your node with:
sudo phala stop
To delete the khala blockchain database on your node, execute the following commands:
rm -rf /var/khala-dev-node/chains/khala
To delete the Kusama blockchain , run:
rm -rf /var/khala-dev-node/chains/polkadot
If you encounter any issues uninstalling the mining scripts and all dependencies except the drivers, you may delete them by executing the following commands:
sudo rm -r /opt/phala
sudo rm -r ~/solo-mining-scripts-main
sudo rm ~/main.zip