Ok, upgraded my server today and seems like the problem is fixed.
Start-Date: 2010-08-02 18:16:54
Upgrade: mysql-client (5.1.41-3ubuntu12.5, 5.1.41-3ubuntu12.6),
mysql-client-core-5.1 (5.1.41-3ubuntu12.5, 5.1.41-3ubuntu12.6),
mysql-server-5.1 (5.1.41-3ubuntu12.5, 5.1.41-3ubuntu12.6), mysql-clie
GerryG
In my.cnf I bind to 127.0.0.1 as I do not need external connections to
mysql for this particular server. Thanks for the reasoning and posts.
Will
--
Upstart does not successfully start mysql on boot
https://bugs.launchpad.net/bugs/610085
You received this bug notification because you are
GerryG, you mention this but I wanted to confirm that it worked for me.
I changed /etc/init/mysql.conf
start on (net-device-up
and local-filesystems
and runlevel[2345])
stop on runlevel [016]
to
start on (net-device-up IFACE=lo and local-filesystems)
stop on runlevel [016]
T
I believe this thread is relevant:
http://ubuntuforums.org/showthread.php?t=1470738
Their solution is not adequate for me because I do not wish to bind
mysql to eth0.
--
Upstart does not successfully start mysql on boot
https://bugs.launchpad.net/bugs/610085
You received this bug notification b
Public bug reported:
After upgrading from 9.10 to 10.4 mysql no longer starts on boot.
Manually running start mysql starts the server just fine. However, this
is not an option because this is a production server. As a workaround I
disabled the upstartlink in /etc/init.d for mysql and copied the o
