Diagnose error codes

This page describes AlloyDB Omni error codes and recommended fixes.

Extract an error

To extract an error code, follow these steps:

  1. To get your database cluster manifest, run:

    kubectl get dbclusters.a DB_CLUSTER_NAME -n DB_CLUSTER_NAMESPACE -o yaml

    Replace the following:

    • DB_CLUSTER_NAME: the name of your database cluster—for example, my-db-cluster.
    • DB_CLUSTER_NAMESPACE: the name of the namespace of your database cluster.

  2. Check for database cluster status conditions and criticalincidents fields that might have some of the following error codes.

AlloyDB Omni error codes

Error code Description Recommended action
DBSE0601.PgBackRest: Failed to backup AlloyDB Omni uses pgBackRest for its backup and restore related features.
This error can occur on a backup resource when pgBackRest failed to take the requested backup.		 If it occurs, check the following logs for more information:
pgBackRest backup logs on the obs disk of the database Pod in the /obs/pgbackrest/db-backup.log directory

PostgreSQL database logs on the obs disk of the database Pod in the /obs/diagnostic/postgresql.log directory.
DBSE0604.pgBackRest: Failed to restore AlloyDB Omni uses pgBackRest for its backup and restore related features.
This error can occur on a restore resource when pgBackRest failed to restore.		 If it occurs, check the following logs for more information:
* pgBackRest restore logs on the obs disk of the database Pod in the /obs/pgbackrest/db-restore.log directory.

* PostgreSQL database logs on the obs disk of the database Pod in the /obs/diagnostic/postgresql.log directory.
DBSE1080. HA: Failed to stop primary database This error occurs when the primary database fails to stop properly.
This can be because the database is not responsive, or it might have timed out waiting for the database to finish stopping.		 If this occurs during a failover, the failover operation attempts to continue to promote a new primary database.
If the issue persists, you may need to manually repair or recreate the database.
DBSE1081. Failed to promote standby database This error can occur during a failover or switchover when attempting to promote a standby database.
Check the error message for more details.		 If this occurs, the failover or switchover operation attempts to roll back to the old primary database.
If the rollback fails, you may need to manually repair, restart, or recreate this database cluster.
DBSE1082. Failed to rewind the database This error can occur during an operation that tries to change a primary database into a standby database.
Check the error message for more details.		 If this occurs during a failover or switchover operation, AlloyDB Omni attempts to roll back to the old primary database.
If the rollback fails, you may need to manually repair, restart, or recreate the database cluster.
DBSE2411. PostgreSQL: Failed to create physical replication slot This error can occur on an upstream instance when trying to set up downstream replication.
Check the error message for additional details.		 If the error persists, you might need to restart the replication setup process.
DBSE2412. PostgreSQL: Failed to query replication slots This error can occur on an upstream instance. Check the error message for additional details on what caused the error.
DBSE2413. PostgreSQL: Failed to reload config This error can occur when a database parameter has been changed and is unable to reload. Check the error message for more details.
If the message indicates that a specific parameter causes the error, then you might need to change the parameter.
DBSE2414. PostgreSQL: Failed to run pg_basebackup This error occurs during the replication setup for a new downstream instance. Check the error message for additional details.
If the error persists, you might need to manually delete this instance and restart the replication process.
DBSE2415. PostgreSQL: failed to connect to database This error occurs when the operator agent is unable to connect to the database. The most likely reason is that the database is shut down or has crashed.
Read the error message for more details.
DBSE2416. PostgreSQL: Failed to set synchronous standby names This error can occur on an upstream instance when setting up a replication.
If synchronous standby names have not been set correctly, then standby names are asynchronous.		 Check the error message for more details.
If the issue persists, you might need to disable and then re-enable the replication.
DBSE2417. PostgreSQL: Failed to terminate replication This error can occur on an upstream instance if a downstream instance has changed, for example, the number of standbys is reduced. Check the error message for more details.
If the issue persists, you might need to disable and then re-enable the replication.
DBSE2418. PostgreSQL: Failed to drop replication slot This error can occur on an upstream instance if a downstream instance has changed, for example, the number of standbys is reduced. Check the error message for more details.
If the issue persists, you might need to disable and then re-enable the replication.