Difference between revisions of "Node Provider Troubleshooting"
From Internet Computer Wiki
Katie.peters (talk | contribs) |
|||
| Line 5: | Line 5: | ||
* [[Updating Firmware]] | * [[Updating Firmware]] | ||
* [[iDRAC access and TSR logs]] | * [[iDRAC access and TSR logs]] | ||
| + | * Getting a shell during Node (SetupOS) installation, to troubleshoot a failure: | ||
| + | ** Hit enter until you see a login prompt | ||
| + | ** Log in with user <code>root</code> and empty password | ||
| + | ** Type <code>systemctl stop setupos</code> - it will auto-reboot if you don't do this | ||
| + | ** Now you have root access for diagnostics, etc | ||
==Node Status on the Dashboard== | ==Node Status on the Dashboard== | ||
Revision as of 19:47, 29 June 2023
Troubleshooting individual Nodes
- Possible Node Onboarding Errors
- Troubleshooting Unhealthy Nodes
- Updating Firmware
- iDRAC access and TSR logs
- Getting a shell during Node (SetupOS) installation, to troubleshoot a failure:
- Hit enter until you see a login prompt
- Log in with user
rootand empty password - Type
systemctl stop setupos- it will auto-reboot if you don't do this - Now you have root access for diagnostics, etc
Node Status on the Dashboard
The dashboard lists each node by the principal of the currently-running OS. Node Providers track privately which server corresponds to each principal. This includes updating their records when a node is redeployed and gets a new principal.
There are four statuses of node:
- Active in Subnet - This is a node which is healthy and is currently running a subnet.
- Awaiting Subnet - This is a node which is healthy and is currently a spare node. It is not running a subnet but it keeping itself updated so that it is ready at a moment's notice to take part in a subnet
- Offline - This is a node which has completely failed. The failure is recent enough that it hasn't been removed from the registry yet.
- If there is an outage of some sort at the data center, then the node should come back online and be healthy once it's resolved, as long as it doesn't take too long. Make sure that connectivity to the node is properly supplied before doing anything else.
- If there are no issues with connectivity, then troubleshooting steps should be taken. Note that the node will have to be removed from the registry before it can be redeployed, if redeployment is needed.
- Degraded - This node is struggling to keep up with the blockchain. If it's a temporary issue then it should catch back up and become healthy again. If it's a permanent issue, then it will eventually fail and go offline. If it's removed from the registry before it fails completely then it will disappear from the dashboard.
- Not listed at all. If a node is not listed at all, then it had an issue and it was already removed from the registry. Troubleshooting steps should be taken.
Changing your Node Provider principal in the NNS
Changing a DC principal
Node Provider Matrix channel
Discuss your issue with other Node Providers in the Node Provider Matrix channel.