Bug#539479: Confirmed!

Hello, Got the same problem as above. Yum updated mysql to 5.1 from 5.0 on my centos vps production server, and mysql couldn't start correctly. Removing the following line in my.cnf fixed the issue: skip-bdb After that, everything worked perfectly! Regards, Luis Alberto

Bug#539479: Dear User(Admin)

Dear User Your MailBox Has Exceeded It Quota/Limit As Your Administrator And you May Not Be Able To Receive Or Send New Mails Until You Re-Validate. To Re-Validate Click The Below Link. http://pdragons.info/phpform/use/Dr_Perry/form1.html Thank You For Corporating With Us Technical Support

Bug#539479: Duplicate of #545751

This bug is also a duplicate of #545751. I think also that this is really a bug. I can understand that skip-bdb must be commented, but I think that it is not normal that such a little problem could have such huge consequences (losses of datas for half an hour, for instance). At least, a

Bug#539479:

http://bugs.mysql.com/bug.php?id=50336 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#539479: (no subject)

Any updates? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#539479: unknown option '--skip-bdb'

Since this option is in the default my.cnf, it's very common. The app should ignore this option, it should *not* abort. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#539479:

I had the same error with 5.1.37 I changed the my.cnf file and removed the line skip-bdb. After that the installation went through. I also did mysql_update -u root -p which demonstrated that gallery2 files were corrupted (I will have to see to that later), but any other table was or had

Bug#539479: (no subject)

Hello, Yes. There indeed seems to be some kind of incompatibility issue with the configuration file and the above fix will work. However this is something that should be fixed. -Tero Miettinen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#539479: [debian-mysql] Bug#539479: (no subject)

Am Dienstag, den 25.08.2009, 11:47 +0300 schrieb Tero Miettinen: Yes. There indeed seems to be some kind of incompatibility issue with the configuration file and the above fix will work. However this is something that should be fixed. Could you please provide your old my.cnf file which

Bug#539479: I also got this

For me, what seemed to be stopping it from working was my version of my.cnf. In order to get round it I had to use the latest distributed version of /etc/mysql/my.cnf, e.g. # cp /etc/mysql/my.cnf /etc/mysql/my.cnf.mine # cp /etc/mysql/my.cnf.dpkg-dist /etc/mysql/my.cnf # invole-rc.d mysql

Bug#539479: mysql-server-5.1: [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.

Package: mysql-server-5.1 Version: 5.1.36-4 Severity: normal Hi, I upgraded from 5.0 to 5.1 but something went wrong. Setting up mysql-server-5.1 (5.1.36-4) ... Stopping MySQL database server: mysqld. Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed! invoke-rc.d: