Error map
disk I/O error SQLite: disk I/O error (SQLITE_IOERR)
SQL · 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)
sqlite3.OperationalError: attempt to write a readonly database
The process can’t write to the SQLite file or its directory.
sqlite3.OperationalError: database is locked (SQLITE_BUSY)
Another connection holds a write lock on the SQLite file, and this one gave up waiting.
sqlite3.DatabaseError: database disk image is malformed
The SQLite file is corrupted.
SQLite: cannot start a transaction within a transaction
BEGIN was issued while a transaction was already open on the same connection.
SQLite: datatype mismatch (SQLITE_MISMATCH)
SQLite refused a value for a column with strict typing, such as a non-integer for an INTEGER PRIMARY KEY or a STRICT table column.
SQLite: database or disk is full (SQLITE_FULL)
SQLite couldn't allocate more space: the disk, quota or a configured size limit is full.
SQLite: database table is locked (SQLITE_LOCKED)
A statement on the same connection (or shared cache) conflicts with another statement that still has an open cursor on that table.
Compute Engine VM disk full: No space left on device — resize the persistent disk and filesystem
The boot or data disk is full, so services crash or SSH logins fail.
Two steps away (24)
Linux: Permission denied
Your user (or the service user) lacks read/write/execute permission on a file, directory or one of its parents.
sqlite3.OperationalError: no such column: x
SQLite can’t find the column — missing migration, typo, or a string written in double quotes.
sqlite3.IntegrityError: UNIQUE constraint failed: users.email
An insert/update duplicated a value in a UNIQUE or PRIMARY KEY column in SQLite.
Deadlock found when trying to get lock; try restarting transaction
Two transactions waited on each other’s locks; the database killed one so the other could continue.
Lock wait timeout exceeded; try restarting transaction (MySQL 1205)
A query waited too long for a row lock held by another transaction and gave up.
MySQL ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
MySQL detected a deadlock between two transactions and rolled one back.
error: object file .git/objects/x is empty / fatal: loose object is corrupt
The local Git object database is corrupted — usually after a crash, disk full or sync tool interference.
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.
sqlite3.IntegrityError: NOT NULL constraint failed: table.column
A NULL went into a NOT NULL column in SQLite.
sqlite3.IntegrityError: FOREIGN KEY constraint failed
An insert/update/delete violated a foreign key in SQLite (with PRAGMA foreign_keys=ON).
sqlite3.OperationalError: unable to open database file
SQLite couldn’t open or create the database file — wrong path or missing/unwritable directory.
sqlite3.OperationalError: near "x": syntax error
SQLite couldn’t parse the statement; the token after “near” is where it stopped.
AttributeError: 'X' object has no attribute 'y'
You accessed an attribute or method that doesn’t exist on that object type.
java.lang.ClassCastException: class A cannot be cast to class B
An object was cast to a type it isn’t.
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
A Node API got an argument of the wrong type — usually undefined because an env var or config value is missing.
ERROR: could not extend file "base/…": No space left on device
The disk holding the PostgreSQL data directory (or WAL) is full.
SQL Server Error 1105: Could not allocate space for object in database because the PRIMARY filegroup is full
The data file or disk has no space left for new pages.
SQL Server Error 9002: The transaction log for database is full
The log file can't grow, so writes stop until space is freed.
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
DDL or a NOWAIT lock couldn’t get the lock because another session holds it.
SQL Server Msg 1205: Transaction was deadlocked on lock resources and has been chosen as the deadlock victim
Two sessions each hold locks the other needs, so SQL Server rolled one of them back.
SQL Server Msg 1222: Lock request time out period exceeded
A statement waited longer than `LOCK_TIMEOUT` for a lock held by another session.
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
GKE/Kubernetes: Pod unschedulable — 0/3 nodes are available: 3 Insufficient cpu
The scheduler found no node with enough free CPU/memory for the pod's resource requests.
Compute Engine: The zone 'projects/p/zones/us-central1-a' does not have enough resources available to fulfill the request (ZONE_RESOURCE_POOL_EXHAUSTED)
Google has no spare capacity for that machine type in the zone right now.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError