Mysql doesn't start at boot

8 posts / 0 new

Topic locked

#1 Sat, 03/12/2011 - 03:54

nils

Mysql doesn't start at boot

Hi!

I have installed Virtualmin 3.83.gpl GPL on Ubuntu Linux 10.04. It works great accept for one little thing: mysql doesn't start correctly when I reboot the server.

I tried to add my own boot up action in webmin to start mysql. It works but the system information in Virtualmin doesn't show the correct status for mysql.

Does anyone know how I can solve this?

Regards, Nils

#2 Sat, 03/12/2011 - 04:45

Locutus

In Ubuntu 10.04, startup actions have mostly been converted to upstart jobs as opposed to /etc/init.d scripts, which Webmin cannot handle yet (I hope the developers will add support for that soon, I already mentioned it a few weeks ago). See if you have a file /etc/init/mysql.conf in your system.

What happens when you do start mysql? Is MySQL actually running? ps aux | grep sql

If not, first thing to check in such cases is always the logs in /var/log.

#3 Sat, 03/12/2011 - 06:22 (Reply to #2)

nils

Yes I have /etc/init/mysql.conf but mysql isn't running after a reboot.

I can't find anything mysql related in the syslog.

#4 Sun, 03/13/2011 - 14:48

Locutus

What happens when you do start mysql?

#5 Mon, 03/14/2011 - 07:56 (Reply to #4)

nils

# start mysql
mysql start/running, process 32178

The status for mysql in virtualmin isn't in sync with the actual status of mysql.

If I stop mysql in virtualmin and start it again mysql starts but the status still says it's stopped. I have to start mysql again to get the right status.

#6 Mon, 03/14/2011 - 11:29

Locutus

So basically it does start okay, but Virtualmin incorrectly reports it as "down"?

Maybe there's a similar issue as I suggested in this thread: http://www.virtualmin.com/node/17521

#7 Tue, 03/15/2011 - 02:48 (Reply to #6)

nils

Actually it's the other way around. Mysql doesn't start and Virtualmin says it's up.

Virtualmin started to report mysql as up after I made a permanent fix to add 127.0.0.1 to the DNS servers at boot. But mysql has never started.

And as I said before Virtualmins status for mysql isn't always correct. It doesn't matter to Virtualmin if I start or stop mysql over ssh.

#8 Wed, 03/16/2011 - 05:45

Locutus

Also in this case, the settings for Virtualmin concerning MySQL PID file might be wrong, or something else might be preventing VM from determining the status of MySQL correctly. You might want to double-check the corresponding settings in Webmin's MySQL module, and if in doubt, turn on Webmin's Debug Logging to see if there are any errors reported by the MySQL module.

Topic locked