Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm trying to track down a process that kills my mysql server on my CentOS box.

I have the following setting in /etc/syslog.conf:

*.*;mail.none;authpriv.none;cron.none /var/log/messages

I assume that this should cause all messages (including kernel messages) to be logged to /var/log/messages, except for authpriv, mail and cron messages.

Yet, when I view /var/log/messages, I don't see any kernel messages that appear to be killing the server.

Here are the full contents of the /etc/syslog.conf file:

# Log anything (except mail) 
# Don't log private authentication messages!
*.*;mail.none;authpriv.none;cron.none           /var/log/messages

# The authpriv file has restricted access.
authpriv.*                                              /var/log/secure

# Log all the mail messages in one place.
mail.*                                                  -/var/log/maillog

# Log cron stuff
cron.*                                                  /var/log/cron

# Everybody gets emergency messages
*.emerg                                                 *

# Save news errors of level crit and higher in a special file.
uucp,news.crit                                          /var/log/spooler

# Save boot messages also to boot.log
local7.*                                                /var/log/boot.log

I have restarted syslog, but it makes no difference.

Any ideas?

share|improve this question
One possibilty would be nothing is killing your mysqld. It simply crashes because of a bug or corrupted data. –  lsmooth Dec 3 '13 at 16:35
@lsmooth has probably right. If yes, somewhere in /var/log you should see the messages of your mysqld. If you can't solve the problem with this, come back and edit the mysqld messages into your question. –  Peter Horvath Dec 3 '13 at 18:09
Well, I had asked this question here: dba.stackexchange.com/questions/54200/… and I had received an answer that with the log entries that I was getting in /etc/my.cnf, that it was likely that something was killing mysql. So I really don't know what to believe at this point. –  Tola Odejayi Dec 3 '13 at 18:16
Do you have anything in dmesg? If the process was killed by the kernel you should see that in there. If not you might want to enable core-dumps and see what happened. –  lsmooth Dec 3 '13 at 20:08
Nothing in dmesg, I'm afraid. This just gets weirder and weirder. I'll enable core-dumps and let you know what happens. Thanks! –  Tola Odejayi Dec 3 '13 at 23:22

Your Answer


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

Browse other questions tagged or ask your own question.