Fedora Account System
Red Hat Associate
Red Hat Customer
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Description of problem: MySQL fails to start: [root@ashley ~]# /etc/init.d/mysqld start Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED] And the following is in the /var/log/mysqld.log: [root@ashley ~]# tail -f /var/log/mysqld.log to the [mysqld] section of init parameters in your my.cnf or my.ini. If you want to use InnoDB tables, add to the [mysqld] section, for example, innodb_data_file_path = ibdata1:10M:autoextend But to get good performance you should adjust for your hardware the InnoDB startup options listed in section 2 at http://www.innodb.com/ibman.html 050629 22:53:59 /usr/libexec/mysqld: Table 'mysql.host' doesn't exist 050629 22:53:59 mysqld ended Version-Release number of selected component (if applicable): mysql-server-3.23.58-16.FC3.1 How reproducible: Always Steps to Reproduce: 1. /etc/init.d/mysqld start 2. 3. Actual Results: Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED] Expected Results: MySQL should have started up OK Additional info:
I think this is a duplicate of bug #141062, although that was supposedly worked around in mysql-3.23.58-14. Did you perhaps update from an earlier package after having the database startup failure? If so, I think the broken installation is still there. Try rm -rf /var/lib/mysql/* and then see if it will start. Also make sure you are using a reasonably up-to-date selinux-policy-targeted package.
OK, I have removed everything in /var/lib/mysql. [root@ashley ~]# /etc/init.d/mysqld start Initializing MySQL database: [ OK ] Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This time, tail -f /var/log/mysqld.log returns: 050630 22:31:03 mysqld started Cannot initialize InnoDB as 'innodb_data_file_path' is not set. If you do not want to use transactional InnoDB tables, add a line skip-innodb to the [mysqld] section of init parameters in your my.cnf or my.ini. If you want to use InnoDB tables, add to the [mysqld] section, for example, innodb_data_file_path = ibdata1:10M:autoextend But to get good performance you should adjust for your hardware the InnoDB startup options listed in section 2 at http://www.innodb.com/ibman.html /usr/libexec/mysqld: ready for connections And, mysqld seems to be running... ps -ef | grep mysql root 6804 1 0 22:22 pts/3 00:00:00 /bin/sh /usr/bin/safe_mysqld --defaults-file=/etc/my.cnf --pid-file=/var/run/mysqld/mysqld.pid mysql 6832 6804 0 22:22 pts/3 00:00:00 /usr/libexec/mysqld --defaults-file=/etc/my.cnf --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-locking It's interesting that the startup script still fails to run although the daemon is actually running ok. And this is a brand new install of MySQL, not from an upgrade. Here is my system configurations: [bwoo@ashley ~]$ rpm -q mysql mysql-3.23.58-16.FC3.1 [bwoo@ashley ~]$ rpm -q selinux-policy-targeted selinux-policy-targeted-1.17.30-3.15 Thanks, Brian
I have the same symptoms on Fedora Core 1, if that helps. But as you say, the daemon does actually start and everything is fine after that so I haven't been worrying about it. [root@gingham mysql]# service mysqld start Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED] [root@gingham mysql]# service mysqld status mysqld (pid 30187) is running...
The start script basically does this to see if MySQL is up yet: /usr/bin/mysqladmin -uUNKNOWN_MYSQL_USER ping echo $? What happens if you try that by hand?
In Fedora Core 1 the command being used is: /usr/bin/mysqladmin ping I found this website: http://www.siliconvalleyccie.com/linux-adv/mysql.htm#_Toc105342556 and followed it's directions to add "-u $RANDOM" to the ping command, and now everything works just great. I guess the username part was added since FC1. Note that the problem does not occur at bootup, just on restarts of the daemon.
i think i found a problem [root@child ~]# diff ./mysqld /etc/init.d/mysqld 81c81 < RESPONSE=`/usr/bin/mysqladmin -uUNKNOWN_MYSQL_USER ping 2>&1` && break --- > RESPONSE=`/usr/bin/mysqladmin -uUNKNOWN_MYSQL_USER -S $socketfile ping 2>&1` && break
It works after I cleaned the mysql directory under /var/lib... but thanks guys.
OK, in that case I'm going to assume this is the same problem as bug #141062. Thanks for getting back on that. *** This bug has been marked as a duplicate of 141062 ***