This problem is seriously harming our production where we never know if MySQL will be functional after a reboot. The problem seems to happen 50% of the time.
Here are some observations when the problem occurs: # status mysql mysql start/running, process 825 # ll /var/run/mysqld/ total 0 drwxr-xr-x 2 mysql root 40 Feb 27 09:28 ./ drwxr-xr-x 18 root root 600 Feb 27 09:35 ../ # ps aux | grep mysql mysql 825 0.0 2.5 624108 52628 ? Ssl 09:27 0:00 /usr/sbin/mysqld root 2040 0.0 0.0 11740 920 pts/0 S+ 09:36 0:00 grep --color=auto mysql # mysqladmin ping mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! ** Summary changed: - mysql fails to start on reboot + mysql does not always create a Unix socket on startup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425995 Title: mysql does not always create a Unix socket on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1425995/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
