Learn how to use the mysql-diag
tool in Ops Manager. mysql-diag
prints the state of your MySQL highly available (HA) cluster and suggests solutions if your node fails. VMware recommends running this tool against your HA cluster before all deployments.
mysql-diag
checks the following information about the status of your HA cluster:
To use the BOSH CLI to run mysql-diag
, do the following:
Obtain the information needed to use the BOSH CLI by doing the procedure in Gather Credential and IP Address Information.
SSH into your Ops Manager VM by doing the procedure in Log in to the Ops Manager VM with SSH for your IaaS.
Log in to your BOSH Director by doing the procedure in Authenticate with the BOSH Director VM.
Identify the VM to log in to with SSH by running the following command:
bosh -e MY-ENV -d MY-DEPLOYMENT vms
Where:
MY-ENV
is the name of your environment.MY-DEPLOYMENT
is the name of your deployment.Record the GUID associated with the mysql-monitor
VM, also known as the jumpbox VM.
SSH into your mysql-monitor
VM by running the following command:
bosh -e MY-ENV -d MY-DEP ssh mysql-monitor/GUID
Where:
MY-ENV
is the name of your environment.MY-DEPLOYMENT
is the name of your deployment.GUID
is the GUID you recorded in the previous step.View the status of your HA cluster by running the following command:
mysql-diag
The mysql-diag
command returns the following message if your canary status is healthy:
Checking canary status...healthy
Here is a sample mysql-diag
output after the tool identified a healthy HA cluster:
View a larger version of this image.
The mysql-diag
command returns the following message if your canary status is unhealthy:
Checking canary status...unhealthy
In the event of a broken HA cluster, running mysql-diag
outputs actionable steps meant to expedite the recovery of that HA cluster. Below is a sample mysql-diag
output after the tool identified an unhealthy HA cluster: