Home / server / Questions / 108790
Accepted
Bart B
Asked: 2010-02-03 08:20:00 +0800 CST

What Could be Causing MySQLD to be very very slow to start but give no errors?

  • 772

I have a brand new server running CentOS 5 with 16 cores and 20GB of RAM. In case it's important the machine is a Xen para-virutalised guest, but it's the only guest on the server and the server has 32 cores and 48GB of RAM.

When I issue:

service mysqld start

I get a timeout and it says it failed. However, if I wait about 45 seconds longer the server then comes up. There are no errors listed in the mysqld log file.

I've never seen mysqld behave like this before, and it can't be that it doesn't have enough resources in this case!

Any ideas where I can even begin to debug this since there are no error messages?

Thanks,

Bart.

linux mysql centos5

1 Answers

  1. Best Answer

    Run mysqld from the commandline and strace it.

    ps -efL | grep mysql

    to see what arguments the init script is passing to mysqld.

    Then:

    service mysqld stop

    Then:

    strace -o /tmp/mysqld.out /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --socket=/var/lib/mysql/mysql.sock

    In another console:

    tail -f /tmp/mysqld.out

    Cheers

    • 1