Error map
Executor error: Sort exceeded memory limit (find().sort) MongoServerError: Executor error during find command :: caused by :: Sort exceeded memory limit of 104857600 bytes, but did not opt in to external sorting
MongoDB · layer 5, Data
Centre: this error. First ring: errors it is linked with (8). 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 (8)
MongoServerError: operation exceeded time limit (MaxTimeMSExpired) / Query timed out
A query ran longer than `maxTimeMS` (or the driver's socket/timeouts) and was aborted.
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.
MongoServerError: Index build failed: E11000 duplicate key error collection: db.users index: email_1 dup key
You tried to build a unique index but existing documents already contain duplicate values.
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.
MongoServerError: Unknown modifier / unknown top level operator: $foo / Cannot use $in with a non-array
The query or update used an invalid operator or argument type.
Two steps away (22)
MongooseError: Operation `users.find()` buffering timed out after 10000ms
Mongoose queued a query waiting for a connection that never opened.
Docker build slow: "Sending build context to Docker daemon 2.5GB" / transferring context takes forever
docker build is uploading your whole project folder — node_modules, .git, data files — before building, because there’s no (or a…
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.
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.
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.
ReplyError: NOAUTH Authentication required.
The Redis server requires a password (or ACL user) but the client didn’t authenticate.
MongoDB: MongoServerError: Document failed validation (code 121)
The collection has a JSON Schema validator and the inserted/updated document doesn’t satisfy it.
mongorestore: Failed: db.coll: error restoring from dump: E11000 duplicate key error / unsupported BSON version
`mongorestore` couldn't load some documents — they already exist, indexes conflict, or the dump/server versions don't match.
MongoServerError: Index key too large to index (key size exceeds 1024 bytes) / pre-4.2 behaviour
A document has an indexed field whose value is too large for the index (limit 1024 bytes before MongoDB 4.2).
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).
MongoServerError: cursor id 1234567890 not found (CursorNotFound)
A cursor you were iterating timed out or was killed on the server, so the next batch fails.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError