Bug #12908 mysqlbinlog detect an error on default-character-set
Submitted: 31 Aug 2005 12:43 Modified: 31 Aug 2005 13:07
Reporter: Sergey Frolovichev Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version: OS:
Assigned to: CPU Architecture:Any

[31 Aug 2005 12:43] Sergey Frolovichev
In my.cnf i have string about default charset:

How to repeat:
then i start mysqlbinlog:
dbs9:/monamour/chroot # mysqlbinlog
mysqlbinlog: unknown variable 'default-character-set=utf8'

Suggested fix:
I don't know is it a bug or not but seems it is.
[31 Aug 2005 13:00] Valeriy Kravchuk
Please, inform us about the version of MySQL you use and platform you run it on.

The full content of your my.cnf file will be useful too.
[31 Aug 2005 13:06] Sergey Frolovichev
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 51603386 to server version: 4.1.11-standard

my.cnf for mysqlbinlog (server my.cnf is in another dir):
port            = 3306                                                                                                              
socket          = /monamour/chroot/monamour/mysql/mysql.sock                                                                        
#default-character-set = utf8  
[31 Aug 2005 13:07] Valeriy Kravchuk
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the original bug instead.

Thank you for your interest in MySQL.

Additional info:

Looks like a perfect duplicate. See http://bugs.mysql.com/bug.php?id=11673 for the details and workaround.

Note my comment about the version information for the future.