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 Helpdesk 192.168.0.1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 small verification that the my.cnf is correct prior to install mysql-server-5.1 should be helpfull. Thanks; Thierry Chich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 already been successfully updated. After this /var/log/daemon.log reports the following mysqld notes: (hostname removed) mysqld: 090901 20:36:47 [Note] /usr/sbin/mysqld: Shutdown complete Sep 1 20:36:47 mysqld: Sep 1 20:36:47 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Sep 1 20:36:48 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Sep 1 20:36:48 mysqld: 090901 20:36:48 [Note] Plugin 'FEDERATED' is disabled. Sep 1 20:36:48 mysqld: 090901 20:36:48 InnoDB: Started; log sequence number 0 76661565 Sep 1 20:36:50 mysqld: 090901 20:36:50 [Note] Event Scheduler: Loaded 0 events Sep 1 20:36:50 mysqld: 090901 20:36:50 [Note] /usr/sbin/mysqld: ready for connections. Sep 1 20:36:50 mysqld: Version: '5.1.37-1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian) Sep 1 20:36:50 /etc/mysql/debian-start[30087]: Upgrading MySQL tables if necessary. Sep 1 20:36:50 /etc/mysql/debian-start[30090]: Looking for 'mysql' as: /usr/bin/mysql Sep 1 20:36:50 /etc/mysql/debian-start[30090]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Sep 1 20:36:50 /etc/mysql/debian-start[30090]: This installation of MySQL is already upgraded to 5.1.37, use --force if you still need to run mysql_upgrade Sep 1 20:36:50 /etc/mysql/debian-start[30097]: Checking for insecure root accounts. Sep 1 20:36:50 /etc/mysql/debian-start[30101]: Triggering myisam-recover for all MyISAM tables That is, all other warnings have gone. The only change I did was to remove skip-bdb. -- Bernhard Kleine bernhard.kle...@gmx.net signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
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 unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 prevented mysqld from starting? Norbert -- 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 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 start You may need to edit /etc/mysql/my.cnf to include your changes from my.cnf.mine of course. Thanks, Yasir No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.45/2284 - Release Date: 08/05/09 18:23:00
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: initscript mysql, action start failed. dpkg: error processing mysql-server-5.1 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-server-5.1; however: Package mysql-server-5.1 is not configured yet. dpkg: error processing mysql-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: mysql-server-5.1 mysql-server E: Sub-process /usr/bin/dpkg returned an error code (1) Aug 1 11:56:02 debian mysqld_safe[4003]: 090801 11:56:02 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb' Aug 1 11:56:02 debian mysqld_safe[4003]: 090801 11:56:02 [ERROR] Aborting Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: 090801 11:56:02 [Warning] Forcing shutdown of 2 plugins Aug 1 11:56:02 debian mysqld_safe[4003]: 090801 11:56:02 [Note] /usr/sbin/mysqld: Shutdown complete Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: Installation of system tables failed! Examine the logs in Aug 1 11:56:02 debian mysqld_safe[4003]: /var/lib/mysql for more information. Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: You can try to start the mysqld daemon with: Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: shell /usr/sbin/mysqld --skip-grant Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: and use the command line tool /usr/bin/mysql Aug 1 11:56:02 debian mysqld_safe[4003]: to connect to the mysql database and look at the grant tables: Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: shell /usr/bin/mysql -u root mysql Aug 1 11:56:02 debian mysqld_safe[4003]: mysql show tables Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: Try 'mysqld --help' if you have problems with paths. Using --log Aug 1 11:56:02 debian mysqld_safe[4003]: gives you a log in /var/lib/mysql that may be helpful. Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: The latest information about MySQL is available on the web at Aug 1 11:56:02 debian mysqld_safe[4003]: http://www.mysql.com/. Please consult the MySQL manual section Aug 1 11:56:02 debian mysqld_safe[4003]: 'Problems running mysql_install_db', and the manual section that Aug 1 11:56:02 debian mysqld_safe[4003]: describes problems on your OS. Another information source are the Aug 1 11:56:02 debian mysqld_safe[4003]: MySQL email archives available at http://lists.mysql.com/. Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4003]: Please check all of the above before mailing us! And remember, if Aug 1 11:56:02 debian mysqld_safe[4003]: you do mail us, you MUST use the /usr/scripts/mysqlbug script! Aug 1 11:56:02 debian mysqld_safe[4003]: Aug 1 11:56:02 debian mysqld_safe[4039]: 090801 11:56:02 [Note] Plugin 'FEDERATED' is disabled. Aug 1 11:56:03 debian mysqld_safe[4039]: 090801 11:56:03 InnoDB: Started; log sequence number 0 43655 Aug 1 11:56:03 debian mysqld_safe[4039]: 090801 11:56:03 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb' Aug 1 11:56:03 debian mysqld_safe[4039]: 090801 11:56:03 [ERROR] Aborting Aug 1 11:56:03 debian mysqld_safe[4039]: Aug 1 11:56:03 debian mysqld_safe[4039]: 090801 11:56:03 InnoDB: Starting shutdown... Aug 1 11:56:04 debian mysqld_safe[4039]: 090801 11:56:04 InnoDB: Shutdown completed; log sequence number 0 43655 Aug 1 11:56:04 debian mysqld_safe[4039]: 090801 11:56:04 [Warning] Forcing shutdown of 1 plugins Aug 1 11:56:04 debian mysqld_safe[4039]: 090801 11:56:04 [Note] /usr/sbin/mysqld: Shutdown complete Aug 1 11:56:04 debian mysqld_safe[4039]: Aug 1 11:56:04 debian mysqld_safe[4055]: 090801 11:56:04 [Note] Plugin 'FEDERATED' is disabled. Aug 1 11:56:04 debian mysqld_safe[4055]: 090801 11:56:04 InnoDB: Started; log sequence number 0 43655 Aug 1 11:56:04 debian mysqld_safe[4055]: 090801 11:56:04 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb' Aug 1 11:56:04 debian mysqld_safe[4055]: 090801 11:56:04 [ERROR] Aborting Aug 1 11:56:04 debian mysqld_safe[4055]: Aug 1 11:56:04 debian mysqld_safe[4055]: 090801 11:56:04 InnoDB: Starting shutdown... Aug 1 11:56:05 debian mysqld_safe[4055]: 090801 11:56:05 InnoDB: Shutdown completed; log sequence number 0 43655 Aug 1 11:56:05 debian mysqld_safe[4055]: 090801 11:56:05 [Warning] Forcing shutdown of 1 plugins Aug 1
