MySQL does not start with utf8 options

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/958120/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in mysql-server-5.5.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Status changed to 'Confirmed' because the bug affects multiple users.

I'm just trying to setup a new TYPO3 instance on a freshly installed VM system Ubuntu precise x64.
After appending this line:

: default-character-set=utf8

in my.cnf (in [mysqld] sect) the mysql server doesn't start anymore. The goal was to get the tables created by the TYPO3 installer in collation utf8_general_ci instead of utf8_swedish_ca.

This worked in 10.04.

What can be done to get this working in 12.04?
Why doesn't the mysql server start anymore when adding this line?

Michael

default-character-set has been remove in mysql 5.5.3. Use character-set-server instead.

Florian:

Well, this was on 5.5.20 and not 5.5.3

To me this one is cleared. It was a wrong collation in the database. Deleting the user, it's db and recreating it solved the problem. I took these settings in my.cnf:

init_connect='SET collation_connection = utf8_general_ci'
init_connect='SET NAMES utf8'
character-set-server=utf8
collation-server=utf8_general_ci
skip-character-set-client-handshake

I ran into this issue and asked a question on askubuntu.com: http://askubuntu.com/questions/127264/installed-12-04-cant-start-mysql-mysql-respawning-too-fast-stopped/129143#129143

ran into this issue in a 12.04 upgrade, my conf is spread across include files based on usage.

I had this for 5.1 (note the two server settings):

/etc/mysql/conf.d$ cat charset.cnf
[mysqld]
collation-server = utf8_unicode_ci
character-set-server = utf8
default-character-set=utf8

[client]
default-character-set=utf8

sudo mysql service start - this would hang until sending a Ctrl+C

Changing to this allowed mysql to start, I guess the client entry is Ok.

/etc/mysql/conf.d$ cat charset.cnf
[mysqld]
collation-server = utf8_unicode_ci
character-set-server = utf8

[client]
default-character-set=utf8

Bit of a tough one, It's possible mysql (the vendor) issued notices about deprecated configuration but it would be good if the service start would not hang and instead issue a warning and die with log messages so a sysadmin knows what's happening.

I checked logs (syslog, mysql error log) and nothing showed up, thinking AppArmor was the issue - which has happened before - I uninstalled that to test but no cigar. Reinstalled and the same issue.

If you hit this issue in a 12.04 upgrade, try out the charset conf change above.

Can somebody who is affected please attach /var/log/mysql* to the bug report? Also just type 'sudo /usr/sbin/mysqld' and paste the output. Its not clear to me what exactly is failing, but I do think the fail is probably logged somewhere.

All `sudo mysqld` gives is:

    120813 7:28:50 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
    120813 7:28:50 [ERROR] Aborting
    120813 7:28:50 [Note] /usr/sbin/mysqld: Shutdown complete

/var/log/mysql.err and tail /var/log/mysql.log are empty because mysqld fails to start (for my version of this problem).

syslog has:

Aug 13 07:22:29 AlSSD kernel: [ 1898.934344] init: mysql main process (5335) terminated with status 1
Aug 13 07:22:29 AlSSD kernel: [ 1898.934403] init: mysql main process ended, respawning
Aug 13 07:22:30 AlSSD kernel: [ 1899.947461] init: mysql post-start process (5336) terminated with status 1
Aug 13 07:22:30 AlSSD kernel: [ 1899.984589] init: mysql main process (5363) terminated with status 1
Aug 13 07:22:30 AlSSD kernel: [ 1899.984649] init: mysql main process ended, respawning
Aug 13 07:22:31 AlSSD kernel: [ 1900.997748] init: mysql post-start process (5364) terminated with status 1
Aug 13 07:22:31 AlSSD kernel: [ 1901.027165] init: mysql main process (5391) terminated with status 1
Aug 13 07:22:31 AlSSD kernel: [ 1901.027185] init: mysql respawning too fast, stopped

Because my original failure started with a syslog about apparmor deny, I disabled apparmor with `sudo service apparmor teardown`, but that left me with the messages above during the failed starts.

Could be related to the fact that for me / (where mysqld would load from) is mounted on an an SSD, but /var, /home, and /tmp (where presumably mysqld would create database files) are on an HD.

why not add by default utf8
and debian sleep more 5 years
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321505

I think this sounds like a reasonable feature request to track with upstream. I've filed: http://bugs.mysql.com/bug.php?id=71659

default utf-8 would be good IMHO.