Error map

Secondary too stale to catch up (RECOVERING) MongoDB: We are too stale to use X as a sync source / replSet too stale to catch up — member in RECOVERING state

MongoDB · layer 5, Data

Open the full error page →

Centre: this error. First ring: errors it is linked with (7). 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.

4 · Application & API 5 · Data 6 · Platform & cloud
Secondary too stale to catch up (RECOVERING) — MongoDB: We are too stale to use X as a sync source / replSet too stale to catch up — member in RECOVERING state (MongoDB)Secondary t…Could not find host matching read preference — MongoServerSelectionError: Could not find host matching read preference { mode: "secondary" } for set rs0 (MongoDB)Could not find host…AlreadyInitialized: already initialized — MongoServerError: already initialized (rs.initiate on a configured replica set) (MongoDB)AlreadyInitialized:…Unclean shutdown: mongod.lock not empty / repair needed — MongoDB: Detected unclean shutdown - /var/lib/mongodb/mongod.lock is not empty (MongoDB)Unclean shutdown: m…WiredTiger: No space left on device — MongoDB: WiredTiger error (28) [...] No space left on device / Fatal assertion 28558 ... disk full (MongoDB)WiredTiger: No spac…NotWritablePrimary: not primary and secondaryOk=false — MongoServerError: not primary and secondaryOk=false / NotWritablePrimary: not master (MongoDB)NotWritablePrimary:…No primary found in replica set / ReplicaSetNoPrimary — MongoServerSelectionError: Server selection timed out after 30000 ms — topology type ReplicaSetNoPrimary (MongoDB)No primary found in…rs.initiate failed: member not reachable / no host described in new configuration — MongoDB: replSetInitiate quorum check failed: Could not connect to mongo2:27017 / No host described in new configuration 1 for replica set rs0 maps to this node (MongoDB)rs.initiate failed:…Transaction numbers are only allowed on a replica set member or mongos — MongoServerError: Transaction numbers are only allowed on a replica set member or mongos (MongoDB)Transaction numbers…Sort/Group exceeded memory limit of 100 MB (allowDiskUse) — MongoServerError: Exceeded memory limit for $group, but didn't allow external sort. Pass allowDiskUse:true to opt in (MongoDB)Sort/Group exceeded…nodemon crashed — [nodemon] app crashed - waiting for file changes before starting... (Node.js)nodemon crashedExited (0) — Docker container exits immediately (Exited (0) / Exited (1) right after start) (Docker)Exited (0)Restarting (1) — Docker container keeps restarting (Restarting (1) x seconds ago) (Docker)Restarting (1)FailedMount — Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition (Kubernetes)FailedMountMulti-Attach error — Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another (Kubernetes)Multi-Attach errorPVC Pending — PersistentVolumeClaim stuck in Pending (no persistent volumes available / waiting for first consumer) (Kubernetes)PVC PendingREADONLY You can't write against a read only replica — Redis: READONLY You can't write against a read only replica (Redis)READONLY You can't …NoSuchTransaction: Transaction was aborted or expired — MongoServerError: Transaction 1 has been aborted / NoSuchTransaction: transaction has expired (transactionLifetimeLimitSeconds) (MongoDB)NoSuchTransaction: …MongoServerSelectionError — MongooseServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017 (Node.js)MongoServerSelectio…MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017 — MongoDB: MongoServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017 (MongoDB)MongoNetworkError: …CursorNotFound: cursor id not found — MongoServerError: cursor id 1234567890 not found (CursorNotFound) (MongoDB)CursorNotFound: cur…CannotPullContainerError — ECS task stopped: CannotPullContainerError: pull image manifest has been retried ... / ref pull has been retried (AWS)CannotPullContainer…network not found — Error response from daemon: network X not found (Docker)network not foundPool overlaps — Error response from daemon: Pool overlaps with other one on this address space (Docker)Pool overlaps

Directly related (7)

Could not find host matching read preferenceMongoDB

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.

AlreadyInitialized: already initializedMongoDB

MongoServerError: already initialized (rs.initiate on a configured replica set)

`rs.initiate()` was called on a node that already has a replica set configuration.

Unclean shutdown: mongod.lock not empty / repair neededMongoDB

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.

WiredTiger: No space left on deviceMongoDB

MongoDB: WiredTiger error (28) [...] No space left on device / Fatal assertion 28558 ... disk full

MongoDB ran out of disk space on the data volume and stopped or refuses writes.

NotWritablePrimary: not primary and secondaryOk=falseMongoDB

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.

No primary found in replica set / ReplicaSetNoPrimaryMongoDB

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).

rs.initiate failed: member not reachable / no host described in new configurationMongoDB

MongoDB: replSetInitiate quorum check failed: Could not connect to mongo2:27017 / No host described in new configuration 1 for replica set rs0 maps to this node

`rs.initiate()`/`rs.add()` couldn't reach a listed member or the config doesn't include the current node's hostname.

Two steps away (16)

Transaction numbers are only allowed on a replica set member or mongosMongoDB

MongoServerError: Transaction numbers are only allowed on a replica set member or mongos

You started a transaction (or used retryWrites) on a standalone MongoDB server, which doesn't support them.

Sort/Group exceeded memory limit of 100 MB (allowDiskUse)MongoDB

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.

nodemon crashedNode.js

[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.

Exited (0)Docker

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…

Restarting (1)Docker

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.

FailedMountKubernetes

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.

Multi-Attach errorKubernetes

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.

PVC PendingKubernetes

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.

READONLY You can't write against a read only replicaRedis

Redis: READONLY You can't write against a read only replica

The client is connected to a replica (or a failed-over node) and tried to write.

NoSuchTransaction: Transaction was aborted or expiredMongoDB

MongoServerError: Transaction 1 has been aborted / NoSuchTransaction: transaction has expired (transactionLifetimeLimitSeconds)

A transaction ran longer than the allowed lifetime (60 s default) or was aborted, so later operations fail.

MongoServerSelectionErrorNode.js

MongooseServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017

The MongoDB driver couldn’t find a reachable server for the connection string.

MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017MongoDB

MongoDB: MongoServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017

The driver couldn't connect to a MongoDB server on localhost:27017 — nothing is listening there.

CursorNotFound: cursor id not foundMongoDB

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.

CannotPullContainerErrorAWS

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.

network not foundDocker

Error response from daemon: network X not found

The container or Compose project refers to a Docker network that doesn’t exist (any more).

Pool overlapsDocker

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).

Map another error

Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError