Skip to content

Error codes

When Alcuin itself stops something, the message carries a code such as ALC-1001. Each code has a page here with what you see, why it happens and what to do. Codes never change meaning, so a search for one, or a link to its page in an issue, stays good.

Errors from Postgres carry the server’s own five-character SQLSTATE code instead, such as 42P01 for a table that does not exist. Alcuin shows those in the server’s words, at the place in your query the server points to. The Postgres manual lists them all in its error codes appendix.

CodeMeaningInternal name
ALC-1001Could not connectENGINE_CONNECT_FAILED
ALC-1002Connection lostENGINE_CONNECTION_LOST
ALC-1003Unknown SSH host keyENGINE_SSH_HOST_UNKNOWN
ALC-1004SSH host key changedENGINE_SSH_HOST_CHANGED
ALC-1005Transaction outcome unknownENGINE_TX_UNKNOWN
ALC-2001CanceledENGINE_CANCELLED
ALC-2002Timed outENGINE_TIMEOUT
ALC-3001Connection is read-onlyENGINE_READ_ONLY
ALC-3002Row changed since you loaded itENGINE_STALE_ROW
ALC-3003Changes already appliedENGINE_DUPLICATE_CHANGESET
ALC-3004Confirmation requiredENGINE_CONFIRM_REQUIRED
ALC-3005Not allowed for this roleENGINE_PERMISSION_DENIED
ALC-3006Conflicting changeENGINE_CONFLICT
ALC-3007Earlier changes landedENGINE_EARLIER_COMMIT_LANDED
ALC-4001Agent request refusedENGINE_AGENT_REFUSED
ALC-9001Not supported hereENGINE_UNSUPPORTED
ALC-9002No longer thereENGINE_NOT_FOUND
ALC-9003Request refusedENGINE_BAD_REQUEST
ALC-9004Service unavailableENGINE_UNAVAILABLE
ALC-9005Internal errorENGINE_INTERNAL