# Seeing errors in compute node initializations
<a name="troubleshooting-fc-v3-compute-node-initialization-v3"></a>

The following sections provide troubleshooting tips for when you see errors in compute node initializations. This includes bootstrap errors, seeing errors in logs, and where to go if none of the scenarios apply to your specific situation.

**Topics**
+ [Seeing `Node bootstrap error` in `clustermgtd.log`](compute-node-initialization-bootstrap-error-v3.md)
+ [I configured on demand capacity reservations (ODCRs) or zonal Reserved Instances](compute-node-initialization-odcr-v3.md)
+ [Seeing `An error occurred (VcpuLimitExceeded)` in `slurm_resume.log` when I fail to run a job, or in `clustermgtd.log`, when I fail to create a cluster](compute-node-initialization-vpc-limit-v3.md)
+ [Seeing `An error occurred (InsufficientInstanceCapacity)` in `slurm_resume.log` when I fail to run a job, or in `clustermgtd.log`, when I fail to create a cluster](compute-node-initialization-ice-failure-v3.md)
+ [Seeing nodes are in `DOWN` state with `Reason (Code:InsufficientInstanceCapacity)...`](compute-node-initialization-down-nodes-v3.md)
+ [Seeing `cannot change locale (en_US.utf-8) because it has an invalid name` in `slurm_resume.log`](compute-node-initialization-locale-v3.md)
+ [None of the previous scenarios apply to my situation](compute-node-initialization-not-found-v3.md)