DB Instance restarting due to " MySQL induced log backup issues"
In the last two weeks, we have been seeing a database instance resetting once or twice a day. Looking at the recent event logs shows the following event, which notes the reset:
MySQL restart initiated to address MySQL induced log backup issues. Note that as part of this resolution, a DB Snapshot will be performed after MySQL completes restarting.
We have not added any new logging to our database instance or changed any settings in the last two weeks. We are not sure what could be causing log backup issues. How can we root cause this issue to drive to a solution?
Someone had a similar problem a few years ago: https://stackoverflow.com/questions/43199330/aws-mysql-rds-instance-becomes-unresponsive-and-getting-restarted-automatically. Later, the author of the post wrote that updating the database was a solution.
If you're looking for a solution to connect directly to RDS, here are step-by-step instructions: https://aws.amazon.com/premiumsupport/knowledge-center/rds-connect-ec2-bastion-host/. If you're looking for shell access, it may be not feasible because this is an AWS-managed service.
Is it redundant to have an EC2 instance and its EBS volumes in the same AWS Backup resource assignment?Accepted Answerasked 5 months ago
Aurora mysql: Started cross AZ failover to DB instance eventasked 5 months ago
Can't connect to MySQL db from Lightsail instance. MY-010055 warning in logs.asked 5 months ago
DB instance in AWS LightSail shows "unknown"asked 3 months ago
DB Instance restarting due to " MySQL induced log backup issues"asked 2 months ago
Update the instance type of AWS DocumentDBAccepted Answerasked 4 months ago
How can we find out when were the binary logs of a MySQL RDS instance created?asked a month ago
Instance reachability check failed - two days in a rowasked 3 years ago
What is the aurora_server_id (mysql) variable alternative for postgresql?asked 2 months ago
Aurora Serverless MySQL - Downtime during scaling eventasked 5 months ago