MySQL Bugs: #94391: MySQL error - using method 'mysql_native

Bug #94391	MySQL error - using method 'mysql_native_password' failed
Submitted:	19 Feb 2019 6:04	Modified:	15 Apr 2019 8:09
Reporter:	Hardik Shah	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S1 (Critical)
Version:	5.6.19-log	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	connector, MySQL

Description:
Hello All,

We have recently found this error increasing in our ASP.NET MVC Application. We are connecting to MySQL using MySQL DLL (6.8.3.0) and our MySQL version is 5.6.19-log. Just to update you all, we have different application and database server connecting through Internet.

We have tried all the options suggested in bug report below.
https://bugs.mysql.com/bug.php?id=76597

1. Restarted the Application Server
          - This resolved error for 2-3 days, but again after that it started appearing as around 100 per day.

2. SSL changes
          - Done both Connection String change in Web.Config and Group Policy change. But issues remains same.

3. skip-name-resolve
          - Again no difference.

4. read_net_timeout and write_net_timeout
          - changing value of this variables - no difference

Please suggest us as this has started becoming a random issue which is not resolvable. Also, this error appears only for few seconds, but at that time the MySQL connections are in like below.

unauthenticated user  - <IP> - <DB> - Connect - NULL - Reading from net - NULL
unauthenticated user  - <IP> - <DB> - Connect - NULL - Reading from net - NULL
unauthenticated user  - <IP> - <DB> - Connect - NULL - Reading from net - NULL
unauthenticated user  - <IP> - <DB> - Connect - NULL - Reading from net - NULL
unauthenticated user  - <IP> - <DB> - Connect - NULL - Reading from net - NULL
unauthenticated user  - <IP> - <DB> - Connect - NULL - Reading from net - NULL

Once it releases the connection, we get below error messages.
Authentication to host <IP> for user <USER> using method 'mysql_native_password' failed with message: Reading from the stream has failed.

Please suggest us some solution here which can fix this bug.

Apologies for creating one more bug, but we are not able to find solution to this and hence wanted someone to respond to us. It would be great help if someone can update us with solution for similar issue they faced.

Thanks
Hardik

How to repeat:
As this error can appear at any point of time, there is no such process through which we can repeat the error.

Our C# .Net application connect the MySQL using connection string like below.

"server=<IP>; user id=<USER>; password=<PASSWORD>; database=<DB>; pooling=false; port=<PORT>;"

We just use the same code to connect to MySQL.

var con = new MySQLConnection(<CONNSTRING>);
con.Open();
//DO CALL STORED PROCEDURE TO USE SELECT 
con.Close();

This is how we get the error.

Suggested fix:
We tried most of the solutions suggested in below link.
https://bugs.mysql.com/bug.php?id=76597

Please provide a console client application as test case which is repeatable on you side.

We cannot repeat the case by our selves, as this error is being generated randomly anytime while making database connection. It will work for few minutes, then will start suddenly holding the connection and throwing the error, and then again after few minutes it will be working fine.

We cannot be sure on how can we repeat that error due to it's being random timing error.

Thanks
Hardik

Thank you for the feedback. We have problems for further process without a repeatable test also are you using a server version 5.6.19? if yes is quite older why you don't test against most released version? current is 5.6.43!.

Hi Miguel,

Thank you for your quick update. We cannot change the MySQL Version that easily with our application, however wanted to ask you that currently we are using MySQL .Net Connector Version (6.8.3).

Was going through the various other versions available and there I found below line written.

"MySQL Connector/NET 8.0 is highly recommended for use with MySQL Server 8.0, 5.7, 5.6, and 5.5. Please upgrade to MySQL Connector/NET 8.0."

So, wanted to confirm whether we should also move to the MySQL Latest Stable Connector (8.0.15) and verify whether it is resolved or not.

Thanks
Hardik

Thank you for the feedback. To check with the latest released version is the recommend way mainly when there isn't a repeatable test case.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".