Lerarn about the basic instructions for troubleshooting on-demand VMware SQL with MySQL for Tanzu Application Service.

For information about temporary VMware Tanzu for MySQL service interruptions, see Service interruptions.

Troubleshoot errors

This section provides information on how to troubleshoot specific errors or error messages.

Common services errors

The following errors occur in multiple services:

• Failed installation
• Cannot create or delete service instances
• Broker request timeouts
• Instance does not exist
• Cannot bind to or unbind from service instances
• Cannot connect to a service instance
• Upgrade all service instances errand fails
• Missing logs and metrics
• MySQL Load is high with large number of CredHub encryption keys

Instance provisioning failed: There was a problem completing your
request. Contact your operations team providing the following information: service: redis-acceptance, service-instance-guid: ae9e232c-0bd5-4684-af27-1b08b0c70089, broker-request-id: 63da3a35-24aa-4183-aec6-db8294506bac, task-id: 442, operation: create

Server error, status code: 504, error code: 10001, message: The request to the service broker timed out: https://BROKER-URL/v2/service_instances/e34046d3-2379-40d0-a318-d54fc7a5b13f/service_bindings/aa635a3b-ef6d-41c3-a23f-55752f3f651b

Server error, status code: 502, error code: 10001, message: Service broker error: instance does not exist`

Server error, status code: 502, error code: 10001, message: Service broker error: There was a problem completing your request. Please contact your operations team providing the following information: service: example-service, service-instance-guid: 8d69de6c-88c6-4283-b8bc-1c46103714e2, broker-request-id: 15f4f87e-200a-4b1a-b76c-1c4b6597c2e1, operation: bind

Service instances can also become temporarily inaccessible during upgrades and VM or network failures. See Service interruptions for more information.

Leader-Follower Service Instance Errors

This section provides solutions for the following errands:

• Unable to determine leader and follower
• Both leader and follower instances are writable
• Both leader and follower instances are read-only

$ Unable to determine leader and follower based on transaction history.

$ Both mysql instances are writable. Please ensure no divergent data and set one instance to read-only mode.

Inoperable app and database errors

This section provides a solution for the following errors:

• Persistent Disk is Full
• Cannot Access Database Table

ERROR 1146 (42S02): Table 'mysql.foobar' doesn't exist

Highly available cluster errors

This section provides solutions for the following errands:

• Unresponsive Node in a Highly Available Cluster
• Many Replication Errors in Logs for Highly Available Clusters

WSREP has not yet prepared this node for application use

  unknown error

160318 9:25:16 [Warning] WSREP: RBR event 1 Query apply warning: 1, 16992456
160318 9:25:16 [Warning] WSREP: Ignoring error for TO isolated action: source: abcd1234-abcd-1234-abcd-1234abcd1234 version: 3 local: 0 state: APPLYING flags: 65 conn_id: 246804 trx_id: -1 seqnos (l: 865022, g: 16992456, s: 16992455, d: 16992455, ts: 2530660989030983)
160318 9:25:16 [ERROR] Slave SQL: Error 'Duplicate column name 'number'' on query. Default database: 'cf_0123456_1234_abcd_1234_abcd1234abcd'. Query: 'ALTER TABLE ...'

Failed backups

If an automated backup or a backup initiated from the ApplicationDataBackupRestore (adbr) plug-in fails, verify that the 2345 port from the TAS for VMs to the ODB component is open.

Troubleshoot components

This section provides guidance on checking for and fixing issues in on-demand service components.

BOSH problems

Large BOSH queue

On-demand service brokers add tasks to the BOSH request queue, which can back up and cause delay under heavy loads. An app developer who requests a new VMware SQL with MySQL for TAS instance sees create in progress in the Cloud Foundry Command Line Interface (cf CLI) until BOSH processes the queued request.

Tanzu Operartions Manager currently deploys two BOSH workers to process its queue. Users of future versions of Tanzu Operations Manager can configure the number of BOSH workers.

Configuration

Service instances in failing state

The VM or Disk type that you configured in the plan page of the tile in Tanzu Operations Manager might not be large enough for the Tanzu SQL for VMs service instance to start. See tile-specific guidance on resource requirements.

Authentication

UAA changes

If you have rotated any UAA user credentials then you might see authentication issues in the service broker logs.

To resolve this, redeploy the Tanzu SQL for VMs tile in Tanzu Operations Manager. This provides the broker with the latest configuration.

You must ensure that any changes to UAA credentials are reflected in the Tanzu Operations Manager credentials tab of the VMware Tanzu Application Service for VMs tile.

Networking

Common issues with networking include:

Validate service broker connectivity to service instances

To validate connectivity, do the following:

1. View the BOSH deployment name for your service broker by running:

   bosh deployments
   

2. SSH into the Tanzu SQL for VMs service broker by running:

   bosh -d DEPLOYMENT-NAME ssh
   

3. If no BOSH task-id appears in the error message, look in the broker log using the broker-request-id from the task.

Validate app access to service instance

Use cf ssh to access to the app container, then try connecting to the VMware SQL with MySQL for TAS service instance using the binding included in the VCAP_SERVICES environment variable.

Quotas

Plan quota issues

If developers report errors such as:

Message: Service broker error: The quota for this service plan has been exceeded.
Please contact your Operator for help.

1. Check your current plan quota.
2. Increase the plan quota.
3. Log in to Tanzu Operations Manager.
4. Reconfigure the quota on the plan page.
5. Deploy the tile.
6. Find who is using the plan quota and take the appropriate action.

Global quota issues

If developers report errors such as:

Message: Service broker error: The quota for this service has been exceeded.
Please contact your Operator for help.

1. Check your current global quota.
2. Increase the global quota.
3. Log in to Tanzu Operations Manager.
4. Reconfigure the quota on the on-demand settings page.
5. Deploy the tile.
6. Find out who is using the quota and take the appropriate action.

Failing jobs and unhealthy instances

To determine whether there is an issue with the VMware SQL with MySQL for TAS deployment:

1. Inspect the VMs by running:

   bosh -d service-instance_GUID vms --vitals
   

2. For additional information, run:

   bosh -d service-instance_GUID instances --ps --vitals
   

If the VM is failing, follow the service-specific information. Any unadvised corrective actions (such as running BOSH restart on a VM) can cause issues in the service instance.

A failing process or failing VM might come back automatically after a temporary service outage. See VM process failure and VM failure.

AZ or region failure

Failures at the IaaS level, such as Availability Zone (AZ) or region failures, can interrupt service and require manual restoration. See AZ failure and Region failure.

Techniques for troubleshooting

Instructions on interacting with the on-demand service broker and on-demand service instance BOSH deployments, and on performing general maintenance and housekeeping tasks

Parse a Cloud Foundry error message

Failed operations (create, update, bind, unbind, delete) result in an error message. You can retrieve the error message later by running the cf CLI command cf service INSTANCE-NAME.

$ cf service myservice

Service instance: myservice
Service: super-db
Bound apps:
Tags:
Plan: dedicated-vm
Description: Dedicated Instance
Documentation url:
Dashboard:

Last Operation
Status: create failed
Message: Instance provisioning failed: There was a problem completing your request.
     Please contact your operations team providing the following information:
     service: redis-acceptance,
     service-instance-guid: ae9e232c-0bd5-4684-af27-1b08b0c70089,
     broker-request-id: 63da3a35-24aa-4183-aec6-db8294506bac,
     task-id: 442,
     operation: create
Started: 2017-03-13T10:16:55Z
Updated: 2017-03-13T10:17:58Z

Use the information in the Message field to debug further. Provide this information to Support when filing a ticket.

The task-id field maps to the BOSH task ID. For more information on a failed BOSH task, use the bosh task TASK-ID.

The broker-request-guid maps to the portion of the On-Demand Broker log containing the failed step. Access the broker log through your syslog aggregator, or access BOSH logs for the broker by typing bosh logs broker 0. If you have more than one broker instance, repeat this process for each instance.

Access broker and instance logs and VMs

Before following these procedures, log in to the cf CLI and the BOSH CLI.

Access Broker Logs and VMs

You can access logs using Tanzu Operations Manager by clicking on the Logs tab in the tile and downloading the broker logs.

To access logs using the BOSH CLI, do the following:

1. Identify the on-demand broker (ODB) deployment by running the following command:

   bosh deployments

2. View VMs in the deployment by running the following command:

   bosh -d DEPLOYMENT-NAME instances

3. SSH onto the VM by running the following command:

   bosh -d DEPLOYMENT-NAME ssh

4. Download the broker logs by running the following command:

   bosh -d DEPLOYMENT-NAME logs

The archive generated by BOSH includes the following logs:

Access service instance logs and VMs

1. To target an individual service instance deployment, retrieve the GUID of your service instance with the following cf CLI command:

   cf service MY-SERVICE --guid

2. To view VMs in the deployment, run the following command:

   bosh -d service-instance_GUID instances

3. To SSH into a VM, run the following command:

   bosh -d service-instance_GUID ssh

4. To download the instance logs, run the following command:

   bosh -d service-instance_GUID logs

Run service broker errands to manage brokers and instances

From the BOSH CLI, you can run service broker errands that manage the service brokers and perform mass operations on the service instances that the brokers created. These service broker errands include:

• register-broker registers a broker with the Cloud Controller and lists it in the Marketplace.

• deregister-broker deregisters a broker with the Cloud Controller and removes it from the Marketplace.

• upgrade-all-service-instances upgrades existing instances of a service to its latest installed version.

• delete-all-service-instances deletes all instances of service.

• orphan-deployments detects “orphan” instances that are running on BOSH but not registered with the Cloud Controller.

To run an errand, run the following command:

bosh -d DEPLOYMENT-NAME run-errand ERRAND-NAME

For example:

bosh -d my-deployment run-errand deregister-broker

Register broker

The register-broker errand does the following:

• Registers the service broker with Cloud Controller.
• Activates service access for any plans that are activated on the tile.
• Deactivates service access for any plans that are deactivated on the tile.
• Does nothing for any plans that are set to manual on the tile.

You can run this errand whenever the broker is redeployed with new catalog metadata to update the Marketplace.

Plans with deactivated service access are only visible to admin Cloud Foundry users. Non-admin Cloud Foundry users, including Org Managers and Space Managers, cannot see these plans.

Deregister broker

This errand deregisters a broker from Cloud Foundry.

The errand does the following:

• Deletes the service broker from Cloud Controller
• Fails if there are any service instances, with or without bindings

Use the Delete All Service Instances errand to delete any existing service instances.

To run the errand, run the following command:

bosh -d DEPLOYMENT-NAME run-errand deregister-broker

Upgrade all service instances

The upgrade-all-service-instances errand does the following:

• Collects all of the service instances that the on-demand broker has registered.
• Issues an upgrade command and deploys the a new manifest to the on-demand broker for each service instance.
• Adds to a retry list any instances that have ongoing BOSH tasks at the time of upgrade.
• Retries any instances in the retry list until all instances are upgraded.

When you make changes to the plan configuration, the errand upgrades all the VMware SQL with MySQL for TAS service instances to the latest version of the plan.

If any instance fails to upgrade, the errand fails immediately. This prevents systemic problems from spreading to the rest of your service instances.

Delete all service instances

This errand uses the Cloud Controller API to delete all instances of your broker’s service offering in every Cloud Foundry org and space. It only deletes instances the Cloud Controller knows about. It does not delete orphan BOSH deployments.

Orphan BOSH deployments do not correspond to a known service instance. While rare, orphan deployments can occur. Use the orphan-deployments errand to identify them.

The delete-all-service-instances errand does the following:

1. Unbinds all apps from the service instances.
2. Deletes all service instances sequentially. Each service instance deletion includes:
   1. Running any pre-delete errands
   2. Deleting the BOSH deployment of the service instance
   3. Removing any ODB-managed secrets from BOSH CredHub
   4. Checking for instance deletion failure, which results in the errand failing immediately
3. Determines whether any instances have been created while the errand was running. If new instances are detected, the errand returns an error. In this case, VMware recommends running the errand again.

Use extreme caution when running this errand. You can only use it when you want to totally destroy all of the on-demand service instances in an environment.

To run the errand, run the following command:

bosh -d service-instance_GUID delete-deployment

Detect orphaned service instances

A service instance is defined as “orphaned” when the BOSH deployment for the instance is still running, but the service is no longer registered in Cloud Foundry.

The orphan-deployments errand collates a list of service deployments that have no matching service instances in Cloud Foundry and return the list to the operator. It is then up to the operator to remove the orphaned BOSH deployments.

To run the errand, run the following command:

bosh -d DEPLOYMENT-NAME run-errand orphan-deployments

If orphan deployments exist—The errand script does the following:

• Exit with exit code 10
• Output a list of deployment names under a [stdout] header
• Provide a detailed error message under a [stderr] header

For example:

[stdout]
[{"deployment\_name":"service-instance\_80e3c5a7-80be-49f0-8512-44840f3c4d1b"}]

[stderr]
Orphan BOSH deployments detected with no corresponding service instance in Cloud Foundry. Before deleting any deployment it is recommended to verify the service instance no longer exists in Cloud Foundry and any data is safe to delete.

Errand 'orphan-deployments' completed with error (exit code 10)

These details are also available through the BOSH /tasks/ API endpoint for use in scripting:

$ curl 'https://bosh-user:bosh-password@bosh-url:25555/tasks/task-id/output?type=result' | jq .
{
  "exit_code": 10,
  "stdout": "[{"deployment_name":"service-instance_80e3c5a7-80be-49f0-8512-44840f3c4d1b"}]\n",
  "stderr": "Orphan BOSH deployments detected with no corresponding service instance in Cloud Foundry. Before deleting any deployment it is recommended to verify the service instance no longer exists in Cloud Foundry and any data is safe to delete.\n",
  "logs": {
    "blobstore_id": "d830c4bf-8086-4bc2-8c1d-54d3a3c6d88d"
  }
}

If no orphan deployments exist—The errand script does the following:

• Exit with exit code 0
• Stdout is an empty list of deployments
• Stderr is None

[stdout]
[]

[stderr]
None

Errand 'orphan-deployments' completed successfully (exit code 0)

If the errand encounters an error during running—The errand script does the following:

• Exit with exit 1
• Stdout is empty
• Any error messages are under stderr

To clean up orphaned instances, run the following command on each instance:

Running this command might leave IaaS resources in an unusable state.

bosh delete-deployment service-instance_SERVICE-INSTANCE-GUID

View resource saturation and scaling

To view usage statistics for any service, do the following:

1. Run the following command:

   bosh -d DEPLOYMENT-NAME vms --vitals

2. To view process-level information, run:

   bosh -d DEPLOYMENT-NAME instances --ps

Identify apps using a service instance

To identify which apps are using a specific service instance from the name of the BOSH deployment:

1. Take the deployment name and strip the service-instance_ leaving you with the GUID.
2. Log in to CF as an admin.
3. Obtain a list of all service bindings by running the following: cf curl /v2/service_instances/GUID/service_bindings
4. The output from the curl gives you a list of resources, with each item referencing a service binding, which contains the APP-URL. To find the name, org, and space for the app, run the following:
   1. cf curl APP-URL and record the app name under entity.name.
   2. cf curl SPACE-URL to obtain the space, using the entity.space_url from the curl. Record the space name under entity.name.
   3. cf curl ORGANIZATION-URL to obtain the org, using the entity.organization_url from the curl. Record the organization name under entity.name.

When you run cf curl ensure that you query all pages, because the responses are limited to a certain number of bindings per page. The default is 50. To find the next page curl the value under next_url.

Monitor quota saturation and service instance count

Quota saturation and total number of service instances are available through ODB metrics emitted to Loggregator. The metric names are shown in the following table:

Quota metrics are not emitted if no quota has been set.

Techniques for troubleshooting highly available clusters

If your cluster is experiencing downtime or in a degraded state, VMware recommends gathering information to diagnose the type of failure the cluster is experiencing with the following workflow:

1. Consult solutions for common errors. See Highly Available Cluster Troubleshooting Errors.
2. Use mysql-diag to view a summary of the network, disk, and replication state of each cluster node. Depending on the output from mysql-diag, you might recover your cluster with the following troubleshooting techniques:
   • To force a node to rejoin the cluster, see Force a node to rejoin a highly available cluster manually.
   • To recreate a corrupted VM, see Recreate a corrupted VM in a highly available cluster.
   • To check if replication is working, see Check replication in a highly available cluster.
   For more information about mysql-diag, see Running mysql-diag.
3. Run bosh logs targeting each of the VMs in your VMware SQL with MySQL for TAS cluster, proxies, and jumpbox to retrieve the VM logs. You must run bosh logs before attempting recovery because any failures in the recovery procedure can result in logs being lost or made inaccessible.
   For more information, see the Downloading logs section.
   
4. If you are uncertain about the recovery steps to take, submit a ticket through Support. When you submit a ticket, provide the following information:
   • mysql-diag output: A summary of the network, disk, and replication state. The Running mysql-diag topic explains how to run mysql-diag.
   • downloaded logs: Logs from your VMware SQL with MySQL for TAS cluster, proxies, and jumpbox VM. The Downloading logs section explains how to obtain these.
   • Deployment environment: The environment that VMware SQL with MySQL for TAS is running in such as VMware Tanzu Application Service for VMs or a service tile.
   • Version numbers: The versions of the installed Ops Manager, TAS for VMs, and VMware SQL with MySQL for TAS.

Do not attempt to resolve cluster issues by reconfiguring the cluster, such as changing the number of nodes or networks. Follow only the diagnosis steps in this document. If you are unsure how to proceed, contact Support.

Force a node to rejoin a highly available cluster manually

If a detached node fails to rejoin the cluster after a configured grace period, you can manually force the node to rejoin the cluster. This procedure removes all the data on the node, forces the node to join the cluster, and creates a new copy of the cluster data on the node.

If you manually force a node to rejoin the cluster, data stored on the local node is lost. Do not force nodes to rejoin the cluster if you want to preserve unsynchronized data. Only do this procedure with the assistance of Support.

Before following this procedure, try to bootstrap the cluster. For more information, see Bootstrapping.

To manually force a node to rejoin the cluster, do the following:

1. SSH into the node by following the procedure in SSH into the BOSH Director VM.
2. Become root by running: sudo su
3. Shut down the mysqld process on the node by running: monit stop galera-init
4. Remove the unsynchronized data on the node by running: rm -rf /var/vcap/store/pxc-mysql
5. Prepare the node before restarting by running: /var/vcap/jobs/pxc-mysql/bin/pre-start
6. Restart the mysqld process by running: monit start galera-init

Recreate a corrupted VM in a highly available cluster

To re-create a corrupted VM:

1. To log in to the BOSH Director VM by doing the following procedures:
   1. Gather the information needed to log in to the BOSH Director VM by doing the procedure in Gather Credential and IP Address Information.
   2. Log in to the Tanzu Operations Manager VM by doing the procedure in Log in to the Tanzu Operations Manager VM with SSH.
   3. Log in to the BOSH Director VM by doing the procedure in SSH Into the BOSH Director VM.
2. Identify and re-create the unresponsive node with bosh cloudcheck, by doing the procedure in BOSH Cloud Check and run Recreate VM using last known apply spec.

   Recreating a node clears the logs. Ensure the node is completely down before recreating it.

   Only recreate one node. Do not recreate the entire cluster. If more than one node is down, contact Support.

Check replication status in a highly available cluster

If you see stale data in your cluster, you can check whether replication is functioning normally.

To check the replication status, do the following:

1. To log in to the BOSH Director VM, do the following:
   1. Gather the information needed to log in to the BOSH Director VM by using the procedure in [Gather credential and IP Address information](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-operations-manager/3-0/tanzu-ops-manager/install-trouble-advanced.html).
   2. Log in to the Ops Manager VM by doing the procedure in [Log in to the Ops Manager VM with SSH](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-operations-manager/3-0/tanzu-ops-manager/install-ssh-login.html).
2. Create a dummy database in the first node by running:
   mysql -h FIRST-NODE-IP-ADDRESS \ -u YOUR-IDENTITY \ -p -e "create database verify_healthy;" Where:
   • FIRST-NODE-IP-ADDRESS is the IP address of the first node you recorded in step 1.
   • YOUR-IDENTITY is the value of identity that you recorded in step 1.
3. Create a dummy table in the dummy database by running:
   mysql -h FIRST-NODE-IP-ADDRESS \ -u your-identity \ -p -D verify_healthy \ -e "create table dummy_table (id int not null primary key auto_increment, info text) \ engine='innodb';"
4. Insert data into the dummy table by running:
   mysql -h FIRST-NODE-IP-ADDRESS \ -u YOUR-IDENTITY \ -p -D verify_healthy \ -e "insert into dummy_table(info) values ('dummy data'),('more dummy data'),('even more dummy data');"
5. Query the table and verify that the three rows of dummy data exist on the first node by running:
   mysql -h FIRST-NODE-IP-ADDRESS \ -u YOUR-IDENTITY \ -p -D verify_healthy \ -e "select * from dummy_table;" When prompted for a password, provide the `password` value recorded in step 1. The previous command returns output similar to the following:

   +----+----------------------+
   | id | info                 |
   +----+----------------------+
   |  4 | dummy data           |
   |  7 | more dummy data      |
   | 10 | even more dummy data |
   +----+----------------------+
       

6. Verify that the other nodes contain the same dummy data by doing the following for each of the remaining MySQL server IP addresses:
   1. Query the dummy table by running:
      mysql -h NEXT-NODE-IP-ADDRESS \ -u YOUR-IDENTITY \ -p -D verify\_healthy \ -e "select * from dummy_table;" When prompted for a password, provide the `password` value recorded in step 1.
   2. Verify that the node contains the same three rows of dummy data as the other nodes by running:
      mysql -h NEXT-NODE-IP-ADDRESS \ -u YOUR-IDENTITY \ -p -D verify\\_healthy \ -e "select \* from dummy\\_table;" When prompted for a password, provide the `password` value recorded in step 1.
   3. Verify that the previous command returns output similar to the following:
      

      +----+----------------------+
      | id | info                 |
      +----+----------------------+
      |  4 | dummy data           |
      |  7 | more dummy data      |
      | 10 | even more dummy data |
      +----+----------------------+
                  

7. If each MySQL server instance does not return the same result, before proceeding further or making any changes to your deployment, contact Support.
   If each MySQL server instance returns the same result, then you can safely proceed to scaling down your cluster to a single node.

Tools for Troubleshooting

The troubleshooting techniques use these tools.

Downloading logs

The following are steps to gather logs from your MySQL cluster nodes, MySQL proxies, and, with highly available clusters, the jumpbox VM.

1. From Tanzu Operations Manager, open your BOSH Director tile > Credentials tab.

2. Click Bosh Commandline Credentials Link to Credential. A short plaintext file opens.

3. From the plaintext file, record the values listed:

   • BOSH_CLIENT
   • BOSH_CLIENT_SECRET
   • BOSH_CA_CERT
   • BOSH_ENVIRONMENT

4. From the BOSH CLI, run bosh deployments and record the name of the BOSH deployment that deployed MySQL for VMware Tanzu for MySQL.

5. SSH into your Tanzu Operations Manager VM. For information about how to do this, see Gather Credential and IP Address Information and SSH into Tanzu Operations Manager.

6. Set local environment variables to the same BOSH variable values that you recorded earlier, including BOSH_DEPLOYMENT for the deployment name you recorded above. For example:

   $ export BOSH_CLIENT=ops_manager \
     BOSH_CLIENT_SECRET=a123bc-E_4Ke3fb-gImbl3xw4a7meW0rY \
     BOSH_CA_CERT=/var/tempest/workspaces/default/root_ca_certificate \
     BOSH_ENVIRONMENT=10.0.0.5 \
     BOSH_DEPLOYMENT=pivotal-mysql-14c4
       

   If you connect to your BOSH director through a gateway, you also need to set variables BOSH_GW_HOST, BOSH_GW_USER, and BOSH_GW_PRIVATE_KEY.

7. Use the bosh logs command to retrieve logs for any instances in your deployment that are named database or prefixed with mysql (such as mysql-jumpbox).

   The following lines show one way to perform this:

   $ tempdir="$(mktemp -d -t MYSQLLOGS-XXXXXX)"
     echo Saving logfiles to "${tempdir}"
     for node in $(bosh instances --column="Instance" | grep -E "(database|mysql.*)/"); do
       echo -e "\nDownloading logs for: ${node}"
       bosh logs --dir="${tempdir}" ${node}
     done
     tar czf "${tempdir}/mysql-logs.tar.gz" ./*
     echo Bundled logfiles are in "${tempdir}/mysql-logs.tar.gz"
   

   For more information, see the bosh logs documentation.

8. Download the retrieved logfiles to your local laptop for inspection. bosh scp from your local workstation can be used to retrieve files on a BOSH VM. For more information, see the bosh scp documentation.

mysql-diag

mysql-diag outputs the current status of a highly available (HA) MySQL cluster in VMware Tanzu for MySQL and suggests recovery actions if the cluster fails. For more information, see Running mysql-diag.

Knowledge Base (Community)

Find the answer to your question and browse product discussions and solutions by searching the VMware Tanzu Knowledge Base.

File a support ticket

You can file a ticket with Support. Be sure to provide the error message from cf service YOUR-SERVICE-INSTANCE.

To expedite troubleshooting, provide your service broker logs and your service instance logs. If your cf service YOUR-SERVICE-INSTANCE output includes a task-id, provide the BOSH task output.