MySQL Bugs: #69160: character set warning when using ssl

Bug #69160	character set warning when using ssl
Submitted:	6 May 2013 19:56	Modified:	19 Aug 2014 17:47
Reporter:	Franjo Markovic	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Errors	Severity:	S3 (Non-critical)
Version:	5.6.13	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I'm getting the following warning in .err file on any new connection to the database, but only when using ssl connection:

 [Warning] Client failed to provide its character set. 'utf8' will be used as client character set.

This started with 5.6.11 - did not happen on 5.6.10 (or any prior version).
If I don't use SSL connection, warning is not reported (whether or not I set "CharSet=xxx" in connection parameters). But when I use SSL, I get this every time (again, regardless of "CharSet" parameter existence or its value).

How to repeat:
Connect to database using .net client, and ssl connection

Suggested fix:
do not provide unnecessary warning

Thank you for the bug report. Please provide your my.cnf . Thanks.

Here are the contents of my.ini file (on windows). I forgot to mention that I get the same behavior on my Mac OSx server installation as well.

[client]
port=3306

[mysql]
default-character-set=utf8

[mysqld]
port=3306
basedir="G:/Program Files/MySQL/MySQL Server 5.6/"
datadir="B:/MySQL/data56/Data/"
character-set-server=utf8
default-storage-engine=INNODB
default-tmp-storage-engine=INNODB
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
max_connections=100
query_cache_size = 60M
table_open_cache=256
tmp_table_size=18M
thread_cache_size=8

#*** MyISAM Specific options
myisam_max_sort_file_size=100G
myisam_sort_buffer_size=35M
key_buffer_size=25M
read_buffer_size=64K
read_rnd_buffer_size=256K
sort_buffer_size = 252K
join_buffer_size = 64M

#*** INNODB Specific options ***
innodb_data_home_dir = "b:/MySQL/data56/"
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size = 145M
innodb_log_file_size = 170M
innodb_thread_concurrency=18

ssl-key = "E:/eclipse/db code/cert/server-key.pem"
ssl-cert = "E:/eclipse/db code/cert/server-cert.pem"
ssl
ssl-ca = "E:/eclipse/db code/cert/ca-cert.pem"
query_cache_type = 1

Thank you for the feedback. I couldn't repeat when connecting with mysql client (I don't have a .net client application to test) please check with mysql client. Thanks.

A sample .Net client application (with complete source code)

Attachment: MySQLNetTestClient.zip (application/x-zip-compressed, text), 268.14 KiB.

One more detail I have noticed (may make testing with an app I just uploaded easier): if you just turn on "SSL Mode" only (equivalent to just adding "SSL Mode=Required" in connecting string), without any other ssl parameters, you would still connect ok (without SSL), but the server will already generate the warning about charset.
And another note - .net connector by default uses connection pooling, so you don't change any connection parameters and just disconnect and connect again, you won't get another server warning, as the connector just reused the same connection (did not really disconnect and reconnect).

Please check with 5.6.12. Thanks.

No improvement with neither 5.6.12 nor 5.6.13

I'm getting the same warning in my error log for every single connection to the database, but we are not using SSL. Server version is 5.6.14. Using MySQL ODBC 5.2 driver to connect. I do not specify a collation on the ODBC DSN connection.

I came across this because we're having issues where our websites losing the ability to connect to the database. This is the only message in the log and it happens several times per second. Starting to wonder if we're losing connections due to the inability of MySQL to keep up managing read/writes on the log file.

Duplicate of bug: http://bugs.mysql.com/bug.php?id=72543 already verified.