Troubleshooting Node Deployment Errors
This page has some error codes that may display as you are onboarding your nodes. Please review the examples, causes, and proposed solutions before contacting support. If you encounter an error not listed here, please capture a screenshot and detail when it happened, which stage in onboarding you were at, the status of any lights on the server, and any other relevant details.
Missing Drives
Example Error
--------------------------------------------------------------------------------
INTERNET COMPUTER - SETUP - FAILED
--------------------------------------------------------------------------------
Please contact the Internet Computer Association (ICA) support.
--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------
Not enough drives found. Are all drives correctly installed?
--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------
Common Causes
This error means that the SetupOS installation medium could not detect all required drives. This is a common issue, even if you believe that all drives are installed correctly. Some of them may not be functioning properly, or may not be fully seated into the chassis.
Suggested Solutions
Check that all drives are fully seated and installed correctly, or install the required number of drives. You may be able to check the drives for indication LEDs to see which may not be installed or functioning correctly.
Invalid CPU Configuration
Example Error
--------------------------------------------------------------------------------
INTERNET COMPUTER - SETUP - FAILED
--------------------------------------------------------------------------------
Please contact the Internet Computer Association (ICA) support.
--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------
Number of threads (16/32) does NOT meet system requirements.
--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------
Common Causes
Issues related to CPU capability usually mean that the CPUs are not configured correctly in the system BIOS.
Suggested Solutions
Please check that BIOS settings are configured correctly. It may be helpful to reset all settings to factory defaults, and go through the BIOS configuration again.
Unable to Reach Internet
Example Error
--------------------------------------------------------------------------------
INTERNET COMPUTER - SETUP - FAILED
--------------------------------------------------------------------------------
Please contact the Internet Computer Association (ICA) support.
--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------
Unable to ping IPv6 gateway.
--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------
Common Causes
This error means that the node is not able to communicate with the network properly. This can be due to a misconfigured network configuration, or due to issues somewhere between the node and the rest of the internet.
Suggested Solutions
Please try to capture any output that is displayed before this error shows. For example:
* Printing user defined network settings... IPv6 Prefix : XXX IPv6 Subnet : XXX IPv6 Gateway: XXX * Printing system's network settings... IPv6 Prefix : XXX IPv6 Subnet : XXX IPv6 Gateway: XXX * Printing IPv6 addresses... SetupOS: XXX HostOS : XXX GuestOS: XXX
Please compare this, and the initial configuration, to what you expect. If this configuration does not match, please update the initial configuration, and try again.
If this does match the expected configuration, please attempt to diagnose any machines between this node and the rest of the internet. This could be due to improper firewall configuration, or an issue with the data center’s network. If all configuration looks correct, please attempt to reboot any machines between this node and the rest of the internet. In most cases, this would be a firewall.
Long Wait on Node Join
Example Error
Orchestrator started. Starting node registration. Attaching HSM. Sending add_node request.
But not:
Join request successful! You may now safely remove the HSM.
Common Causes
The node has installed and launched successfully, but is unable to join the network. This could be due to an out of date SetupOS, trouble contacting the NNS, or node installation limits on the network.
Suggested Solutions
Please verify that a recent version of SetupOS from the wiki is being used for the installation, and check https://dashboard.internetcomputer.org/ to see how many nodes are currently registered under your Node Provider. If there are more nodes listed than expected, or if there are multiple nodes overlapping, please have any extra nodes removed from the network before attempting to install again. This can be caused if multiple installations have been performed on the same hardware, without cleaning up the records from the network. The current installation does not need to be done again, but it will require re-insertion of the HSM before it will join successfully.