> ## Documentation Index > Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt > Use this file to discover all available pages before exploring further. # Error message lookup > Find the literal error string you are seeing and jump to the page that explains it This page maps literal error strings to the page that explains each one. Paste or search for the exact text you see in a log line, a `kubectl` event, an S3 client response, or a Slurm reason. Then follow the link to the page that explains the cause and the fix. If you can't find your error string here, browse the [Support articles](/support) by product, or [contact support](/support/contact). Before you open a ticket, gather the evidence listed in the [support ticket templates](/support/ticket-templates). ## How to use this page Error strings are grouped by the surface where they appear: Kubernetes scheduling and Pods, capacity and quota, GPU and training, networking, and storage. Within each group, entries are listed by the substring you are most likely to search for. Match on the distinctive part of the message, not the full line, because most messages include Pod names, timestamps, and other variable text. ## Scheduling and Pod errors These strings appear in `kubectl describe pod`, `kubectl get events`, or Pod status on CKS. | Error string | What it usually means | Where to go | | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `FailedScheduling` | The scheduler can't place the Pod on any Node. The accompanying text names the reason, for example insufficient GPUs, taints, or affinity. | [Workload scheduling on CKS](/products/cks/clusters/scheduling/workload-scheduling). | | `0/N nodes are available` | No Node satisfies the Pod's requests, taints, or affinity. The suffix lists the failing predicate per Node. | [Workload scheduling on CKS](/products/cks/clusters/scheduling/workload-scheduling). | | `Insufficient nvidia.com/gpu` | No Node has enough free GPUs for the Pod's request. | [Node Pool status](/products/cks/nodes/nodepool-status). | | `Insufficient rdma/ib` | No Node has a free RDMA interface for the request. | [InfiniBand and RoCE labels](/products/networking/hpc-interconnect/infiniband-roce-labels) and [Use GPUDirect RDMA](/products/networking/hpc-interconnect/use-gpudirect-rdma). | | `node(s) had untolerated taint(s)` | The Pod lacks a toleration for a taint CoreWeave or you applied to the Node. | [Workload scheduling on CKS](/products/cks/clusters/scheduling/workload-scheduling). | | `ImagePullBackOff`, `ErrImagePull` | The kubelet can't pull the container image: wrong name or tag, missing pull secret, or registry rate limiting. | [Workload scheduling on CKS](/products/cks/clusters/scheduling/workload-scheduling) for namespace and secret context. | | `CreateContainerConfigError` | The container references a missing ConfigMap, Secret, or key. | Check the referenced ConfigMap and Secret names against your manifest. | | `OOMKilled` | The container exceeded its memory limit and the kernel killed it. | [Recommended resource requests and limits](/support/cks/articles/what-are-the-recommended-resource-requests-and-limits-for-gpu-pods). | | `Multi-Attach error for volume` | A `ReadWriteOnce` volume is still attached to another Node, often after a Node failure or a stuck Pod. | [Troubleshoot a Pending PVC](/support/storage/articles/why-is-my-pvc-stuck-in-pending). | | `FailedMount`, `Unable to attach or mount volumes` | The volume can't mount: missing PVC, wrong access mode, or a storage-side problem. | [Troubleshoot a Pending PVC](/support/storage/articles/why-is-my-pvc-stuck-in-pending). | ## Capacity and quota errors These strings appear on Node Pool status, in scheduling events, and in the Cloud Console. | Error string | What it usually means | Where to go | | ------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | `CWInsufficientCapacity` | CoreWeave doesn't currently have free capacity to satisfy the Node Pool's `targetNodes`. | [Node Pool status](/products/cks/nodes/nodepool-status). | | `CWOverQuota` | The request exceeds your organization's quota for the instance type. | [Node Pool status](/products/cks/nodes/nodepool-status) and [Quota self-service](/products/cks/clusters/quotas). | | `QueuedAwaitingCapacity` | The Node Pool request is valid and queued until capacity frees up. | [Node Pool status](/products/cks/nodes/nodepool-status). | | `Requested node configuration is not available` (Slurm) | The Slurm job requests a partition, feature, or constraint that no Node provides. | [Monitor Slurm node states](/products/sunk/manage_sunk/slurm-node-states). | ## GPU and training errors These strings appear in training logs, GPU health events, and `dmesg`. | Error string | What it usually means | Where to go | | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | `NCCL error`, `NCCL WARN` | A collective communication operation failed. The numeric code and message identify the cause, often a network or interface problem. | [Why is multi-node NCCL training slow?](/support/platform/articles/why-is-my-multi-node-nccl-training-slow). | | `NCCL error 3`, `internal error` | An internal NCCL failure, frequently downstream of a transport or topology problem rather than a NCCL bug. | [Use GPUDirect RDMA](/products/networking/hpc-interconnect/use-gpudirect-rdma). | | `WorkNCCL ... timed out`, `Watchdog caught collective operation timeout` | A `torch.distributed` collective didn't complete within the timeout, often because one rank fell behind or died. Review per-rank logs to find the first rank to fail. | [Why is multi-node NCCL training slow?](/support/platform/articles/why-is-my-multi-node-nccl-training-slow). | | `XID` (for example `XID 79`, `XID 48`, `XID 119`) | An NVIDIA driver-reported GPU error. The XID number classifies the fault, from recoverable to hardware failure. | [Interpret GPU health events](/support/cks/articles/how-do-i-interpret-gpu-health-events). | | `CUDA error: out of memory` | The process requested more GPU memory than is free. Reduce batch size or model footprint. | [Recommended resource requests and limits](/support/cks/articles/what-are-the-recommended-resource-requests-and-limits-for-gpu-pods). | | `uncorrectable ECC error`, `Xid ... row remap` | A GPU memory hardware fault. CoreWeave detects these and replaces affected hardware. | [Interpret GPU health events](/support/cks/articles/how-do-i-interpret-gpu-health-events) and [Node cordoning](/products/cks/nodes/cordon). | ## Networking errors These strings appear in application logs, `kubectl` events, and DNS lookups. | Error string | What it usually means | Where to go | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | | `dial tcp ... connection refused` | The target Service or Pod isn't listening, or the Service has no ready endpoints. | [Networking support](/support/networking). | | `no route to host`, `network is unreachable` | The destination isn't reachable from the Pod's network, often a policy, CIDR, or routing problem. | [Networking support](/support/networking) and [VPC CIDR blocks](/products/networking/vpc/vpc-cidr). | | `Temporary failure in name resolution`, `SERVFAIL`, `NXDOMAIN` | DNS resolution failed inside the Pod. | [Networking support](/support/networking). | | `i/o timeout` on a Service or external host | The connection started but received no response in time, often a policy or upstream problem. | [Networking support](/support/networking). | ## Storage errors These strings appear in NFS and PVC mounts, and in S3 client responses. | Error string | What it usually means | Where to go | | ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ESTALE`, `Stale file handle` | The NFS file handle is no longer valid, often after a remount or a deleted-and-recreated file. | [About Distributed File Storage](/products/storage/distributed-file-storage/about). | | `ENOSPC`, `No space left on device` | The filesystem, quota, or local disk is full. On `/tmp` this is often a tmpfs limit, not a disk limit. | [Manage quotas](/products/storage/distributed-file-storage/manage-quotas). | | `Permission denied` on a shared path | The path is owned by a different user or group, or the access mode doesn't allow the operation. | [About Distributed File Storage](/products/storage/distributed-file-storage/about). | | `BucketNotEmpty` | A delete-bucket call failed because the bucket still contains objects or incomplete multipart uploads. | [Empty and delete a bucket](/products/storage/object-storage/buckets/empty-and-delete-bucket) and [Abort multipart uploads](/products/storage/object-storage/buckets/abort-multipart-uploads). | | `405 Method Not Allowed`, `write suspended for this availability zone` | A write was attempted against a bucket or path where writes aren't allowed, often an over-quota write suspension. | [Manage Object Storage quotas](/products/storage/object-storage/manage-quotas). | | `PathStyleRequestNotAllowed`, `InvalidRequest` (path-style) | The S3 client used path-style addressing. CoreWeave AI Object Storage expects virtual-hosted addressing. | [Configure endpoints](/products/storage/object-storage/using-object-storage/configure-endpoints). | | `AccessDenied`, `403 Forbidden` (S3) | The request isn't authorized: wrong keys, missing bucket policy permission, or an organization policy block. | [Bucket policies](/products/storage/object-storage/auth-access/bucket-access/bucket-policies) and [Manage access keys](/products/storage/object-storage/auth-access/manage-access-keys/about). | | `SignatureDoesNotMatch` | The request signature is wrong, usually a wrong secret key, clock skew, or an addressing-style mismatch. | [Configure endpoints](/products/storage/object-storage/using-object-storage/configure-endpoints). | ## When the error is not listed If your exact string isn't here, the message is still your best search key. Try these steps in order: 1. Browse the [Support articles](/support) for your product by symptom, for example "pod pending", "mount failed", or "GPU error". 2. Check [what CoreWeave manages](/support/what-coreweave-manages) to decide whether the problem is on the platform side or the workload side. 3. Review the [glossary](/glossary) if the message includes a term you don't recognize, such as a Node label or a condition. 4. If you still need help, [contact support](/support/contact) with the evidence from the [support ticket templates](/support/ticket-templates).