Podcast: Duplicate Indexes in MySQL
In this podcast, we’ll explore the issue of duplicate indexes in MySQL; including redundant index, foreign keys, left-prefixed secondary index /w primary key, and how to tackle the issue at…
MySQL Podcast – Practical Learning & Training
Hello, readers! I’m excited to announce the launch of my latest project: a dedicated MySQL Podcast! As a long-time MySQL enthusiast with extensive hands-on experience in database management, I understand…
MySQL Change Buffer – What When and FAQ
In the world of database management, efficiency is key. MySQL’s change buffer is a powerful feature that helps optimize how secondary index changes are managed. The idea of introducing a…
Understanding Return Codes of pt-upgrade: A quick guide
Interpreting the results and exit codes of your upgrade tests is essential for assessing the process’s outcome. In this blog, we’ll explore the significance of pt-upgrade return codes and how…
Troubleshooting MySQL: Encryption can’t find Master Key
If you’ve encountered the “Encryption can’t find master key” error while starting MySQL, you’re likely facing issues with the keyring plugin. I recently faced a similar issue on my server,…
MySQL 8 upgrade may fail using checkForServerUpgrade
These days MySQL consultants around me are busy assisting with MySQL 8 upgrades for those who couldn’t board the train before EoL.I was recently involved in one of the MySQL…
2 responses to “MySQL 8 upgrade may fail using checkForServerUpgrade”
What about this one:
2024-03-13T03:10:59.782280Z 55 [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’
Hi Ashok,
The error clearly says that “mysql_native_password is deprecated” meaning we need to start using the new hashing algorithm of caching_sha2_password.
We can change the passwords of existing users with
ALTER USER ‘user’@’host’ IDENTIFIED WITH caching_sha2_password BY ‘password’;
Ensure that new users are created using new auth plugin and we can adjust the default auth plugin in my.cnf:
default_authentication_plugin=caching_sha2_password
If you want to skip making this change and just want to stop logging these warnings from filling your error log you can make use of log_error_suppression_list config.
set global log_error_suppression_list =’MY-013360′;
let me know how it goes.
Ref:
1. https://dev.mysql.com/doc/mysql-security-excerpt/8.3/en/sha256-pluggable-authentication.html
2. https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_log_error_suppression_list