Comment 3 for bug 1413620
Revision history for this message
| Mario Splivalo (mariosplivalo) wrote Re: Error after reboot: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) | #3 |
Hi.
Can you provide us with the mysql logs (.err files residing in mysql datadir) too? This looks like a race condition (mysql was not up when juju wanted to run config_change hook on it), but we'll need more info to investigate. It would be nice to have 'juju status' output from before you did 'juju resolved', do you, maybe, still have it saved? Also, if you could bundle (in a .zip or similar archive) all the log files from the failed unit, that would also help (as allmachines.log is a bit hard to parse).
Have you tried reproducing this issue? If so, does it fail every time?
Do you maybe have a juju delployer configuration file that you can share (assuming that you did use juju deployer to deploy your stack)?
There is a updated version of the percona-cluster charm available, it might be wise to upgrade the current charm version (make sure you have your mysql databases backed up, just in case!).