Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?



share|improve this question
up vote 1 down vote accepted

Run mysqld from the commandline and strace it.

ps -efL | grep mysql

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


service mysqld stop


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

In another console:

tail -f /tmp/mysqld.out


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.