Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_Events.Messages.html below:

Amazon RDS event categories and event messages for Aurora

availability

DB instance shutdown.

None

availability

DB instance restarted.

None

availability

Error restarting mysql: message.

An error has occurred while restarting Aurora MySQL or RDS for MariaDB.

availability

RDS-EVENT-0419

Amazon RDS has been unable to access the KMS encryption key for database instance name. This database will be placed into an inaccessible state. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

None

backtrack

The actual Backtrack window is smaller than the target Backtrack window you specified. Consider reducing the number of hours in your target Backtrack window.

For more information about backtracking, see Backtracking an Aurora DB cluster.

backtrack

The actual Backtrack window is the same as the target Backtrack window.

None

configuration change

Updated to use DBParameterGroup name.

None

configuration change

Applying modification to database instance class.

None

configuration change

Finished applying modification to DB instance class.

None

configuration change

Finished applying modification to allocated storage.

None

configuration change

Finished applying modification to convert to a Multi-AZ DB instance.

None

configuration change

Finished applying modification to convert to a standard (Single-AZ) DB instance.

None

configuration change

There are number users matching the master username; only resetting the one not tied to a specific host.

None

configuration change

Unable to reset your password. Error information: message.

None

configuration change

Monitoring Interval changed to number.

The Enhanced Monitoring configuration has been changed.

configuration change

Finished updating DB parameter group.

None

creation

DB instance created.

None

deletion

DB instance deleted.

None

failure

Database instance put into state. message.

The DB instance has invalid parameters. For example, if the DB instance could not start because a memory-related parameter is set too high for this instance class, your action would be to modify the memory parameter and reboot the DB instance.

failure

Database instance in state. message.

The DB instance is in an incompatible network. Some of the specified subnet IDs are invalid or do not exist.

failure

Amazon RDS has been unable to create credentials for enhanced monitoring and this feature has been disabled. This is likely due to the rds-monitoring-role not being present and configured correctly in your account. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

Enhanced Monitoring can't be enabled without the Enhanced Monitoring IAM role. For information about creating the IAM role, see To create an IAM role for Amazon RDS enhanced monitoring.

failure

Amazon RDS has been unable to configure enhanced monitoring on your instance: name and this feature has been disabled. This is likely due to the rds-monitoring-role not being present and configured correctly in your account. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

Enhanced Monitoring was disabled because an error occurred during the configuration change. It is likely that the Enhanced Monitoring IAM role is configured incorrectly. For information about creating the enhanced monitoring IAM role, see To create an IAM role for Amazon RDS enhanced monitoring.

failure

Amazon RDS has been unable to create credentials to access your Amazon S3 Bucket for your DB instance name. This is due to the S3 snapshot ingestion IAM role not being configured correctly in your account or the specified Amazon S3 bucket cannot be found. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

Aurora was unable to copy backup data from an Amazon S3 bucket. It is likely that the permissions for Aurora to access the Amazon S3 bucket are configured incorrectly. For more information, see Physical migration from MySQL by using Percona XtraBackup and Amazon S3 .

failure

The DB instance can't be created because of insufficient resource limits. message.

The message includes details about the failure.

failure

RDS-EVENT-0418

Amazon RDS is unable to access the KMS encryption key for database instance name. This is likely due to the key being disabled or Amazon RDS being unable to access it. If this continues the database will be placed into an inaccessible state. Please refer to the troubleshooting section in the Amazon RDS documentation for further details.

None

failure

RDS-EVENT-0420

Amazon RDS can now successfully access the KMS encryption key for database instance name.

None

low storage

Allocated storage has been exhausted. Allocate additional storage to resolve.

The allocated storage for the DB instance has been consumed. To resolve this issue, allocate additional storage for the DB instance. For more information, see the RDS FAQ. You can monitor the storage space for a DB instance using the Free Storage Space metric.

low storage

The free storage capacity for DB instance: name is low at percentage of the provisioned storage [Provisioned Storage: size, Free Storage: size]. You may want to increase the provisioned storage to address this issue.

The DB instance has consumed more than 90% of its allocated storage. You can monitor the storage space for a DB instance using the Free Storage Space metric.

low storage

