This topic discusses how to use the
mysql-diag tool in MySQL for Pivotal Cloud Foundry (PCF).
mysql-diag relays the state of your MySQL service and suggests steps to take in the event of a node failure. In conjunction with Pivotal Support, this tool helps expedite the diagnosis and resolution of problems with MySQL for PCF.
In MySQL for PCF 1.9.0 and later, the
mysql-diag tool is automatically installed and configured. If you are on a prior version, select the documentation for your version of MySQL for PCF.
If this is your first time using
mysql-diag, follow the instructions within the Prepare to Use the BOSH CLI topic. If you have completed this step in a prior use of
mysql-diag, move directly to Step 2.
Select either Elastic Runtime or MySQL for PCF as your deployment to troubleshoot. Perform the steps detailed in the Select a Product Deployment to Troubleshoot topic.
bosh sshfrom the Ops Manager VM and select the mysql-monitor node from the list. Perform the steps detailed in the Select a Product Deployment to Troubleshoot topic.
Once on the
mysql-monitorVM type the following command to run
MySQL for PCF 1.9.0 and later will have the
mysql-diag-agent present. Older versions of MySQL for PCF do not have the
mysql-diag-agent. If the
mysql-diag-agent is not available, your output from the
mysql-diag tool will not include the percentage of Persistent and Ephemeral Disk space used by a Host.
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 cluster:
mysql-diag command returns the following message if your canary status is unhealthy:
Checking canary status...unhealthy
In the event of a broken cluster, running
mysql-diag outputs actionable steps meant to expedite the recovery of that cluster. Below is a sample
mysql-diag output after the tool identified an unhealthy cluster: