Bug #72543 | remove the spam warnings: Client failed to provide its character set | ||
---|---|---|---|
Submitted: | 6 May 2014 5:15 | Modified: | 3 Nov 2014 18:04 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Security: Privileges | Severity: | S3 (Non-critical) |
Version: | 5.6.20 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[6 May 2014 5:15]
Shane Bester
[3 Jun 2014 13:41]
Charles Sheridan
HAProxy's mysql-check option causes this warning as well. A solution for suppressing this warning would be helpful to keep error logs clean.
[30 Sep 2014 12:52]
Bryan Welch
A way to suppress this warning would be appreciated. We upgraded to 5.6.20 and the error logs are now filled with the following message: 2014-09-30 07:36:55 11072 [Warning] Client failed to provide its character set. 'utf8' will be used as client character set. This is making it hard to see any actual issues in the log.
[3 Nov 2014 18:04]
Paul DuBois
Noted in 5.6.23, 5.7.6 changelogs. The server no longer logs the following warnings because they are uninformative: Client failed to provide its character set. 'charset' will be used as client character set.
[12 Feb 2015 12:01]
Laurynas Biveinis
$ git show -s b3373e4 commit b3373e414abe051cb3db5e7eb2125584e173ed72 Author: Venkata Sidagam <venkata.sidagam@oracle.com> Date: Mon Nov 3 22:35:41 2014 +0530 Bug #18708334 REMOVE THE SPAM WARNINGS: CLIENT FAILED TO PROVIDE ITS CHARACTER SET Description: When we try to connect mysql-5.6 server with mysql-4.0 client the error log gets filled with below warning message "[Warning] Client failed to provide its character set. 'latin1' will be used as client character set" Analysis: Since the the client protocol is older than 4.1 and the 4.0 client is not providing the character set while trying to connect to the server. so, the warning message is sent to error log file Fix: Since the warning message is not necessary, we are removing the warning message.