As shown in http://ubuntuforums.org/showthread.php?t=1470738 many people are effected by this, if mysqld must be bound to an interface other than "lo". Most of the problems appear to results from a timing issue, where upstart attempts to start the mysqld daemon before the specific network interface is available. Towards this, another posted workaround changes the condition in /etc/init/mysql from: start on (net-device-up and local-filesystems) to start on (net-device-up IFACE=eth0 and local-filesystems)
Obviously, this is not good because it conditions starting mysqld on a specific interface, and any future changes there would break unless you remembered to change this script. A better solution would be a conditional that required ALL network interfaces to be up before starting mysqld. While this might impose a slight additional delay in some systems, it would be robust. I was unable to find such a conditional. -- Upstart does not successfully start mysql on boot https://bugs.launchpad.net/bugs/610085 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
