Support for log_error_suppression_list in MySQL8 Parameter Groups

25

MySQL 8.0.34 error log contains deprecation warnings when a client authenticates using the mysql_native_password authentication plugin. This is the default for previous MySQL versions on RDS, so I imagine many users upgrading will have a similar issue. Errors look like this:

2023-08-31T12:01:12.183036Z 19100582 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password'
is deprecated and will be removed in a future release. Please use caching_sha2_password instead'

On a busy server, this creates several MB of logs per minute. I'd like to update to the preferred caching_sha2_password, but doing so requires client library updates which will take some time and coordination.

In the mean time, I'd like to suppress the warning using the https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_log_error_suppression_list system variable, but this variable is not supported in MySQL 8 parameter groups.

I can fall back to suppressing ALL warnings by setting https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_log_error_verbosity to 1 (instead of the default 2), but doing so turns off all warnings, which I would like to continue to see.

Can the RDS team add support for log_error_suppression_list in MySQL 8 parameter groups please? Or is there another solution to prevent logs from filling up with the deprecation warnings?

  • Is there a solution for this yet? Same issue, it's destroying logging.

已提問 9 個月前檢視次數 5524 次
12 個答案
4

We have the same problem. The error logs aren't usable anymore. RDS team: please add support for log_error_suppression_list in MySQL 8 parameter group

已回答 6 個月前
2

This is still an ongoing issue with the 8.0.35 release..

george
已回答 4 個月前
  • Set engine parameter log_error_verbosity to 1 to suppress all warnings (From AWS Support) - I made the change and verified this on our test instance

2

Also having the same issue after updating user credentials to use caching_sha2_password. I wonder if it's related to the rdsadmin account still being set to mysql_native_password, which I don't think we can update. It is unclear whether rdsadmin may be getting used by AWS for duplication, monitoring, etc.

Hobbes
已回答 8 個月前
2

We would also like to see support added for this parameter, especially as the rdsadmin account does not support the caching_sha2_password setting and our logs have a good number of warning messages related to the deprecated authentication plugin.

已回答 7 個月前
2

We're having the same problem, as over 7million alarms are being logged in Cloudwatch each month, that's burning the AWS bill badly.

已回答 5 個月前
2

Just spoke with AWS and they mentioned that "I would like to let you know that our development team is aware of this limitation and there is already plan in place to have "default_authentication_plugin" modifiable in the future. Currently, we are unable to provide ETA when this will be done, however, as soon as its gets released, it will be publicly announced in either one of the following links noted below".

AWS RDS Blog: https://aws.amazon.com/blogs/aws/category/amazon-rds/ AWS RDS forum: https://forums.aws.amazon.com/forum.jspa?forumID=60 What's new blog: https://aws.amazon.com/new/

CrisS
已回答 4 個月前
2

Can the RDS team add support for log_error_suppression_list in MySQL 8 parameter groups please?

Rod
已回答 4 個月前
2

I'm about to update my Mysql 5 RDS instance to Mysql 8, given that now Mysql 5 will only be supported via extended support, which for my usage is x3-x4 the price of my current RDS bill.

We need a way to remove the warning message but also a way to configure the mysql_native_password in the related default group so everyone impacted has multiple choices at hand to ease their migration process.

I believe support for similar needs will rise until February 24th, when newcomers start to work on it.

nyman
已回答 4 個月前
1

Same issue.

My environment is: Wordpress 6.4.2 / php-fpm 8.2 and Mysql 8.0.35. I've change the field "plugin" on users table from "mysql_native_password" to "caching_sha2_password" and warning logs still reporting. Hope a deploying for this log_error_suppression_list feature.

profile picture
已回答 3 個月前
1

The absence of support for log_error_suppression_list and default_authentication_plugin is a significant inconvenience.

To address this issue, we've disabled automatic minor version upgrades on the majority of our databases. However, for those left enabled for testing purposes, the warning surfaced in logs following the upgrade from 8.0.33 to 8.0.35. Oracle's decision to log this warning at every login poses a substantial challenge, particularly for high-traffic databases.

Presently, the available options are either setting log_error_verbosity to 1 to suppress all warnings from being logged, or ensuring that the upgrade does not go beyond version 8.0.33.

Code changes and updates to users in the database to use the new authentication plugin will not fully resolve the issue due to the absence of default_authentication_plugin support.

AWS must promptly notify customers about this issue due to the restricted workaround options, or address it accordingly. Failure to address this could result in unforeseen high bills and complications in diagnosing other issues triggered by warnings now obscured by this particular warning.

已回答 3 個月前
1

The issue still continues.

We've recently upgraded MySQL Engine from 5.7.44 to 8.0.36 (April 22, 2024, 21:00, UTC). And I still got the same log.

2024-04-24T08:10:00.229029Z 8097847 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'

已回答 23 天前
0

Has anyone upgraded to .36 ? Does it fix the [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated errors? I also see that **rdsrepladmin **and **rdsproxyadmin **are still using mysql_native_password. Can these be changed to caching_sha2_password?

MZ
已回答 3 個月前
  • Yes, I've updated one of my databases to 8.0.36 and the log warning persists.

  • I can verify that issue persists with MySQL 8.0.36 in Apr 2024

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南