I had the same problem with Fedora Core 5. I fixed it by removing "/var/lock/subsys/mysqld", then restarting via the Services GUI. After this mysql worked fine.

I believe the file should have been removed automatically by the shutdown script but was not for some reason. I suspect that mysqld crashed without cleaning up rather than a bug but I might be wrong.

OS=Red Hat Enterprise Linux ES release 4
mysql related packages=
[root@MIA ~]# rpm -qa |grep mysql
mysqlclient10-3.23.58-4.RHEL4.1
libdbi-dbd-mysql-0.6.5-10.RHEL4.1
mysql-4.1.12-3.RHEL4.1INLD
mysql-server-4.1.12-3.RHEL4.1INLD
mysql-devel-4.1.12-3.RHEL4.1INLD
php-mysql-4.3.9-3.9INLD

After rebooting the machine i am facing the same Timed out error
[root@MIA ~]# /etc/init.d/mysqld start
Timeout error occurred trying to start MySQL Daemon.
Starting MySQL: [FAILED]

And status gives me:
[root@MIA ~]# /etc/init.d/mysqld status
mysqld dead but subsys locked

I checkd the /var/log/mysqld.log which is:

060426 5:14:02 InnoDB: Error: unable to create temporary file; errno: 13
060426 5:14:02 InnoDB: Error: unable to create temporary file; errno: 13
060426 5:14:02 InnoDB: Error: unable to create temporary file; errno: 13
060426 5:14:02 InnoDB: Error: unable to create temporary file; errno: 13
060427 1:39:49 [Note] /usr/libexec/mysqld: Normal shutdown

060427 1:39:49 InnoDB: Starting shutdown...
060427 1:39:53 InnoDB: Shutdown completed; log sequence number 0 1342013
060427 1:39:53 [Note] /usr/libexec/mysqld: Shutdown complete

060427 11:09:53 mysqld ended

060427 11:11:26 mysqld started
/usr/libexec/mysqld: Can't create/write to file '/tmp/ibowZA6D' (Errcode: 13)
060427 11:11:27 InnoDB: Error: unable to create temporary file; errno: 13
060427 11:11:27 [ERROR] Can't init databases
060427 11:11:27 [ERROR] Aborting

060427 11:11:27 [Note] /usr/libexec/mysqld: Shutdown complete

060427 11:11:27 mysqld ended

060427 11:15:53 mysqld started
/usr/libexec/mysqld: Can't create/write to file '/tmp/ibk4gLG1' (Errcode: 13)
060427 11:15:53 InnoDB: Error: unable to create temporary file; errno: 13
060427 11:15:53 [ERROR] Can't init databases
060427 11:15:53 [ERROR] Aborting

060427 11:15:53 [Note] /usr/libexec/mysqld: Shutdown complete



########################################

Now for restarting mysqld and possible lock problem I removed

/var/lock/subsys/mysqld

as well as
/var/lib/mysql.sock

restared the /etc/init.d/mysqld But facing the same time out error.

The thing I found is after removing both the files are created again. But there is no pid file in my /var/run/mysqld
as it's restart/start is giving time out error.

Any idea ? solution?


thanks and regards
Anuj

Here's what I did to fix this problem:

As a security measure networking in the mysql server has been disabled per
default, only localhost connections will work. This is because the mysql
root user has no password in a default install and that leaves the MySQL
server open for anyone to use.

To do this, open /etc/sysconfig/mysqld and change the line:

MYSQLD_OPTIONS="--skip-networking"
to
MYSQLD_OPTIONS=""

Save and restart mysql. Voila!

All,

I wrangled with this problem for a while, and found a very simple solution that worked.

In the directory /var/lib/mysql/ are files with names similar to: "mysql-bin.000xxxx". Most of them were owned by mysql:mysql, but the latest one (by number) was owned by root:root.

I believe the latest file was written when I executed '/usr/libexec/mysqld --user=root &' to start the DB.

By changing the ownership of the latest mysql-bin.xxx file from root:root to mysql:mysql using 'sudo chown mysql:mysql mysql-bin.xxxx', I was then able to start MySQL with /etc/init.d/mysqld start.

Hope this helps.