Error map
WiredTiger: No space left on device MongoDB: WiredTiger error (28) [...] No space left on device / Fatal assertion 28558 ... disk full
MongoDB · layer 5, Data
Centre: this error. First ring: errors it is linked with (12). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (12)
Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition
The kubelet couldn’t mount one of the pod’s volumes, so the pod stays in ContainerCreating.
PersistentVolumeClaim stuck in Pending (no persistent volumes available / waiting for first consumer)
The PVC hasn’t been bound to a volume, so pods using it can’t be scheduled.
Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another
A ReadWriteOnce volume (EBS, Azure Disk, PD) is still attached to another node, so the new pod on a different node can’t use it.
mongod: Process exited with status 14 — Exception in initAndListen: IllegalOperation: Attempted to create a lock file on a read-only directory
`mongod` couldn't start because the data directory or log/socket file isn't writable or already locked.
MongoDB: Detected unclean shutdown - /var/lib/mongodb/mongod.lock is not empty
MongoDB wasn't shut down cleanly (crash/power loss), so it warns or refuses to start without recovery.
MongoDB: We are too stale to use X as a sync source / replSet too stale to catch up — member in RECOVERING state
A secondary fell so far behind that the primary's oplog no longer covers the gap, so it can't resync by replaying.
MongoDB: connection refused / timed out from a remote host — mongod bindIp defaults to 127.0.0.1
MongoDB only listens on localhost by default, so remote clients can't connect.
MongoServerSelectionError: Could not connect to any servers in your MongoDB Atlas cluster. One common reason is that you're trying to access the database from an IP that isn't whitelisted
Atlas rejects connections from IP addresses that aren't in the project's Network Access list.
MongoServerError: bad auth : Authentication failed. (Atlas user / special characters in password)
Atlas rejected the username/password in the connection string.
MongoDB: Out of memory: Killed process (mongod) — WiredTiger cache + queries exhausted RAM
The Linux OOM killer terminated `mongod` because the host ran out of memory.
MongoServerError: Exceeded memory limit for $group, but didn't allow external sort. Pass allowDiskUse:true to opt in
An aggregation stage needed more than 100 MB of RAM and spilling to disk wasn't enabled.
MongoServerError: BSONObj size: 17825792 (0x1100000) is invalid. Size must be between 0 and 16793600(16MB)
A single document (or an aggregation result row) grew past MongoDB's 16 MB limit.
Two steps away (36)
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
You’re accessing blob/queue data with Microsoft Entra ID, but the identity has only management roles (Owner/Contributor) — not a…
Kubernetes: CreateContainerConfigError — secret / configmap not found
Kubernetes can’t build the container’s configuration — usually a referenced Secret, ConfigMap or key doesn’t exist in that namesp…
Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available
The scheduler can’t find a node that satisfies the pod’s resource requests, selectors, taints or volume constraints.
QuotaExceededError: Failed to execute 'setItem' on 'Storage': Setting the value exceeded the quota
localStorage/sessionStorage is full (about 5 MB per origin) or storage is disabled.
MySQL ERROR 126 (HY000): Incorrect key file for table; try to repair it
MySQL can’t use a table’s index file — usually a full tmp disk during a query, or MyISAM corruption.
Stack is in ROLLBACK_COMPLETE state and can not be updated
The stack’s first creation failed and rolled back; a stack in ROLLBACK_COMPLETE can only be deleted, not updated.
CloudFormation stack in UPDATE_ROLLBACK_FAILED
An update failed, and then the rollback also failed, leaving the stack stuck until you continue the rollback.
Elastic Beanstalk: Environment health has transitioned from Ok to Severe
Most instances in the Elastic Beanstalk environment are failing health checks or returning errors.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
The docker CLI can’t talk to the Docker engine — it isn’t running, or your user can’t access the socket.
user is not in the sudoers file. This incident will be reported.
Your account isn’t allowed to use sudo.
Error: listen EACCES: permission denied 0.0.0.0:80
Node isn’t allowed to bind that port — ports below 1024 need root on Linux/macOS, and some Windows ports are reserved.
[nodemon] app crashed - waiting for file changes before starting...
Your app threw an error on startup; nodemon is waiting for a file change to retry.
Docker container exits immediately (Exited (0) / Exited (1) right after start)
The container started and its main process finished at once, so the container stopped — Docker containers only live as long as PI…
Docker container keeps restarting (Restarting (1) x seconds ago)
The container crashes on start and its restart policy (always/unless-stopped/on-failure) starts it again in a loop.
MongoServerError: not primary and secondaryOk=false / NotWritablePrimary: not master
A write (or read without secondary preference) hit a secondary — the primary changed or you connected directly to a secondary.
MongoServerSelectionError: Server selection timed out after 30000 ms — topology type ReplicaSetNoPrimary
The driver sees the replica set members but none is a primary (election failing or members unreachable).
MongoServerSelectionError: Could not find host matching read preference { mode: "secondary" } for set rs0
The requested read preference (secondary, nearest with tags) matches no available member.
ECS task stopped: CannotPullContainerError: pull image manifest has been retried ... / ref pull has been retried
The ECS task couldn’t pull its image — no network route to the registry, missing ECR permissions, or a wrong image tag.
Error response from daemon: network X not found
The container or Compose project refers to a Docker network that doesn’t exist (any more).
Error response from daemon: Pool overlaps with other one on this address space
Docker tried to create a network whose subnet clashes with an existing Docker network (or a VPN/host route).
Error: connect ECONNREFUSED 127.0.0.1:5432
Nothing is listening at that host:port — the target service is down or you’re connecting to the wrong address.
Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
A stream ended or was destroyed before it finished — often a client disconnect or upstream aborting a download.
TypeError: fetch failed (cause: ConnectTimeoutError / ECONNREFUSED / UND_ERR)
Node’s built-in fetch (undici) couldn’t complete the request; the real reason is in error.cause.
MongooseError: Operation `users.find()` buffering timed out after 10000ms
Mongoose queued a query waiting for a connection that never opened.
MongooseServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017
The MongoDB driver couldn’t find a reachable server for the connection string.
MongoServerError: E11000 duplicate key error collection: db.users index: email_1 dup key
An insert/update violated a unique index in MongoDB.
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
Segmentation fault (core dumped)
A program accessed memory it wasn’t allowed to, and the kernel killed it with SIGSEGV (exit code 139).
Killed / Out of memory: Killed process (Linux OOM killer)
The kernel ran out of memory and killed a process to recover — the program just prints “Killed” (exit code 137).
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
The V8 heap hit its limit — a large build (webpack, tsc, Next.js) needs more memory, or the app leaks.
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 listeners added
More than 10 listeners were added to one event — often a leak where listeners are added repeatedly.
CastError: Cast to ObjectId failed for value "x" (type string) at path "_id"
A value that isn’t a valid 24-hex-character ObjectId was used in an _id query.
Too many open files (EMFILE)
The process hit its file-descriptor limit — sockets, files and pipes all count.
ValidationError: User validation failed: email: Path `email` is required.
A document failed Mongoose schema validation before saving.
Lambda: Request must be smaller than 6291456 bytes for the InvokeFunction operation (RequestEntityTooLargeException)
The event payload (or response) is over Lambda’s 6 MB synchronous limit (256 KB for async invocations).
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError