Sign up ×
Server Fault is a question and answer site for 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. –  peterh Dec 3 '13 at 18:09
Well, I had asked this question here:… 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

1 Answer 1

Without going into speculation on your crashes, I can help with syslog.

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

You dont need to list any facilities or priorities if you use asterisks. This is purely pedantic, but just an fyi. If you really want all messages going to /var/log/messages, you would use:

*.* /var/log/messages

Ensure that you are actually running "syslog" rather than "rsyslog". The config you are quoting is based on the usage of the older "syslog" that was default in CentOS 5 and earlier. You don't mention which version of CentOS you are on, but if that happens to be CentOS 6, then you are likely running rsyslog. Rsyslog uses /etc/rsyslog.conf and /etc/rsyslog.d/*.conf Both of those can not be running at the same time or you may not see messages. The first one to bind to the syslog port will win.

To test syslog for kernel messages, use the following:

 logger -i -p kern.crit "This is a syslog test"

If you see your test message, then syslog is working and mysqld is crashing on it's own, as lsmooth mentioned.

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.