Comments on: MySQL 8.0.34 Upgrade and tons of MY-013360 ‘mysql_native_password’ is deprecated warnings

By: Brandon Checketts

Brandon Checketts — Fri, 28 Mar 2025 19:42:41 +0000

For anybody still seeing this, upgrading to MySQL 8.0.38 effectively fixes this by only logging the warning once

By: Anse

Anse — Fri, 14 Jun 2024 04:29:37 +0000

@velloraposo, your users won’t be able to connect when you just change the mysql.user.plugin field. Your mysql.user.authentication_string needs to be encrypted again, using the new plugin. The correct way is to pass both plugin and password per SQL, like Brandon wrote above:
ALTER user ‘yourusername’@’hostname’ IDENTIFIED WITH caching_sha2_password BY ‘yourpassword’;

By: velloraposo

velloraposo — Tue, 06 Feb 2024 15:40:54 +0000

Hi Brandon,

Thanks a lot for your post. I0ve the 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 an AWS deploying for this log_error_suppression_list feature.

By: Brandon

Brandon — Sun, 07 Jan 2024 01:48:28 +0000

In reply to Tom Wijnroks. Yes, that would be the desired way to prevent this error. Since this instance is hosted on RDS, though, that setting is not currently modifiable. The link to AWS Repost is a request for Amazon to make this setting able to be configured by customers. It looks like it has attracted some attention and may happen soon.

By: Tom Wijnroks

Tom Wijnroks — Fri, 05 Jan 2024 12:13:37 +0000

Have you tried to use ‘log_error_suppression_list’ to supress the specific MY-013360 warning? I tested this on MySQL 8.0.35 by adding the following line in my.cnf (and restarted MySQL):

log_error_suppression_list = “013360”

After this I no longer get the MY-013360 warnings in the error logs. From the docs:

“The log_error_suppression_list system variable applies to events intended for the error log and specifies which events to suppress when they occur with a priority of WARNING or INFORMATION. For example, if a particular type of warning is considered undesirable “noise” in the error log because it occurs frequently but is not of interest, it can be suppressed.”

More information here: https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_log_error_suppression_list

By: Brandon

Brandon — Thu, 07 Dec 2023 17:19:40 +0000

The AWS RePost topic has been upvoted a bit, but no word from the AWS team on if they will implement the proper fix for this. In the mean time, I have logs suppressed and have not updated any other servers past 8.0.33.

By: cw

cw — Thu, 07 Dec 2023 06:12:12 +0000

Thanks for your information,
This continues to happen with RDS MySQL 8.0.35.
did you solve the problem?