MySQL 9.04. > 9.10 problem

[jdsampayo]

I also have the same problem,

For me, it solved:

1.- renaming my.cnf
2.- #aptitude reinstall mysql
3.- restoring my.cnf
4.- removing 'bind-address' option of my.cnf
5.- #service mysql restart

[vikonen]

After struggling with it for a LONG time, playing with apparmor setting etc., I had to go all the way; removing mysql-server & mysql-common with purge option (+OpenOffice etc. dependencies).

Also had to rm -r /etc/mysql , /var/lib/mysql , /var/log/mysql
and after all this, reinstall all. Finally, Ubuntu managed to create a new my.cnf under /etc/mysql .
Database started up nicely, and I noticed the weirdest thing:
after seeing the error at mysql startup
"/etc/init.d/mysql: line 123: /etc/mysql/debian-start: No such file or directory"
I realised that the complete reinstall made the /etc/mysql/debian-start disappear, and suddenly everything works.
I suppose that file had not been properly updated in the upgrade from 9.04 -> 9.10 .
Next time: fresh install to 10.04 ...

[phillw]

After struggling with it for a LONG time, playing with apparmor setting etc., I had to go all the way; removing mysql-server & mysql-common with purge option (+OpenOffice etc. dependencies).

Also had to rm -r /etc/mysql , /var/lib/mysql , /var/log/mysql
and after all this, reinstall all. Finally, Ubuntu managed to create a new my.cnf under /etc/mysql .
Database started up nicely, and I noticed the weirdest thing:
after seeing the error at mysql startup
"/etc/init.d/mysql: line 123: /etc/mysql/debian-start: No such file or directory"
I realised that the complete reinstall made the /etc/mysql/debian-start disappear, and suddenly everything works.
I suppose that file had not been properly updated in the upgrade from 9.04 -> 9.10 .
Next time: fresh install to 10.04 ...

Next Time, tasksel

http://forum.phillw.net/viewtopic.php?f=4&t=4

Although, my LAMP from 9.04 --> 9.10 went sweet.

You know it makes sense

Regards,

Phill.

[kpm]

I simply started removing option from my.cnf until it came up.
I found out that skip-bdb is not a valid option anymore, and it was there by default on previous mysqls so you might want to delete that one.

Thank you! This did it for me!

[Socawarrior]

I simply started removing option from my.cnf until it came up.
I found out that skip-bdb is not a valid option anymore, and it was there by default on previous mysqls so you might want to delete that one.

I followed the recommendation above, but it still didn't work for me. I ended up with a different message along the lines of:

--------------------------------------------------------------------------
ERROR 1577 (HY000) at line 1: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
--------------------------------------------------------------------------

I saved a copy of my functioning my.cnf file prior to the update, and I DIFFed it with the new one from Karmic. My findings proved that commenting out:

--------------------------
#myusam-recover = BACKUP
--------------------------

was ALSO necessary.

[MunksterMan2]

I followed the recommendation above, but it still didn't work for me. I ended up with a different message along the lines of:

--------------------------------------------------------------------------
ERROR 1577 (HY000) at line 1: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
--------------------------------------------------------------------------

I saved a copy of my functioning my.cnf file prior to the update, and I DIFFed it with the new one from Karmic. My findings proved that commenting out:

--------------------------
#myusam-recover = BACKUP
--------------------------

was ALSO necessary.

This worked for me, but I should note you have it mis-spelled.

So, for the newcomers... to fix this, comment off these 2 lines in /etc/mysql/mysql.cnf then reboot:

skip-bdb

myisam-recover = BACKUP

[Leo_Luz]

I tried the recommendations about "my.cnf" and didn't work. I not tried to remove mysql-common because of all dependencies that needs to be removed too.

So, I opened the Synaptic Package Manager and saw that was installed "mysql-server-core-5.1", but not the "mysql-server-5.1".
I marked "mysql-server-5.1" for installation and that was an advice that "mysql-server-5.0" should be removed before install the 5.1

Well, I installed mysql-server-5.1, removed mysql-server-5.0 and mysql worked fine after reboot.