Your Aurora cluster's storage is dangerously low with only amount terabytes remaining. Please take measures to reduce the storage load on your cluster.

The Aurora storage subsystem is running low on space.

maintenance

Applying off-line patches to DB instance.

Offline maintenance of the DB instance is taking place. The DB instance is currently unavailable.

maintenance

Finished applying off-line patches to DB instance.

Offline maintenance of the DB instance is complete. The DB instance is now available.

maintenance

Database instance patched.

None

maintenance

The DB instance has a DB engine minor version upgrade available.

None

maintenance

Database instance upgrade is in progress.

None

maintenance

RDS will replace the host of DB instance name due to a pending maintenance action.

None

notification

message

This is an operator-issued notification. For more information, see the event message.

notification

Delaying database engine upgrade since this instance has read replicas that need to be upgraded first.

Patching of the DB instance has been delayed.

notification

DB instance stopped.

None

notification

DB instance started.

None

notification

Timezone files were updated. Restart your RDS instance for the changes to take effect.

None

notification, serverless

Initiated pause for the DB instance.

A new attempt to pause an idle Aurora Serverless v2 DB instance was started.

notification, serverless

Pause was canceled for the DB instance.

An attempt to pause an idle Aurora Serverless v2 DB instance was unsuccessful, due to workload.

notification, serverless

Successfully paused the DB instance.

The Aurora Serverless v2 DB instance was paused.

notification, serverless

Initiated resume for the DB instance.

The Aurora Serverless v2 DB instance started resuming, due to new workload or administrative or maintenance activity.

notification, serverless

Successfully resumed the DB instance.

notification

Cluster topology is updated.

There are DNS changes to the DB cluster for the DB instance. This includes when new DB instances are added or deleted, or there's a failover.

notification, global database

Attempt to block writes for DB cluster cluster_id in Region region_id succeeded.

Aurora began blocking writes at the storage layer in preparation for switchover or failover of an Aurora global database.

notification, global database

Attempt to block writes for DB cluster cluster_id in Region region_id timed out.

Aurora wasn't able to block writes at the storage layer in preparation for switchover or failover of an Aurora global database. The switchover or failover will proceed but you might need to recover recently written data from the snapshot of the original primary cluster.

read replica

Replication has stopped.

This message appears when there is an error during replication. To determine the type of error, see Troubleshooting a MySQL read replica problem.

read replica

Replication for the Read Replica resumed.

This message appears when you first create a read replica, or as a monitoring message confirming that replication is functioning properly. If this message follows an RDS-EVENT-0045 notification, then replication has resumed following an error or after replication was stopped.

read replica

Replication streaming has been terminated.

None

recovery

Recovery of the DB instance has started. Recovery time will vary with the amount of data to be recovered.

None

recovery

Recovery of the DB instance is complete.

None

recovery

Emergent Snapshot Request: message.

A manual backup has been requested but Amazon RDS is currently in the process of creating a DB snapshot. Submit the request again after Amazon RDS has completed the DB snapshot.

recovery

Multi-AZ instance recovery started.

Recovery time will vary with the amount of data to be recovered.

recovery

Multi-AZ instance recovery completed. Pending failover or activation.

This message indicates that Amazon RDS has prepared your DB instance to initiate a failover to the secondary instance if necessary.

recovery

Recovery of standby DB instance has started.

The standby DB instance is rebuilt during the recovery process. Database performance is impacted during the recovery process.

recovery

Recovery of standby DB instance has completed.

The standby DB instance is rebuilt during the recovery process. Database performance is impacted during the recovery process.

restoration

Restored from DB instance name to name.

The DB instance has been restored from a point-in-time backup.

security patching

A system update is available for your DB instance. For information about applying updates, see 'Maintaining a DB instance' in the RDS User Guide.

A new, minor version, operating system patch is available for your DB instance. For information about applying updates, see Operating system updates for Aurora DB clusters.

maintenance

Amazon RDS can't perform the OS upgrade because there are no available IP addresses in the specified subnets. Choose subnets with available IP addresses and try again.

None

maintenance

Amazon RDS can't perform the OS upgrade because of insufficient capacity available for the type instance type in the zone Availability Zone

None

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4