Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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
denis@australia:~$ cat /etc/issue
Ubuntu 12.04.1 LTS \n \l

denis@australia:~$ chkconfig --list mysql
mysql                     0:off  1:off  2:off  3:off  4:off  5:off  6:off

But mysql runs on the startup anyway.

share|improve this question
up vote 3 down vote accepted

I'm guessing that the issue here is that checkconfig checks the old style init scripts, and you have a new upstart init script.

Go to /etc/init/mysql.conf and change start on (net-device-up and local-filesystems) to start on runlevel [!0123456] If you need to start it manually service mysql start will do the trick. This thread on ubuntu forums goes into some depth on the process

A bit more background - chkconfig works on old school init scripts - they're known as /etc/rc scripts, but the form used in ubuntu was /etc/init.d. In order to list scripts - according to this question on AU, the command you should be using instead of chkconfig is initctl list. It will not change runlevels for you like chkconfig would tho.

share|improve this answer
Every time I get used to how Linux handles startup, something changes, and it never gets easier to understand. (Sorry, nothing to do with your post, I'm just getting frustrated.) – pjmorse Oct 16 '12 at 1:28
I hear ya. For many years, init.d was the way. Now we also have upstart and systemd to worry about. I only know how to use upstart cause I had issues with it before and ended up learning it. Docs were crappier then ;p. – Journeyman Geek Oct 16 '12 at 1:30

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.