- Newest
- Most votes
- Most comments
Contacted AWS Support about this and was told it was a known issue and they are working on an OS patch to resolve this issue. No ETA on when that patch will be available. I hope that helps others who are stuck seeing this error fill up their logs.
@e0steven, thank you, is good to confirm that is something inside AWS, hope they fix it quickly
As an update, the upgraded cluster does not show Aborted Clients anymore, I expect the other cluster will get the patch soon.
rdsadmin is a built-in administrative account that is managed by AWS. AWS uses this account for maintenance and management tasks, so you should not modify this account. If you're seeing a large number of aborted connections from rdsadmin, it could be a symptom of a deeper problem.
So before upgrading please follow https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html ans check the parameters before and after upgrade since
sometimes major upgrades can affect some parameter values like https://dev.mysql.com/doc/refman/8.0/en/packet-too-large.html if you detect such differences you need to fix or you need to open case to AWS Support directly.
Hello @sdtslmn, thanks for you input, I think the issue is more general, I have created two new Aurora MySQL 3.03.1 also a 3.03.0 and in both new all-default clusters the situation happened, a lot of "db: 'unconnected' user: 'rdsadmin' host: 'localhost' (Got an error reading communication packets)" errors and the AbortedClient metric goes on.
Relevant content
- asked 10 months ago
- Accepted Answerasked 2 years ago
- asked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
We have the same issue /w 3.02.2 MySQL 8, have a constant stream of them in the error log, over a dozen per minute.
I created an empy RDS Aurora 3.03.1 MySQL 8.0 and the situation is the same, lots of erros for rdsadmin.
Same problem 8.0.mysql_aurora.3.03.0
We have same issue 8.0.mysql_aurora.3.02.2
Same issue with 8.0.mysql_aurora.3.02.2